-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
$node-green #80bd01 on white background does not pass accessible contrast ratio #501
Comments
Ref: #458 |
Agreed. @mikeal who should we ping to double check if and which colours could be altered to increase accessibility, without violating brand rules? |
+1 to |
The dark green on the bottom left of the "o" in "node" is If anyone else wants to check these, this is the easiest place http://webaim.org/resources/contrastchecker/ |
We have a new set of colors from a preliminary document for the new logo design: Maybe |
The WCAG validation is supposed to set the floor for contrast, so on that basis it would have to be Unless there are objections to that, since the colors are documented now, a pull request seems appropriate to update this. |
Currently standard links on the website appear in
#80bd01
most often on a white background. Chrome accessibility tools indicate the contrast ratio is 2.28 and passing for AA level accessibility at the ~15px font-size on the API docs, like this page https://nodejs.org/api/fs.html would be a contrast ratio of ~3 which equates to a suggested#6ea400
.I personally think it is important that the website is properly accessible to everyone, but realize this creates some conflict between a Node brand color and what color combinations are accessible.
Please let me know if I can be of any assistance in resolving this, I felt it was premature to just open a PR suggesting a new color where it is a brand issue.
The text was updated successfully, but these errors were encountered: