What the reader needs

Colour can help group information, but the meaning should survive without it. If a table distinguishes planned and live features, add explicit text labels rather than relying only on green and amber. If a form contains an error, include an explanation rather than a red border alone. Review text against its actual background, especially over photographs and gradients. A brand palette should support reading, not require the reader to work around it.

How to review it

Create a small design review covering body text, captions, buttons, links and status labels. Use an appropriate contrast-checking tool with the implementation team, and inspect the page in real lighting on a phone. Check images with text overlays at every crop used by the layout. Record which combinations are approved so later editors do not improvise unreadable variations. When a colour carries a business distinction, give that distinction a written label in the underlying content model too.

Imagine this

Hypothetical example

A feature comparison uses coloured dots to indicate availability. The team adds “Available,” “Planned” and “Confirm eligibility” labels and adjusts low-contrast captions. The page retains its cobalt and coral styling while the meaning no longer depends on interpreting the dots correctly.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

Further reading: W3C WAI: Colors with good contrast ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.