Skip to content

Guide

Designing for color blindness

About one man in twelve sees color differently. Here is which colors they confuse, a palette that works for nearly everyone, and the small design habits that make color optional.

By Mark Stoumann ·

How common is it?

Color vision deficiency, the medical name for color blindness, affects about 1 in 12 men and 1 in 200 women, according to the charity Colour Blind Awareness, which puts the total at around 300 million people worldwide. The US National Eye Institute gives the same 1 in 12 for men. It is more common in some populations than others: Masataka Okabe and Kei Ito, two researchers who are color blind themselves, cite about 8% of men of European descent, 5% of Asian and 4% of African men.

Most color blindness is inherited and lifelong. The genes for red-green color blindness are passed down on the X chromosome, and men have only one, which is why they are affected far more often. For a website with a broad audience, that means several visitors in every hundred, every day.

The types, and what gets confused

Very few color blind people see in black and white. Most see plenty of color but can’t tell certain colors apart. The National Eye Institute describes these types:

TypeWhat happensHard to tell apart
Deuteranomaly (most common)Some greens look more redRed and green, especially muted shades
ProtanomalySome reds look greener and less brightRed and green; red looks dark
Protanopia, deuteranopiaNo difference between red and green at allRed, green, brown, orange; blue and purple
Tritanomaly, tritanopia (rare)Blue-yellow confusionBlue and green, purple and red, yellow and pink
Monochromacy (very rare)No color at allEverything except lightness

The red-green types make up the vast majority. Blue and purple appear in the list because a purple is a blue with some red in it; when the red signal is weak, the purple looks blue.

Why lightness is your safety net

Red-green color blindness takes away one axis of color, but the sense of light and dark stays. So the question to ask of any pair is: do these differ in lightness, not just in hue? The WCAG contrast ratio measures exactly that, which makes the contrast checker a quick color blindness test too.

Pure red #ff0000 and CSS green #008000 look nothing alike to most people, but their contrast ratio is only 1.28:1: almost the same lightness. Take away the red-green difference and they are nearly the same color. That is why the classic “red bad, green good” status dot fails so many people.

As a rule of thumb, aim for at least 3:1 between colors that must be told apart, such as two lines in a chart or a status color against its neighbor. That is the level WCAG asks for graphics that carry meaning, and a lightness difference holds up far better than a hue difference for every type of color blindness. One caveat: for people with protan types, reds look darker than the formula assumes, so don’t put red text on a dark background.

A palette that works for nearly everyone

If you need several distinct colors, for a chart or a map, you don’t have to invent them. Okabe and Ito’s “color universal design” set is the best-known color blind safe palette, and it is the default in R’s palette.colors():

NameHexContrast with white
Black#00000021:1
Orange#E69F002.25:1
Sky blue#56B4E92.30:1
Bluish green#009E733.42:1
Yellow#F0E4421.32:1
Blue#0072B25.18:1
Vermillion#D55E003.86:1
Reddish purple#CC79A73.06:1

The last column matters if you use these colors for text or thin lines on white: only black and blue pass 4.5:1 for normal text. For chart fills and thick lines, bluish green, vermillion and reddish purple also clear the 3:1 bar against white; orange, sky blue and yellow need a dark outline or a dark background. Order matters too. Blue next to orange differs in both hue and lightness (2.30:1 between them), while blue next to vermillion relies on hue alone (1.34:1), so keep that pair apart or add a pattern.

Okabe and Ito add some practical advice from their own experience: label chart lines directly instead of relying on a color key, use magenta and green rather than red and green when you need a two-color overlay, and use thick lines and bold type for anything color-coded.

Never let color work alone

WCAG’s success criterion 1.4.1, Use of Color, is at the most basic level, A: color must not be the only visual means of conveying information. In practice:

  • Form errors: a red border alone fails. Add an icon and a message in words, such as “Enter a valid email address”.
  • Charts: give lines different dash styles or markers, and label them at the end of the line instead of in a legend.
  • Status: pair green and red dots with text (“Online”, “Failed”) or with different shapes, such as a check mark and a cross.
  • Links in text: keep the underline. If you remove it, the W3C’s technique G183 asks for at least 3:1 contrast between the link color and the surrounding text, and an underline on hover and focus is still a kind extra.
  • Selected states: a selected tab or filter shown only by a color change needs a second sign, such as a bolder label, a bar or a check mark.

How to test your design

  1. Grayscale first. Turn a screenshot to grayscale. Anything you can no longer tell apart relies on hue alone.
  2. Simulate. In Chrome, open DevTools, choose More tools, Rendering, and pick a type under Emulate vision deficiencies. Check protanopia, deuteranopia and tritanopia.
  3. Measure. Put any pair that must be told apart into the contrast checker and look for 3:1 or more.
  4. Ask. With one man in twelve affected, someone on your team or among your users likely is. Their feedback beats any simulator, which only shows the strongest form of each type.

When you build a new palette with the palette generator, the Balanced option keeps colors at equal lightness, which looks calm but is the hardest case for color blind readers. For charts and status colors, pick shades from different steps of the scale so they differ in lightness as well as hue. The contrast ratio guide explains how that lightness is measured.

Frequently asked questions

What colors should you avoid for color blind people?

Avoid pairs that differ mainly in hue and not in lightness, especially red with green, green with brown, and blue with purple, and avoid using any color alone to carry meaning. Pairs that also differ strongly in lightness, such as dark blue and light orange, are distinguishable for almost everyone.

What is the most color blind friendly palette?

A widely used choice is the eight-color set by Masataka Okabe and Kei Ito: black, orange #E69F00, sky blue #56B4E9, bluish green #009E73, yellow #F0E442, blue #0072B2, vermillion #D55E00 and reddish purple #CC79A7. It was designed so the colors stay distinct for the common types of color blindness.

Is blue and orange good for color blindness?

Yes, it is one of the safest pairs. Blue and orange sit on the axis that red-green color blindness leaves intact, and a dark blue against a light orange also differs in lightness, which helps people with any type.

Can I test my design for color blindness?

Yes. Chrome DevTools can simulate protanopia, deuteranopia, tritanopia and achromatopsia under Rendering, Emulate vision deficiencies. Simulations show the strongest forms, so treat them as a check, not as an exact picture of what every color blind person sees.

Does passing WCAG contrast make a design color blind friendly?

It helps, because contrast is measured on lightness, which color blindness leaves mostly intact. But it is not enough on its own: WCAG also requires that color is never the only way information is shown, so errors, chart series and links need a label, icon, pattern or underline as well.