Level APerceivable
1.4.1

Use of Color

Color can't be the only way you signal something, because not everyone sees color the same way, or at all.

In plain English

Color is a great extra signal, but a terrible only signal. If the only way to tell a required field, an error, a sale price, or a link apart is its color, then anyone who can’t distinguish that color is locked out.

The rule is simple: whenever color means something, add a second cue that doesn’t depend on color: a word, an icon, an underline, a pattern, or a shape.

Who this is for

  • People with color vision deficiency (very common, roughly 1 in 12 men), who may not see red-vs-green or other pairs the way you designed them.
  • Screen-reader users, who get no color information at all.
  • Anyone in grayscale or high-contrast mode, or on a cheap or sun-washed screen where colors flatten out.

What “good” looks like

Keep the color, just never let it stand alone.

Required field:  "Email *"  (asterisk + label)   ✓   not just a red border
Form error:      "⚠ Enter a valid email"          ✓   not just red text
Sale price:      "$29  Sale"  or a "Sale" badge   ✓   not just orange text
Links in text:   underlined                        ✓   not just a blue color

A quick test: switch your screen to grayscale (most operating systems have a one-tap setting) and browse your store. If you can still tell errors, links, and required fields apart, you pass.

Where stores get it wrong

The classic misses are red-only form errors, sale prices shown only in a brand color, “in stock / out of stock” dots with no label, and in-text links that are only a slightly different color with no underline. The common Shopify failures list covers these, and they often travel together with contrast problems.

How to meet it

Techniques the W3C accepts as sufficient (summarized). Follow a link for the full method.

Common mistakes

Patterns the W3C lists as failures of this criterion. Avoid these.

Frequently asked questions

What does 'use of color' mean in WCAG?+

Success Criterion 1.4.1 says color can't be the only visual means of conveying information, indicating an action, prompting a response, or telling elements apart. There must always be a second cue: text, an icon, a pattern, or a shape.

Can I still use color to show errors or sale items?+

Yes, just don't rely on it alone. Pair the red error color with an error message or icon, and pair a sale color with the word 'Sale' or a badge. Color can reinforce the message; it just can't be the whole message.

Why does using color alone fail accessibility?+

About 1 in 12 men and 1 in 200 women have some color vision deficiency, and screen-reader and grayscale users get no color at all. If color is the only signal, all of these people miss it.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 1.4.1?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit