Home / Guides
Designing for colour blindness
Colour blindness — more precisely, colour vision deficiency — affects roughly 1 in 12 men and 1 in 200 women, according to Colour Blind Awareness, most of them with red-green deficiency. The WCAG rule that protects them is a single Level A criterion, SC 1.4.1 Use of Color: colour is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. Everything in this guide is that sentence, applied.
The vision types you are designing for
- Protanopia / protanomaly — no, or shifted, red perception. Reds darken and move toward green-brown.
- Deuteranopia / deuteranomaly — the most common family: no, or shifted, green perception. Reds and greens converge.
- Tritanopia / tritanomaly — blue perception absent or shifted; rare. Blues move toward green, yellows toward pink.
- Achromatopsia / achromatomaly — total, or partial, absence of colour vision; the world in luminance only. Very rare, and the strictest test of whether your design works without hue at all.
Simulators approximate these with published models — this site uses the model of Machado, Oliveira and Fernandes (2009) — but a simulation is an approximation of a spectrum, not a photograph of someone else's eyes.
Where colour-only design actually breaks
- Status by colour — a red figure for "down" and green for "up" becomes two similar brownish figures. Add arrows, signs, or words.
- Required-field asterisks in red — say "required" in text; the asterisk alone is fragile even for fully sighted users.
- Links distinguished by colour only — inside body text, a link needs a non-colour cue: an underline is the reliable default. WCAG techniques accept colour-only links only with an additional cue on hover/focus and a strong contrast difference from body text — the underline is simpler and kinder.
- Charts — series told apart by hue alone collapse. Label lines directly, vary dash patterns, and never let a legend be the only key.
- Form errors — a red border alone says nothing to someone who cannot see the red. Pair it with an icon and text.
Design moves that always work
- Add a second cue — icon, label, pattern, position or shape alongside every colour signal. Redundancy, not palette surgery, is the fix.
- Choose palettes whose pairs survive simulation — test your actual pairings under protanopia and deuteranopia, not just a generic "colour-blind safe" list.
- Keep luminance contrast doing the heavy lifting — pairs that differ strongly in lightness stay distinguishable in almost every vision type.
- Name colours in words where colour is the content — "the blue route" on a map needs its name on the route itself.
Honest limits
A simulator shows you a model's rendering of a deficiency, at one severity. Anomalous trichromacy in real people varies continuously, lighting and screens vary, and no simulation substitutes for a user who lives with the deficiency. Use simulation to catch collisions early — pairs that become indistinguishable are real findings — and treat a clean simulation as "no obvious barrier", never as proof.
Put it into practice
Preview your colours under all eight vision types.
Every pairing in your palette, verdict by verdict.
Sources and checking
WCAG facts in this guide follow the official W3C WCAG 2.2 Recommendation and its Understanding documents; any other fact is attributed to its source in the text. Facts checked November 16, 2026. Direct links to the sources are in the references below.
References
More guides