Inclusive design · Color vision deficiency

Designing color-blind safe UIs: testing protanopia, deuteranopia, and tritanopia

Roughly 1 in 12 men and 1 in 200 women experience some form of color vision deficiency (CVD). Even when a palette passes WCAG text contrast, adjacent status colors—like red error and green success—can collapse into nearly identical olive/brown tones under protanopia or deuteranopia.

What each simulation mode checks

  • Protanopia (red-weak / red-blind): Deep reds darken dramatically and merge with dark greens or browns. Never place dark red text on a black card without checking luminance.
  • Deuteranopia (green-weak / green-blind): Classic red/amber/green traffic-light badges lose hue separation. Pair status pills with icons and explicit text labels.
  • Tritanopia (blue-yellow): Blues shift toward teal and yellows look pinkish-gray; chart series that rely on blue vs teal alone can become indistinguishable.
  • Monochromacy (achromatopsia): Strips all hue and chroma so you see pure luminance contrast—ideal for auditing visual hierarchy at a glance.

Practical three-step verification workflow

  1. Build your 5-color palette in the Generator and aim for adjacent luminance gap badges above 1.5:1 between neighboring chart or badge colors.
  2. Switch the top vision dropdown from Normal Vision through Deuteranopia and Monochromacy—ColorStory filters the swatch fills while keeping UI labels crisp.
  3. Ensure no interaction (form validation, chart series, link state) depends on hue alone; pair color with iconography, borders, or text badges.