Designing Color for Color Blindness
· 4 min read
How color vision deficiency changes what people see, why red and green fail, and practical rules for states, charts and testing your interface.
Roughly 1 in 12 men and 1 in 200 women of Northern European ancestry have some form of color vision deficiency. On a site with thousands of visitors, that is a lot of people who may not see your red error state, your green "online" dot or the difference between two lines on a chart. The good news is that designing for them rarely means giving up color. It mostly means not letting color carry meaning on its own.
What color blindness actually is
Most people with color vision deficiency see color, just a smaller range of it. The common types are named after the cone that is missing or shifted:
- Deuteranomaly and deuteranopia (green cones): the most common type. Reds, greens, oranges and browns drift toward similar yellowish tones.
- Protanomaly and protanopia (red cones): similar red–green confusion, and reds also look darker than they do to others.
- Tritanomaly and tritanopia (blue cones): rare. Blue and green, and yellow and pink, become hard to tell apart.
- Achromatopsia: very rare. The world is seen in shades of gray.
The "-anomaly" forms are milder and far more common than the "-anopia" forms. Designing against the stronger forms covers the milder ones too.
Why red and green fail
Red and green are the classic pair for bad and good, and also the classic failure. The problem is not only hue. Typical UI reds and greens often have almost the same lightness, so once the hue difference is gone, nothing is left to separate them.
The first two are a common red and green. Their contrast ratio against each other is only 1.47:1. The last two are the same colors simulated for deuteranopia: two muddy olive tones with a ratio of 1.13:1, practically the same color. A status list that marks failures in red and successes in green gives these readers no information at all.
Rule one: never rely on color alone
WCAG success criterion 1.4.1 (Use of Color, level A) says color must not be the only visual means of conveying information. In practice, pair every color signal with a second cue:
- Status: add an icon or a word. A check mark and "Paid", a cross and "Failed".
- Form errors: show an error message and an icon, not just a red border.
- Links in text: keep the underline, or make sure links differ from body text by 3:1 and get an underline on hover and focus.
- Charts: label lines directly, or vary marker shapes and dash patterns, instead of relying on a color legend.
- Selected states: combine a color change with a border, a check mark or a weight change.
A quick test: convert a screenshot to grayscale. If you can still understand every state and every chart, color is supporting the design rather than holding it up.
Rule two: separate colors by lightness
Lightness differences survive every type of color blindness, including full achromatopsia. When two colors must be told apart, make one clearly lighter than the other. A light green and a dark red stay distinguishable even when their hues merge.
This also explains why text contrast rules help here. Text that meets 4.5:1 against its background is readable regardless of how the reader perceives hue, because the ratio is computed from luminance alone. For icons, borders and other non-text elements, WCAG 1.4.11 asks for 3:1. See color contrast and WCAG for the details.
Rule three: pick safer hue pairs
When you need two contrasting categories, blue and orange is the safest common pair. Blue sits on the axis that red–green deficiencies keep, so it stays blue, while orange shifts toward yellow. The two remain clearly different.
Blue and orange as designed, then simulated for deuteranopia: still one blue and one yellow. Other robust choices:
- For good and bad, use blue for good and orange or red for bad, or keep green but make it much lighter or darker than the red.
- For charts with many series, use a palette designed for color vision deficiency, such as Okabe–Ito or the viridis family.
- For heat maps, use a single hue that varies in lightness rather than a rainbow scale. Rainbows have bands of near-equal lightness that collapse for many readers.
Charts and data
Data visualization is where color blindness causes the most damage, because charts often have nothing but color to go on.
- Limit the number of categorical colors. Beyond five or six, even people with typical vision struggle to match them to a legend.
- Put labels next to lines and bars so readers do not have to match colors at all.
- Add white gaps between adjacent areas in stacked or pie charts so edges are visible regardless of color.
- Make hover and focus states show the value in text.
How to test
- Browser emulation: Chrome and Edge DevTools can emulate protanopia, deuteranopia, tritanopia and achromatopsia in the Rendering panel, on your real page.
- Palette preview: every palette page on Colorset has a Vision menu that redraws the website, dashboard and app previews as they appear with each deficiency.
- Grayscale screenshot: the simplest check for lightness separation.
- Real users: simulations are approximations. If your product relies heavily on color, ask people with color vision deficiency to try it.
Putting it together
Color blind–friendly design is mostly ordinary good design: enough contrast, clear labels, and more than one cue for anything important. Start from a palette with strong lightness steps, like the ones in high-contrast palettes, check it with the Vision simulator, and add icons and text wherever color is doing the talking.