Checklist

Give the colour a second way to speak

The meaning should survive when the colour does not.

About 1 min read

Before you use it

Use when
  • Status, charts or errors rely on red, green or another colour code.

Keep this limit in mind

  • An unexplained icon can be as ambiguous as a colour. Do not assume that adding any symbol makes the information accessible.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Checklist

  • Does each important state have information beyond its colour?
  • Can a reader distinguish chart series without memorising a colour legend?
  • Do error messages identify the problem rather than merely tinting a field?

Why it matters

Add a meaningful label, symbol, pattern or other non-colour cue. Keep that cue consistent and understandable in context. This addresses colour dependence; contrast, accessible names and text alternatives still need their own checks.

An example

A reconciliation table replaces red-only rows with an Error status and a short reason, while retaining colour as an optional aid.

Check your result

Can someone explain every important distinction without naming a colour?

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingGive the colour a second way to speak

Evidence and sources
Supports

WCAG 1.4.1 does not allow colour to be the only visual means of conveying information, indicating an action or distinguishing an element.

A text label or pattern does not independently establish sufficient contrast or accessible naming.

Understanding Success Criterion 1.4.1: Use of Color · Success criterion and intent.

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details