Menu

Accessibility

Colour Contrast Testing

A practical UX and accessibility method for validating text and UI contrast against recognised readability standards.

How to run colour contrast testing to improve readability, accessibility compliance, and interface clarity.

5 min read

What it is

Colour contrast testing is a UX and method used to evaluate whether text and elements have sufficient contrast against their background.

It ensures that content is readable for users with visual impairments, including low vision and colour blindness.

The method involves checking contrast ratios against standards such as .

It applies to text, buttons, icons, and any element that conveys meaning through colour.

The focus is on , , and .

The goal is to ensure all users can perceive and understand the .

Contrast testing protects readability across real-world lighting, devices, and visual capabilities.

When to use it

Use this method whenever content needs to be readable.

It is most useful when:

you are designing or reviewing UI
you need to meet WCAG standards
you are auditing accessibility
you are working with text-heavy interfaces
you want to improve readability

It is less useful when:

the product is still in very early concept stages
colour is not being used to convey meaning
Colour contrast testing is often part of accessibility audits and design reviews.

Key takeaway

Run contrast checks throughout design and QA, not only at the end.

How to run it

Set up properly

Decide which elements you are testing, which level you are meeting, and which tool you are measuring with. Different tools round differently at the boundary, so agree one and stay with it.

Test real use cases, including text over photography, gradients and video, where a single ratio does not describe the whole surface.

Run the method

Colour contrast testing is part tool and part judgement. The tool gives you a number; whether the number is the right one to measure is your call.

  1. Measure the ratio between text and its actual background, not the background you intended. Overlays, tints and opacity all change the result.
  2. Check against the threshold for the level you are claiming, and record the measured figure rather than a pass or fail alone.
  3. Review every UI element that carries meaning, not only text: icons, focus rings, chart series, form borders and .
  4. Test each interactive state: hover, active, focus, disabled and error. Disabled styling is where contrast is most often abandoned entirely.
  5. Validate in real and on real devices. A ratio that passes on a calibrated monitor can be unreadable on a phone in daylight.

Focus on real , not just the numbers. Passing at 4.51:1 and being genuinely hard to read is a common and entirely legal outcome.

Capture and make sense of it

The value comes from clear, measurable results. After testing, document:

  • Every element that fails, with its measured ratio and required threshold
  • Issues prioritised by how much of the product uses that colour pairing
  • Specific colour adjustments rather than a note that contrast is insufficient
  • The states and tested, so nobody re-tests the same ground

Use this to improve and . Contrast fixes tend to be systemic. One token change can resolve findings across a whole product.

What to look for

Focus on:

Readability: whether text can be easily read
Contrast ratios: compliance with accessibility standards
States: different interaction states
Meaning: whether colour is used correctly
Consistency: across the interface

Where it goes wrong

Most issues come from:

If it looks fine to you, it might not be for others.

Judging contrast by eye, which is unreliable at exactly the ratios that matter
Testing text and ignoring icons, borders, charts and focus rings
Choosing a palette first and discovering the contrast problem after build
Skipping the states (hover, focus, disabled, error) where contrast is usually abandoned
Treating it as a launch check rather than something the design system enforces

What you get from it

Done properly, this method gives you:

Readable text for people with low vision, and for everyone in bright light
Measured ratios rather than opinions about whether something is legible
Fixes that are usually systemic: one token change resolving findings everywhere
Interfaces that hold up on a phone outdoors, not only on a calibrated monitor

Key takeaway

It helps ensure your product can actually be seen and used.

Get in touch

If this sounds like something you need, we can test and improve your colour contrast so your product is clear, accessible, and easy to use.

No guesswork. No assumptions. Just design that works for everyone.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is colour contrast testing in UX?

It is a method for checking whether text and UI elements are readable against their background.

When should you use colour contrast testing?

During design, accessibility audits, and before release.

What standards apply?

WCAG sets the thresholds. At level AA, normal text needs a contrast ratio of at least 4.5:1, large text at least 3:1, and interface components and meaningful graphics at least 3:1 against whatever sits behind them.

Large text means roughly 18pt, or 14pt bold. Level AAA raises normal text to 7:1 and large text to 4.5:1, which is worth targeting for long-form reading.

What can you test?

Body text, headings, links, buttons and form fields, plus icons and graphics that carry meaning rather than decoration. Test every state (hover, focus, disabled, error) and any text sitting over images or gradients, which is where contrast usually fails.

Does colour contrast testing improve UX?

Yes. It ensures content is readable and usable for all users.

Quick take

If users can’t read your content, nothing else matters. Test your contrast.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer