Level
A
Since
WCAG 2.0
/ WCAG criterion

1.4.1 Use of Color

Colour must never be the only thing that tells a person what something means, what to do or which item is which.

/ What it requires

Colour is often the quickest cue on a page: a red border on the field that failed, a green dot beside the service that is up, a blue word that turns out to be a link. This criterion requires that such a cue never stands alone. Wherever colour conveys information, indicates an action, prompts a response or tells one element from another, something visible besides colour has to carry the same meaning: text, an icon, a pattern, an underline, a change of shape. It protects people with colour vision deficiency, people with partial sight and many older people who see colour poorly, and anyone using a monochrome or limited-colour display.

The requirement is about sight and not about assistive technology. A text alternative that a screen reader announces does not satisfy it, because a sighted person who cannot tell red from green never hears it. Two colours that also differ in lightness, with a contrast ratio of at least 3:1 between them, count as a second visual cue, so a link clearly darker than the text around it can pass. That does not help where the user has to recognise a particular hue, such as green for valid and red for invalid. Using colour is never a failure in itself, and W3C notes that visited and unvisited links told apart by colour alone do not fail, because authors can style the visited state with colour only.

/ How pages fail it

  • Links in a paragraph are a slightly different blue from the body text, have no underline and reach less than 3:1 contrast against that text.
  • Required fields are marked only by a red label, with no asterisk and no word saying they are required.
  • A form shows a failed field only by turning its border red, and no error text appears next to it.
  • A line chart separates its series by colour alone, with a legend of coloured squares and no labels, markers or dash patterns on the lines.
  • A status column shows green, amber and red dots with no word or distinct icon, so the state of a server or an order cannot be read without telling the colours apart.

/ How to check it yourself

  1. List every place where colour seems to mean something: links in running text, required and invalid fields, chart series, status badges, the selected tab or menu item, map legends.
  2. View the page without colour. In Chrome DevTools open the Rendering panel, find Emulate vision deficiencies and choose Achromatopsia, then repeat with Protanopia and Deuteranopia.
  3. For each item on the list, check that the meaning survives: an underline or icon on links, an asterisk or the word required on fields, an error message in words, labels or patterns in the chart.
  4. Where links in text are told apart by lightness only, measure the link colour against the surrounding text colour with a contrast checker. The ratio must reach 3:1, and both colours still need 4.5:1 against the background under 1.4.3.
  5. Submit a form with mistakes and confirm that every error is stated in text and not only by a change of colour.

/ How to fix it

  • Keep text-decoration: underline on links in body text, or give them another visible cue such as a heavier font-weight. If the underline goes, keep at least 3:1 between the link colour and the text colour.
  • Mark required fields with an asterisk or the word required inside the label, explain the asterisk at the top of the form, and set the required attribute on the input.
  • Show each validation error as text next to its field, with an icon if the design wants one, and connect the message to the input with aria-describedby.
  • In charts, label the lines directly, give each series its own marker shape or dash pattern (stroke-dasharray in SVG), and provide the values in a table.
  • Put a word in every status badge, such as Up, Degraded or Down, next to the coloured dot, and mark the current navigation item with aria-current="page" plus a visible underline or bar.

/ What our scanner checks

Nothing in our scan reports under 1.4.1. The criterion asks whether colour is the only cue, which is a question about what a person sees, and no rule we run compares a link, a field state or a chart series with its neighbours to look for a second visual signal. HTML_CodeSniffer raises only a reminder for 1.4.1, and the scan keeps errors alone. A manual audit checks it with the page shown in greyscale.

/ Who fails it, in our own measurements

The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.

One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.

/ Questions about this criterion

Do links have to be underlined to meet WCAG 1.4.1?

No, but a link in running text needs some cue besides its hue. The underline is the simplest. Without it, the link colour must differ from the surrounding text by a contrast ratio of at least 3:1, which counts as a difference in lightness and not in colour alone. W3C also notes that a link styled exactly like the text around it does not fail 1.4.1, since no colour is used to mark it, although it is hard for everyone to find.

Does 1.4.1 apply to charts, maps and images?

Yes. The criterion covers any visual means of conveying information, so a chart, map or diagram whose meaning rests on colour alone fails it. Direct labels, markers, patterns or numbers next to the colours solve it. The text alternative should carry the same information as well: W3C lists a description that leaves out what the colours meant as a failure of both 1.1.1 and 1.4.1.

Is Use of Color the same as colour contrast?

No. 1.4.1 is level A and asks only that colour is never the sole cue. Contrast is measured under 1.4.3 for text, at 4.5:1 for normal text, and under 1.4.11 for interface components and graphics, at 3:1, both level AA. A page can pass every contrast check and still fail 1.4.1, for example with dark red and dark green status dots that both stand out well against white.