Get rid of yellow diamond to left of Subject
How do I get rid of the useless yellow diamonds to the left of the subject? It appears to do nothing but show "READ status" The email is bold if it is unopened. The undescernable stupid green spot to the right of the subject also indicate READ status.
STOP making changes with no purpose but to confuse us and piss us off.
Get the menu bar back where it belongs.
Put the search bar back where is relates to the subject and address of the email.
Why does the search bar say Ctrl + K ?
What is with all of the new clutter that appears to have no purpose?
The faint gray Search... is a contrast violation of WCAG.
I know I am complaining to the wall but .......
Todas las respuestas (4)
Idadho said
How do I get rid of the useless yellow diamonds to the left of the subject? It appears to do nothing but show "READ status" The email is bold if it is unopened. The undescernable stupid green spot to the right of the subject also indicate READ status. STOP making changes with no purpose but to confuse us and piss us off. Get the menu bar back where it belongs. Put the search bar back where is relates to the subject and address of the email. Why does the search bar say Ctrl + K ? What is with all of the new clutter that appears to have no purpose? The faint gray Search... is a contrast violation of WCAG. I know I am complaining to the wall but .......
If you really want a response from reasonable people you might use a less direct, confrontational tone when writing messages. It's not a good way to engage, and actually produces the opposite effect.
Sweat appeals have never even got a response before. I could resort to an ADA attorney regarding the low contrast and unrecognizable function issues.
I've been told that the development team does not really care. At least I get to vent and start a track record of requests for accommodations.
Idadho said
I've been told that the development team does not really care.
Then you are sadly misinformed - you might want to more carefully vet your information source. If the team did not care, they would not have someone specializing in accessibility, a focus which hasn't existed in the history of the product.
This is not mean that no mistakes are possible, or that everything that is demanded gets adopted. But it does mean that we are making great progress in accessibility, and that the team does care.
I've seen comments from those people who are supposed to be focused on accessibility. They don't give a rat's behind about what is truly needed. I will gladly stand before any of them and tell them how they have failed to make very simple changes that will improve accessibility.
Those in the accessibility team appear to be quota fillers so they can make the claim,"Yes, we have an accessibility team" Microsoft and Apple are the same. They serve the vision impaired/blind and a few other disabilities at a minimal level and consider the job done.
I used to do product testing for Intuit and TurboTax. I know how changes CAN be made. Quicken Home and Business was a result of the user team I was on.
Text under icon option. At the very least, a description when you pause your cursor over an icon. Every function should be obviously understandable. Nothing should require learning then memorizing how to do a task. Proper contrast. 4.6 to 1 is the required minimum contrast. Minimize clutter or make it optional. Those stupid yellow diamonds come to mind. The circled numbers next to folders, too.
There are untold millions of people who have difficulty with shades/contrast.
Firefox and T'Bird use to be eons ahead of Chrome and Edge for usability/accessibility. They have been backing into the useless swamp that Chrome and Edge have ruled for years.
I am likely the most intelligent person they will ever meet who has a visual processing disability. Most people who struggle with tech turn inward and just resign themselves to say "I'm just too stupid to use this." They are not too stupid. The developers choose to ignore their simple needs.