Support high contrast mode in chrome without a plugin
See original GitHub issueSummary
Although Carbon supports Windows High Contrast Mode in Chrome with a Chrome plugin, you should be able to support it on native Chrome.
This can be done (in theory) by using the forced-colors media query instead of the prefers-contrast
and -ms-high-contrast
media queries.
Justification
Easier for vision-impaired people to use Carbon web apps if they don’t need to install a plugin.
Also, according to MDN, forced-colors
is a web standard whereas prefers-contrast
hasn’t been approved, and of course, -ms-high-contrast
is Microsoft-specific.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to Turn High Contrast Mode On/Off on any website
About Helperbird is a Chrome /Edge/Firefox browser extension that gives you the features to make more web more accessible and productive to ...
Read more >High Contrast
High Contrast lets you browse the web with your choice of several high-contrast color filters designed to make it easier to read text....
Read more >Microsoft adds High Contrast Mode support to Chrome and ...
Microsoft adds High Contrast mode Support to Google Chrome and Chromium Edge on Windows, here is how you can enable it.
Read more >92 - Chrome should support high-contrast color schemes for ...
Use system themes where possible in Omnibox edit and dropdown; in other cases, provide a pair of colors and use whichever contrasts more...
Read more >How to Turn On & Off High Contrast Mode in Your Browser
Go to the Chrome Web Store to download the High Contrast extension. · Click on the Add to Chrome button. · Click the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK, thanks. I’m expecting though that you’ll end up with dozens of tickets – one for every place you currently use
prefers-contrast
– which seems like overkill for what should just essentially be a global search-and-replace. That’s why I thought this one ticket would be sufficient.WIP PR: #8489