Use of Color
Tier 1 · The normative floor
Baseline compliance
What the normative text of WCAG 2.2 requires, and nothing more. Only a failure of this tier is a WCAG failure.
The bare minimum
Color is not the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Normative text
Verbatim from WCAG 2.2, W3C Recommendation 12 December 2024. Underlined terms are defined below.
Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
Not required by the normative text
Common claims that this criterion does not support. Don't log these as WCAG failures.
- Avoiding color. Color can carry meaning as long as something else visual (text, an icon, a pattern, an underline) carries it too.
Notes in the criterion Informative
WCAG 2.2 lists notes among its informative material, which "does not create requirements that impact a conformance claim." They help interpret the criterion but are not part of the floor.
This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding.
Tier 2 · The gap
Usability & user impact
Where content can meet this criterion and still make things harder for people with disabilities. These are not failures of SC 1.4.1, so raise them as usability defects. Known failures, including failures of related criteria, are listed in Tier 1.
A second cue that meets 3:1 but is small, such as a small icon beside a red error message, is still easy for color-blind users to miss.
Tier 3 · The golden path
Recommended best practice
The pattern that meets the floor, closes the gap, and avoids audit disputes. A recommendation, not a requirement.
Pair color with text or an icon. Underline links in running text. Give charts patterns or direct labels.
W3C's Understanding document and techniques for SC 1.4.1 ↗ are informative: sufficient techniques show ways to pass, and documented failures show common ways to fail, but neither changes what the criterion requires.
How SC 1.4.1 maps to the WCAG 3 draft
From this site's reviewed map to the WCAG 3 editor's draft. It's an interpretation: W3C has not published a mapping.
Successor provisions
From WCAG 2.2, section 5.1: “The main content of WCAG 2.2 is normative and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative", diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.”