| Etonkovidova | |
| Feb 2 2023, 2:56 AM |
| F36578141: Screen Shot 2023-02-01 at 2.55.38 PM.png | |
| Feb 2 2023, 2:56 AM |
| F36578291: Screen Shot 2023-02-01 at 6.50.59 PM.png | |
| Feb 2 2023, 2:56 AM |
| F36578134: Screen Shot 2023-02-01 at 2.46.52 PM.png | |
| Feb 2 2023, 2:56 AM |
Based on T328058: [QA task] Accessibility check for Wikifunctions pages
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Etonkovidova | T328627 Accessibility check: Background and foreground colors on disabled primary Codex buttons do not have a sufficient contrast ratio. | |||
| Declined | None | T296034 Re-evaluate disabled Codex state colors to WCAG 2.2 |
The first example is an upstream Ace editor choice which we can't control.
The second and third are both concerns with the WikimediaUI interface (via Codex); I guess we should tag them in?
Stand-alone example of this button is https://doc.wikimedia.org/codex/latest/components/demos/button.html#destructive-primary-disabled
Thank you for reviewing and adding tags! Yes, button.html#destructive-primary-disabled displays the same contrast ratio complaint.
@Etonkovidova if i'm not mistaken, and i'm not interpreting this incorrectly, inactive buttons (and inactive components in general) are not required to have a minimum color contrast ratio
Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
source https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html
Thanks @AAlhazwani-WMF for putting it in the right context. See also T281717#7053678 for historic reference.
Note, that this exception stays the same in WCAG 2.2 https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html
Thx @Volker_E and @AAlhazwani-WMF for clarification, for the reference to https://phabricator.wikimedia.org/T281717#7053678. My understanding of "inactive user interface component" was different. I saw the inactive state of any button as an essential element of the page that contributes to users' understanding of workflows available to them.