How accessible is your website?Start free check
WCAG 1.4.1Level APerceivable

Use of Color: Never Rely on Color Alone

Also called: Color alone, Color-only information, Color as the only cue

Definition

Use of Color is WCAG success criterion 1.4.1. Color must not be the only visual means of conveying information, indicating an action, prompting a response or distinguishing a visual element.

Use of Color is the WCAG rule that color may never be the only way a page tells visitors something. A red border alone on a wrong form field, a link that differs from the text around it only by its hue, or a chart that is read only by its colors all shut out people who cannot see those colors. You can keep your colors – you just add a second cue such as text, an icon, an underline or a pattern.

What it means

WCAG 1.4.1 Use of Color is a Level A criterion of WCAG 2.2, and is included in EN 301 549, the standard used to meet the European Accessibility Act. The criterion text: color is not used as the only visual means of conveying information, indicating an action, prompting a response or distinguishing a visual element.

W3C names who depends on it: people with partial sight, who often have limited color vision; older users who may not see color well; people with color vision deficiency (color blindness); and anyone using a monochrome or limited-color display.

Where color is used Second cue that works
Required or invalid form fields Text like "(required)" or an error message, plus an icon
Links inside running text Underline – or at least 3:1 contrast to the surrounding text (W3C technique G183)
Charts and maps Patterns, direct labels or numbers with a legend (G111, G14)
Status (online, sold out, active tab) A word, a symbol or a change in shape or weight

Examples

A common failure (W3C F73) is a link that is only colored. Dark gray #333333 text with links in #0066CC has just 2.27:1 between link and text – too close for G183, so the link needs an underline. Black text with links in #2563EB reaches 4.06:1 against the text and 5.17:1 against white.

Example
<!-- Bad: the only sign of an error is a red border -->
<input id="email" style="border-color: #d00000">

<!-- Good: text and icon tell the error, color only supports it -->
<label for="email">Email (required)</label>
<input id="email" aria-invalid="true" aria-describedby="email-error">
<p id="email-error">⚠ Please enter an email address like name@example.com.</p>

<!-- Good: links in running text keep their underline -->
<style>
  main p a { color: #0066cc; text-decoration: underline; }
</style>
Do

Underline links in paragraphs, write "required" or show an icon next to required fields, explain errors in words, add labels or patterns to chart lines and mark the current tab with more than its color.

Don't

Remove the underline from links in text without another cue, mark wrong fields only with red, ask visitors to "click the green button", or show status only as a red or green dot.

These cues also help everyone else: a clear error identification message and a link purpose that is obvious at a glance make forms and articles faster to use.

How to check use of color

    Questions

    Do links have to be underlined for WCAG?

    Not always. Links in running text need a cue besides color. An underline is the simplest one; W3C also accepts a link color with at least 3:1 contrast to the surrounding text (technique G183).

    Is a red error border enough?

    No. If the only sign of an error is red, people who cannot see red miss it. Add an error message in text and, ideally, an icon next to the field.

    What is the difference between use of color and color contrast?

    Use of color (1.4.1) asks whether information has a cue besides color. Color contrast (1.4.3) asks whether text is readable against its background. They are tested separately.

    Can I find use-of-color problems automatically?

    Partly. Automated checks can compare link and text colors, and the free WCAG scanner helps you find code-level issues across your pages. Charts, error states and instructions still need a quick look in grayscale.

    • Color Contrast: WCAG Ratios and How to Check Them

      Color contrast is the difference in brightness between text or interface elements and their background, measured as a ratio from 1:1 to 21:1. WCAG requires at least 4.5:1 for normal text and 3:1 for large text.

      Read definition: Color Contrast: WCAG Ratios and How to Check Them
    • Non-text Contrast: 3:1 for Icons, Borders and Focus

      Non-text Contrast is WCAG success criterion 1.4.11. The visual parts needed to identify user interface components and their states, and the parts of graphics needed to understand content, must have a contrast ratio of at least 3:1 against adjacent colors.

      Read definition: Non-text Contrast: 3:1 for Icons, Borders and Focus
    • Link Purpose: Write Link Text That Makes Sense

      Link purpose is what a link does or where it leads. Under WCAG 2.4.4, users must be able to tell it from the link text alone or together with its programmatically determined context, such as the surrounding sentence.

      Read definition: Link Purpose: Write Link Text That Makes Sense
    • Error Identification: Clear Form Error Messages

      Error identification means that when a website detects an input error automatically, it points out the field in error and describes the problem to the user in text. It is required by WCAG 3.3.1 at Level A.

      Read definition: Error Identification: Clear Form Error Messages

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done