Description
It is obvious that the user is responsible for the resulting contrasts when the user adjusts the colors on a web page (e.g. High Contrast or Dark Mode in the operating system, color adjustment in the browser, adjustment via userstyles etc.).
But what if the web author prevents the adjustment of the colors by querying the user's settings via CSS media queries (forced-colors, prefers-color-scheme, prefers-contrast
) and then adjusts the colors or prevents the adjustment of the colors? Is the author expected to accept the user's settings (the browser is obliged to do so according to UAAG)? If not, why not?
If yes:
- what content could be non-adjustable (graphics?),
- what minimum contrasts must be respected (for
prefers-contrast
=more maybe 7:1 instead of 4,5:1), - what maximum contrasts must be kept (with
prefers-contrast
=less) - what must be light or dark for
prefers-color-scheme
=light/dark? - is it sufficient to conform with WCAG contrasts SCs only in one user's display mode? If so, does that have to be the default mode? If it does not have to be the default mode: How must the user be informed that the default mode does not have sufficient contrasts, but another mode (of the browser or operating system) does?
This seems to me to be unresolved at this time because CSS techniques are newer than WCAG. If it is not possible to update to the existing Understandings, I would suggest to consider this from WCAG 2.2 or 2.3. In my opinion it would be absurd if the accessibility features of the browsers and operating systems (regarding high contrast or dark mode etc.) can be undermined by the author.
Related: #1209