Conversion and UX

Colour Contrast

Also called color contrast, contrast, contrast ratio

How far text and interface elements stand out from their background, measured as a ratio with WCAG benchmarks.

Quick facts: Colour Contrast

Category
Conversion and UX
Also called
color contrast, contrast, contrast ratio
Level
Beginner
Affects
Accessibility, readability, button clicks, Equality Act compliance, Lighthouse accessibility score
Where to see it
Lighthouse in Chrome DevTools, axe browser extension, WAVE, WebAIM contrast checker
In this article4
  1. How colour contrast works
  2. Why it matters
  3. Common mistakes
  4. How to act on it

Colour contrast is the difference in lightness between text, or an interface element such as a button, and the background behind it. Enough contrast lets people read and use a page easily, including people with low vision, colour blindness, or a phone screen in bright sunlight.

How colour contrast works

Contrast is measured as a ratio, calculated from the relative brightness of the two colours. It runs from 1:1, where the colours are identical, to 21:1 for black on white. The Web Content Accessibility Guidelines (WCAG), at version 2.2 at the time of writing (October 2026), set the benchmarks most organisations use:

What it applies toLevel AALevel AAA
Normal body text4.5:17:1
Large text (about 24px, or about 19px bold)3:14.5:1
Button edges, form field borders, icons that carry meaning3:1Not set separately

Level AA is the usual target. Logos, purely decorative images and disabled controls are exempt. Placeholder text inside form fields is not exempt, and it is one of the most common failures.

Lightness is what counts, not hue. A mid-orange that looks bold as a large heading can fail when used for small white text on a button, because the white and the orange are closer in lightness than they appear. Darkening the orange slightly usually fixes it without changing the brand.

Why it matters

Low contrast shuts some visitors out and slows everyone else down. Pale grey body text, light text on photographs and thin outline buttons all make a page harder to read on a phone outdoors, on a cheap laptop screen, or for an older customer whose eyesight has changed.

There is a legal side in the UK. Under the Equality Act 2010, businesses that provide services to the public have a duty to make reasonable adjustments for disabled people, and that duty is widely understood to cover websites. Public sector bodies have specific website accessibility regulations that point to WCAG AA. For a private business, meeting the AA contrast ratios is a practical, measurable way to show you have taken the duty seriously.

It affects results too. A call to action that blends into its background gets pressed less, whatever the copy says.

Common mistakes

  • Light grey body text chosen because it looks elegant in a design mock-up.
  • Text over photographs with no overlay, so some words sit on dark areas and others on light ones.
  • Brand colours used everywhere. A colour that passes for large headings may fail for small links or button labels.
  • Pale placeholder text used instead of a proper label on form fields.
  • Checking only the main state. Hover, focus and error states need enough contrast too, and so does the keyboard focus outline.
  • Relying on colour alone, such as marking errors only in red, which some colour-blind visitors cannot tell apart.

How to act on it

Run your main templates through an automated checker such as Lighthouse in Chrome or the axe browser extension, which flag contrast failures with the exact ratio. For individual colour pairs, a contrast checker tool gives the ratio instantly. Then fix the colour palette, not individual pages: define a darker shade of each brand colour for small text and buttons, and keep the brighter shade for large headings and decoration.

Check text over images by hand, as automated tools often miss it. Record what you have checked and what is still outstanding in an accessibility statement.

Contrast is one of the first things I fix in a website redesign, because it is cheap to correct in the design system and expensive to patch page by page later.

Do and do not

Do

  • Meet WCAG AA ratios for text, buttons and form borders
  • Use a darker brand shade for small text and buttons
  • Check hover, focus and error states as well

Do not

  • Use pale grey for body text
  • Put text on a photo without an overlay
  • Rely on colour alone to show errors or status

Questions people ask about this

What contrast ratio do I need for my website?

Aim for WCAG level AA: at least 4.5:1 for normal text and 3:1 for large text, buttons, form borders and meaningful icons. Level AAA (7:1 for normal text) is stricter and rarely required across a whole site. If you meet AA everywhere, you are in a good position.

Do I have to change my brand colours to meet contrast rules?

Rarely. Most brands keep their main colour for logos, large headings and decoration, and add a slightly darker or lighter variant for small text and button labels. Visitors almost never notice the difference, but the ratio moves from failing to passing.

Is dark mode better for contrast?

Not automatically. Dark mode can cause its own problems, such as mid-grey text on a dark grey background, or pure white on pure black, which some readers find tiring over long passages. Whatever the theme, check the ratios separately for each one.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.