-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"High-contrast" mode #277
Comments
Hmm. Isn't one of the benefits of adhering to WCAG contrast guidelines that we don't have to do this? Can you link to me to any reading on this subject? This seems like a wacky solution, but maybe I'm not aware of how commonplace it is? |
Adhering to WCAG guidelines just keeps everything legible. This is about ensuring a great experience and keeping the interface clear, beyond just legibility, in terrible conditions. Another alternative is to add more whitespace and titling throughout our UI, so that borders and shapes aren't necessary to distinguish between UI elements. Here is a post from Salesforce that sort of alludes to the issue. |
This is one of those things that if it was me suggesting it, I would expect your response to be something like:
I read the Salesforce post, but it stills seems pretty wacky to have a special "high-contrast" mode for these users. Maybe we should pick up an old monitor from Craigslist, and bring it to our new office so that we can test our designs in a "real-world government IT" scenario? 😁 (Not a joke!) |
When I suggest we simplify, I'm relying on the fact that we know most human brains can only hold so much complexity in our heads. UI best practices work because human cognition and psychology are fairly predictable. By contrast, we can't predict a user's physical abilities or technology of choice (especially on the web!) And from that perspective, a "one size fits all" approach doesn't really work. You wouldn't design a building where everyone must take a long wheelchair ramp instead of a short flight of stairs. Instead, you make sure to accommodate differently-abled people with what works best for them. In this instance, displaying higher contrast to every monitor would actually be super distracting to users on normal screens, making it harder for them to distinguish information from decoration. I don't know if this specific idea is 💯, but in principle I think we should get more comfortable with the idea of letting users adjust our UI for ease of access. |
Also, I like the "old monitor" idea! I've been meaning to test Screendoor at an open device lab in SF, but I don't think they'll have old PCs, or old projectors... |
In person:
|
When I go to customer on-on-sites (DOJ in particular, but also other enterprises from past jobs), washed-out monitors are common, and washed-out projectors are commonplace.
Especially in the case of projectors, users don't want to fiddle with their display settings to improve visibility. Or they don't know how, or their IT admin won't let them.
It would be nice if we had a higher-contrast stylesheet that customers with less fortunate hardware choices could take advantage of.
During my DOJ visit, I noticed that anything lighter than
$darkerGray
was invisible. It would be cool if we could automatically:color:
property to$darkestGray
(or keep them at$black
, if applicable).background
andborder
colors) lighter than$darkerGray
to$darkerGray
The text was updated successfully, but these errors were encountered: