-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
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
Vivid Cyan Blue Button Block: Fails Accessible Color Contrast #264
Comments
hm, this is a content issue, the button is using the core color I'd like to hear some other thoughts about how we could fix this (because it is a contrast problem). (labelled question but I really mean "discussion" 🙂 ) |
Sorry I was going quick at the end of my day, really should be prefixing these with "the site looks gorgeous, apologies to nitpick" 😇 Everything else I've checked (not comprehensive) passed WCAG AA, this was the only thing that didn't so I just wanted to flag it. I'm not familiar enough with the codebase to know where else it's used. |
Here are the posts that contain the
I'm inclined to agree that this is a Content issue. |
#359 makes them bold in css, which should fix it going forward I think. |
Is there a plugin available for WordPress/Gutenberg which can flag elements that have low-contrast? That might resolve content issues going forward, and might be able to lean on editors to ensure the elements are accessible? |
That should be a core functionality, but it looks like it's not working on Buttons — made an issue about it here: WordPress/gutenberg#39226 I don't think we should be forcing buttons bold, I would rather see the existing content updated and let the editors manage this in the future. |
Button Blocks with #FFF text and #0693E3 background color (
.has-vivid-cyan-blue-background-color
) display at 16px in 400 weight, which fails WCAG AA and AAA.The text was updated successfully, but these errors were encountered: