1.4.1 Use of Color (Level A) — WCAG 2.1
WCAG 2.1 Success Criterion 1.4.1 Use of Color (Level A): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Perceivable → 1.4.1 Use of Color
1.4.1 Use of Color (Level A)
What it requires: Color can’t be the only way information is conveyed. If color is used to show state, error, or category, there also has to be a non-color indicator (text, icon, pattern, underline).
Common failure: A form marks required fields only by turning the label red, and flags a validation error only by turning the field border red — a colorblind user or screen-reader user gets no signal either way.
Fix it: Pair color with a second cue: an asterisk plus the word “required,” an error icon plus visible error text, underlines in addition to colored links.
In 1.4 Distinguishable: 1.4.2 Audio Control →
↑ Back to Perceivable overview
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.