Skip to main content
Perceivly: Perceivly home

1.4.1 Use of Color

Level A · added in WCAG 2.0

Color must not be the only visual way you convey information, show an action, prompt a response or tell elements apart. Add a second cue, such as text, an icon, a pattern or an underline.

Who it helps

Among people of Northern European descent, about 1 in 12 men and 1 in 200 women have a color vision deficiency. Many cannot tell red from green. It also helps people with low vision, people using monochrome or high-contrast displays, and anyone reading a screen in bright sunlight.

How to meet it

Examples

Fails:A link shown only by color: #1a5fb4 against #333 body text is about 2:1, and there is no underline
p { color: #333; }
p a {
  color: #1a5fb4;
  text-decoration: none;
}
Fails:An error shown only with a red border
<label for="email">Email</label>
<input id="email" type="email" style="border-color: #d32f2f">
Passes:Links in body text keep their underline, so they do not depend on color
p { color: #333; }
p a {
  color: #1a5fb4;
  text-decoration: underline;
}
Passes:The error is stated in text, linked to the field and marked as invalid
<label for="email">Email</label>
<input id="email" type="email" style="border-color: #d32f2f"
       aria-invalid="true" aria-describedby="email-err">
<p id="email-err">Error: enter an email address like [email protected].</p>

Can a scanner detect this?

Partly

Automated tools can flag links in a text block that differ from nearby text only by color, with less than 3:1 contrast. They cannot judge whether color alone carries meaning in charts, status labels, form errors or selected states, so a person must review those.

axe-core rules that test it

Common mistakes

Official W3C explanation of 1.4.1

Check your own page

See which automated WCAG checks your page fails, with the failing elements and how to fix them.

Enter a page address, for example example.com/shop.

Reviewed November 2, 2026