Pass color-contrast if aria-model="true" is on the page, and the text is aria-hidden
See original GitHub issueRelated to #170
Elements in the background of modals are currently flagged as contrast issues, even when within an aria-hidden
parent. Example here: https://jsfiddle.net/204dkrsn/2/show
I know the applicability of contrast to aria-hidden
elements is up for interpretation, since they’re also often visible. On the other hand, the current setup has been generating some false positives when modals are open.
Another workaround might be ignoring visual rules on anything outside an aria-modal="true"
element if one exists on the page, but I’m not sure how feasible that is.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Understanding Success Criterion 1.4.3: Contrast (Minimum)
The contrast requirement for larger text is therefore lower. This allows authors to use a wider range of color choices for large text,...
Read more >Understanding WCAG 2 Contrast and Color Requirements
I am blue text. Important. If text and background colors are swapped, the contrast ratio remains the same. Three success criteria in WCAG...
Read more >Text elements must have sufficient color contrast against the ...
Success Criterion: Ensure color contrast of at least 4.5:1 for small text ... Use the color contrast analyzer below to find colors that...
Read more >Info and Examples for Accessibility Insights for Web
Solve accessibility issues before they reach your customers.
Read more >Understanding Web Accessibility Color Contrast Guidelines ...
The contrast ratio explains the difference between the lightest color brightness and the darkest color brightness in a given range. It's 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 Free
Top 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
Thanks for the issue. This is a similar problem we encountered in #1482. Could probably solve them in the same way.
@straker sorry I missed this, thanks so much! I’m closing the issue, since I think the behavior is correct in both FF and Chrome now.
Thanks again!