We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Our "success" and "error" notification link texts fail the Lighthouse accessibility check for foreground / background contrast.
To Reproduce Steps to reproduce the behavior:
Expected behavior Link text contrast should pass accessibility checks.
Screenshots
Additional context Discovered via automated GitHub Action here. See failing Lighthouse report here.
Success text is #0072ce (pacific) on #f0f8eb (green-10), which is 4.49:1. Error text is #0072ce (pacific) on #fbefec (red-10), which is 4.34:1.
WCAG AA requirement is 4.5:1.
See previous related report at #1943; @anselmbradford tried to fix in #1944 but it seems this broke somewhere, maybe in #1919?
@sonnakim for awareness
The text was updated successfully, but these errors were encountered:
I see the issue. There's a group of notification modifiers
&__success, &__warning, &__error { & a {
…that slipped through the cracks and didn't get updated from __ to --. I'll fix this soon.
__
--
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Describe the bug
Our "success" and "error" notification link texts fail the Lighthouse accessibility check for foreground / background contrast.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Link text contrast should pass accessibility checks.
Screenshots
Additional context
Discovered via automated GitHub Action here. See failing Lighthouse report here.
Success text is #0072ce (pacific) on #f0f8eb (green-10), which is 4.49:1.
Error text is #0072ce (pacific) on #fbefec (red-10), which is 4.34:1.
WCAG AA requirement is 4.5:1.
See previous related report at #1943; @anselmbradford tried to fix in #1944 but it seems this broke somewhere, maybe in #1919?
@sonnakim for awareness
The text was updated successfully, but these errors were encountered: