On this page
The rule, in one sentence
WCAG success criterion 1.4.1, "Use of Color," says: color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. It sits at Level A — the most basic conformance tier, below even the AA level that contrast rules occupy — which is the standards body's way of saying this isn't advanced accessibility, it's the floor.
Note what the rule does not say. It doesn't ban color coding, doesn't require drab palettes, and doesn't limit how much color you use. It requires redundancy: whatever color communicates, something else must also communicate. Color remains the fast channel most users read first; the rule just guarantees a second channel exists.
Why a contrast checker can't catch this
Contrast (SC 1.4.3) and Use of Color (SC 1.4.1) fail independently, and conflating them is the most common audit mistake. A red error message on white can pass contrast at 7:1 and still fail 1.4.1 — if red is the only thing marking it as an error. Conversely, a chart whose two lines differ only by hue can fail both. Contrast asks "can everyone read this?"; Use of Color asks "can everyone tell what it means?" You need both, and they're tested differently: ratios in a contrast checker, meaning-survival in a color blindness simulator or plain grayscale.
The four places it fails in practice
Links inside body text. A link distinguished from surrounding prose only by color is the canonical violation. The clean fix is the one you're looking at on this site: underline links in running text. WCAG's alternative technique — link color at 3:1 against the surrounding text plus a visible cue on hover and focus — is legal but fragile in practice; the underline just works.
Form validation. A red border on the invalid field fails twice: red-green CVD users may not see which field is red, and no one is told what's wrong. The accessible pattern is boring and universal: an icon plus a text message attached to the field ("Email address needs an @"), with the red border kept as reinforcement.
Charts and dashboards. Two lines distinguished only by hue, a legend mapping colors to series, red/green candles — all rely on color matching between legend and mark, which is exactly what CVD breaks. Defenses, in rough order of power: direct labeling (put the name on the line, killing the legend round-trip entirely), distinct markers or dash patterns per series, and a CVD-tested palette — our designing-for-color-blindness playbook covers palette selection in depth.
Status dots. The green/yellow/red badge triple is everywhere, and unlabeled it's meaningless to a meaningful slice of users. Pair each with an icon (check / warning triangle / cross), a label, or at minimum a distinct shape. Text labels have a bonus: they survive screen readers, machine translation, and screenshots too.
How to audit for it
The grayscale test is the fastest first pass: screenshot the interface, drop the saturation to zero, and ask of every state and distinction, "would I still know?" Grayscale is stricter than any real deficiency, so it never produces false confidence. For a subtler check, run real screenshots through the image simulator under deuteranopia and protanopia — the two most common strong types — and look specifically at small elements: a 2px chart line loses its identity long before a large filled region of the same color does.
Then audit by category rather than by page: find every link-in-prose, every form error state, every chart legend, every status indicator across the product, and fix the pattern once in the design system. 1.4.1 violations are almost never one-off mistakes; they're systemic patterns, which is bad news for the audit and great news for the fix.
The mindset shift
The deeper lesson of 1.4.1 generalizes past disability: color is fragile everywhere. It disappears in grayscale printouts, bright sunlight, projector washout, night-shift filters, and machine translation of your screenshots. Information that survives with color removed is simply more robust information. Treat color as emphasis — the thing that makes meaning fast — never as the meaning itself, and the rule takes care of itself.