-
Notifications
You must be signed in to change notification settings - Fork 220
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
Make Accessibile Button #8
Comments
You can already use FYI using HSL for lighter/darker variants isn't a great idea, as HSL lightness is not a good measure of luminosity (think that yellow and blue both have 50% lightness). |
Ok, so you could do conversion of colors using http://stackoverflow.com/questions/17242144/javascript-convert-hsb-hsv-color-to-rgb-accurately So if what you wanted to do was find the closest WCAG 2.0 Compliant color, what is the best way to suggest a more accessible color? I don't know how Webaim is doing it, but theirs is just too coarse to be useful much of the time. I'd like to have something that gives designers a suggestion that is as close to their original vision as possible (while still meeting WCAG). |
I wonder if it's worthwhile to make it possible to convert colours between different representations? That would make it easier to use |
Soon, this will be possible via CSS alone. |
That is very cool! Thanks @LeaVerou I also like the implementation by http://contrast-finder.tanaguru.com/ |
This is a very visually appealing color contrast checker. Often though I end up going to http://webaim.org/resources/contrastchecker/
I do this because it has a simple lighter/darker link on the side which makes it pretty trivial to pick a variation that is just slightly darker than the original. I'm not sure how Webaim does this, but in talking to @mparker17 he suggested that this is something that could be done in a fairly straight forward way using the HSL color space.
It would be great to know given a random foreground color, what is the lightest background color necessary to meet WCAG 2.0 AA & also for AAA.
The text was updated successfully, but these errors were encountered: