Did you know that 1 in 12 people have some sort of color deficiency? This episode discusses colors and web accessibility including color contrast, conveying meaning through color, and CSS colors.
- W3C Checkpoint 2.1 (information)
- W3C Checkpoint 2.2 (contrast)
- About Color Blindness – general info and stats
- Understanding Color and Accessibility
- Accessibility Color Wheel – tool for confirming adequate color contrast
- Vischeck – tool for confirming adequate color contrast
3 replies on “Colors & Accessibility”
Thanks for another good show. I look forward to many more.
If I remember correctly, you commented that using named colors are deprecated. Do you have a source for that information?
This prompted me to do some research and figure this one out. From what I’ve found, the CSS3 Color Module Recommendation has the same 16 standard colors that they had in HTML 4.01 (links below). (CSS 2.1 also has orange which is omitted from either of the other specs.)
Otherwise, it seems like some colors were added to the CSS3 Color Module. Look at the section on (SVG color keywords). It list a few dozen key words that are new to this specification. They are borrowed from SVG 1.0 spec and X11’s color list.
I think that it would be correct to say that using standard colors would be safe for browsers. Using only those 16 would be safest for now. (Except for devices that don’t support color!)
HTML 4.01 Spec – Sec 6.5 Colors
CSS 2.1 Spec – Sec 4.3.6 Colors
CSS3 Color Module – Sec 4.1. HTML4 color keywords
CSS3 Color Module – Sec 4.3. SVG color keywords
Thank you for the informative response on using color names. Here was my source, from the W3C:
It does appear by other sources that you are correct–color names are not deprecated. Personally, I like hexadecimal.
Here’s a good point from WebAim about busy backgrounds (for all you My Space users!)