Skip to content
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

Support for Windows high contrast mode #4297

Closed
afercia opened this issue Jan 4, 2018 · 0 comments
Closed

Support for Windows high contrast mode #4297

afercia opened this issue Jan 4, 2018 · 0 comments
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes).

Comments

@afercia
Copy link
Contributor

afercia commented Jan 4, 2018

Follow up to #1562 (comment) and complementing a similar ticket open on the core Trac, see https://core.trac.wordpress.org/ticket/41286

Also mentioned in the (now closed) issue with initial accessibility recommendations, see #297 point 5:

You will have to support Windows High Contrast Mode in your controls, including the SVGs for the buttons. Luckily, this may not be very hard for single-color SVGs as the fill can be defined via a media query.

Windows high contrast mode removes, among other things, any background and box-shadow. Here's an example on Windows 10 and IE 11 with some text selected:

screenshot 24

Overall, the interface is visible but the biggest issue is the focus style. All the ones based on box-shadow are not visible, including, for example, some important controls in the toolbar and all the sidebar panels.

For many other controls, the focus indication is actually given only by the text of the tooltip:

screenshot 25

As mentioned in the Trac ticket, and as a long term goal, it would be great to switch to a new focus style not exclusively built with box-shadow. Note: borders and outlines are visible in high contrast mode.

@afercia afercia added the [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). label Jan 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes).
Projects
None yet
Development

No branches or pull requests

1 participant