Replies: 5 comments 5 replies
-
To meet 1.4.3, you would. The working group did not anticipate that this would be an issue for browser standard controls, so no exception was provided. An author might make a statement of partial conformance due to 3rd party content (https://www.w3.org/TR/WCAG21/#conformance-partial) but according to the WCAG spec this would still be a conformance issue. |
Beta Was this translation helpful? Give feedback.
-
|
good times, since this will be browser-dependent in many cases. i do wish there was a clearer demarcation of "WCAG vs UAAG" / "author responsibility vs browser developers" ... but ho hum |
Beta Was this translation helpful? Give feedback.
-
|
Me too, but the fact that authors can change the CSS does make this specific case easier to handle. Do you disagree with my conclusion? |
Beta Was this translation helpful? Give feedback.
-
|
that's not always true though, and especially per the use case provided. the options of a select element cannot be styled by web developers |
Beta Was this translation helpful? Give feedback.
-
For what it's worth: In Windows on Chrome, Firefox, and Edge, a web developer can now control the text color and background color of option elements, except for the currently selected one. So the problem is smaller, but still a problem. |
Beta Was this translation helpful? Give feedback.
-
|
Where end users can make the contrast of web content higher (or lower) through an operating system setting, are WCAG evaluators also permitted to adjust their own operating system settings to increase the contrast of certain web pages elements, and thus pass 1.4.3? In the Firefox bug for selected I'm working on contacting the Chrome team for a similar fix. Assuming these particular browser fixes do occur, they won't make @JAWS-test's important question go away entirely, but I hope the dilemmas for auditors and developers can become less frequent in practice. More importantly, these fixes in browser bugs should improve accessibility incrementally for end-users. |
Beta Was this translation helpful? Give feedback.
-
possibly related thoughts #2909 |
Beta Was this translation helpful? Give feedback.
-
|
To avoid scope creep of this issue, I'm moving my operating system settings question out of here and into new issue #3052. @JAWS-test, has your original issue here been answered? |
Beta Was this translation helpful? Give feedback.
-
I think not. I think there are different opinions on the subject. So this should be clarified by the Working Group and added to the Understanding. |
Beta Was this translation helpful? Give feedback.
-
|
Related Chrome bugs (new). Until at least one of these two bugs is fixed, they demonstrate the problem @JAWS-test asked about.
Related Firefox bug. The discussion has concentrated on which Windows system color should apply, not on styling with CSS. The Windows system color could still cause web content to fail 1.4.3 even after the fix. |
Beta Was this translation helpful? Give feedback.
-
If a standard unchanged HTML element does not keep the contrasts (e.g. a select with option), do I have to adjust the colors or use a custom drop down?
Of course, this is an error of the browsers, which I as a web developer am not responsible for and partly cannot influence at all (because I have no access to certain elements via CSS, which the browser displays for standard elements). But a corresponding exception is not mentioned in 1.4.3. There is only an exception for non-text contrasts in 1.4.11.
Examples: BIK-BITV/BIK-Web-Test#317. There, by the way, it is claimed: "Only if user-defined controls are used, for example rebuilt selects with their own styles, then contrast requirements must be fulfilled for these custom controls" - but I don't think that is what 1.4.3 says.
Related: #866
Beta Was this translation helpful? Give feedback.
All reactions