Compliance

Colour Contrast and Brand Palettes: How to Keep Your Agency's Look and Meet WCAG

Colour contrast is the most common accessibility failure on public websites, and it is usually a branding decision rather than a coding mistake. A pale-blue link, white text on a light-green banner, grey placeholder text in a form: each looks tidy to the designer and unreadable to a person with low vision, to anyone in bright sunlight, or to someone using a cheap screen.

The good news is that contrast is measurable. There are numbers to meet, and you can usually keep your brand by adjusting shades rather than starting over.

What does WCAG actually require?

The main criterion is 1.4.3 Contrast (Minimum), part of Level AA:

  • Normal text needs a contrast ratio of at least 4.5:1 against its background.
  • Large text needs at least 3:1. WCAG defines large as 18 point (about 24 pixels) or larger, or 14 point (about 18.5 pixels) and bold or larger.
  • Logos and purely decorative text are exempt, as is inactive interface text.

A second criterion, 1.4.11 Non-text Contrast (introduced in WCAG 2.1), asks for 3:1 for the visual information needed to identify user interface components and states, and for graphics needed to understand content. That covers form field borders, the outline of a button, a focus indicator and the lines in a chart. What changed in WCAG 2.2 adds more on focus visibility.

Both criteria are measured with a ratio computed from the luminance of the two colours. You do not have to calculate it by hand: any contrast checker will give the ratio for two hex values.

Where do brand palettes usually fail?

The failures follow a pattern.

  • Light accent colours as text. A pastel brand colour that works as a background fails as text.
  • White text on a mid-tone. Mid-tone teals, oranges and greens often sit around 3:1 against white, which passes only for large text.
  • Links distinguished by colour alone. If links inside a paragraph differ from the surrounding text only by hue, WCAG 1.4.1 (Use of Color) is not met. Add an underline, or ensure a 3:1 contrast between link and body text plus another cue on hover and focus.
  • Placeholder and disabled-looking text. Light grey hint text inside form fields is very common, and placeholder text still has to be readable if it carries meaning.
  • Text over images. Contrast varies across a photograph, so a headline over a photo can pass in one area and fail in another. A solid or semi-opaque panel behind the text fixes this.
  • Hover and focus states that reduce contrast.

How do you fix a palette without a rebrand?

You rarely need to drop the brand. Work through the palette in a few steps.

  1. List every colour pair in use, not just the main ones: body text, links, buttons, banners, form borders, charts, alerts, footers.
  2. Check each pair with a contrast tool, and record the ratio.
  3. Darken the text or lighten the background just enough. A shade closer to the brand colour often passes where a different hue would not.
  4. Create two tones of each brand colour: a light one for backgrounds and a dark one safe for text.
  5. Write the approved pairs into the style guide, so that every future page, slide and PDF uses them.
  6. Check the focus indicator and error states, which are often missed.

A style guide that lists safe pairs prevents the problem from coming back each time a new page is built.

What about charts, maps and infographics?

Colour is the main language of a chart, which makes it a risk area. Series that are distinguished only by a red and a green are indistinguishable for many people with colour-vision deficiency, and light lines on a white grid may fall below 3:1.

Does contrast apply to documents and slides too?

Yes. The same palette flows into PDFs, slide decks and social graphics. A website may pass while the downloadable PDF with the same colours fails. Accessible Word, PowerPoint and Excel documents explains how to apply the rules to Office files. Do not forget video: captions and on-screen text need contrast as well, as described in accessible video.

What changes with translation?

Translation touches colour in ways teams forget.

  • Text length changes. A button label that fitted in English may wrap in German, shifting text onto a part of the background where contrast is lower.
  • Scripts with fine strokes, such as some Arabic, Thai or Chinese typefaces, can lose legibility at small sizes and light colours more quickly than Latin text, so an elegant light-weight font can fail in practice even where the ratio passes.
  • Colour meanings differ by culture. Red for danger is not universal, and a colour-only cue in the source design does not become safer in translation.
  • Images containing text must be re-created in each language with the same contrast, rather than left in the source language.

If your palette is tested only in English, test it again in each language you publish.

How do you test and document it?

Run an automated checker for a first pass, then review by hand, because tools cannot judge text over images, hover states or charts. Automated scan vs. manual audit explains the gap. Keep a record of the pairs you checked and the ratios, as part of your test evidence.

Where Taika fits

We check contrast across websites, PDFs and slide decks, rebuild documents with compliant colour pairs, and re-create translated graphics so every language version meets the same standard. We do not redesign your brand identity; we help you meet the ratios inside it. We meet and exceed ISO 17100, 9001 and 27001 standards.

Reviewing a style guide? Send us your colour palette, a sample of the website pages, PDFs and slides in use, and the languages you publish in, then request a quote. Our accessibility assessment page explains how we scope a review.

Need this done right?

Taika Translations provides certified translation, interpretation, and accessibility services in 300+ languages.

Get a quote →More resources