Skip to content
Tutorials Center
My learning

Topics

Lesson 20 of 38 ยท Colour, Contrast and Media

Not Relying on Color Alone

Learn WCAG 1.4.1 Use of Color: add text, icons, underlines and patterns so color-blind users get the same information. Includes links, errors and charts.

About 1 in 12 men and 1 in 200 women have some form of color vision deficiency. Others use monochrome screens, print in black and white, or work in bright light that washes colors out. If your page says "fields in red are required" or "click the green button", some of your visitors cannot follow along.

WCAG success criterion 1.4.1 Use of Color (level A) says color must not be the only visual means of conveying information, indicating an action, prompting a response or distinguishing an element. The fix is always the same: add a second cue.

Common types of color vision deficiency

  • Deuteranopia / deuteranomaly (reduced green sensitivity): the most common. Reds and greens look similar.
  • Protanopia / protanomaly (reduced red sensitivity): reds look dark and muddy.
  • Tritanopia (blue-yellow): rare.
  • Achromatopsia: no color perception at all.

You do not need to memorize these. Test by viewing your page in grayscale; anything that disappears relied on color alone.

A link that is only a different color from the surrounding text fails unless the link color has at least 3:1 contrast against the body text and gains a non-color cue (usually an underline) on hover and focus. The simplest robust choice is to keep the underline.

Links with and without underlines

Navigation menus are different: links in a clearly grouped menu are identifiable by position, so an underline is not required there.

Form errors and required fields

Do not mark an invalid field with only a red border, and do not mark required fields with only a red label. Add:

  • Text that says what is wrong ("Enter an email address like [email protected]").
  • An icon with a text alternative, or a visually hidden "Error:" prefix.
  • A programmatic link to the field (aria-describedby, covered in form errors).
Color plus text plus icon

Notice that "(required)" is written out. A red asterisk alone is not enough unless a legend explains it, and even then, the word is clearer for screen reader users.

Charts, maps and status indicators

A line chart with five colored lines is unreadable if the colors look alike. Improve it with:

  • Direct labels at the end of each line instead of a color legend.
  • Different shapes for markers and different dash patterns for lines.
  • Patterns or textures in bar and pie fills.
  • A data table alternative next to the chart.

For status dots (online, away, busy), put a word next to the dot or change its shape (circle, half circle, ring). Traffic-light red/amber/green meters need text such as "Critical", "Warning", "OK".

Status with color and shape

Instructions that mention color

"Press the red button" is a problem for users who cannot tell the color, and for screen reader users who do not see any. Name the control instead: "Press Delete". You can mention the color as an extra hint, never as the only one.

A quick test routine

  1. Switch the OS or browser to grayscale (or use the DevTools "Emulate vision deficiencies" panel).
  2. Scan the page: can you still find links, errors, selected tabs, required fields and chart series?
  3. Add a second cue wherever something vanished.
flowchart TD
  A["Meaning conveyed by color?"] --> B{"Another cue present?"}
  B -- "text, icon, underline, pattern" --> C["Pass 1.4.1"]
  B -- "no" --> D["Add a second cue"]
  D --> C

The second cue can be text, an icon, a shape, an underline or a pattern.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which is the most robust way to make an inline link identifiable?

    An underline works for everyone, including users with monochrome screens. Color or bold alone can disappear.
  2. 2. A form marks invalid fields only with a red border. What should you add?

    Text explains the problem to everyone. Red is not distinguishable for some users and says nothing to screen readers.
  3. 3. Which makes a multi-line chart more accessible?

    Labels, patterns and a table give information without needing to tell the colors apart.
  4. 4. What is a fast way to test for color-only information?

    Grayscale removes hue, so anything that depended on hue stands out as missing.

Summary

  • 1.4.1 (level A) forbids color as the only way to convey information.
  • Keep underlines on in-text links; add text and icons to errors; label charts directly; use shapes for status.
  • Describe controls by name, not by color.
  • Test by viewing the page in grayscale.

Next: Text Resizing, Reflow and Spacing