A brand colour cannot fail a contrast test

Somebody has run the brand palette through a contrast checker and something has come back red. Before anyone proposes a new blue, it is worth knowing what the checker was testing. Contrast is a property of two colours together, not of one colour on its own. Your brand colour did not fail anything. A pairing did.

That distinction decides what this costs you. If a colour has failed, the answer is a new palette and a rebrand nobody budgeted for. If a pairing has failed, the answer is a rule about which pairings are allowed to carry text, written into the identity while the palette is still on screen. The first is a project. The second is an afternoon.

What actually fails a contrast check

The rule being quoted at you is WCAG 2.2, criterion 1.4.3. It asks for a ratio of at least 4.5:1 between text and its background, and allows 3:1 for large text. A second criterion asks for 3:1 on interface components and on graphics you need to see in order to understand the content. Every one of those is a ratio between two things. There is no test a single hex value can sit down and fail on its own.

The same criterion carries an exemption that surprises most people who have just been sent a red report: "Text that is part of a logo or brand name has no contrast requirement." The logo is not the problem. The problem is the tenth use of that colour, where somebody set body copy in it because the palette offered no guidance and it was the brightest thing in the file.

A colour cannot pass or fail. A pair of colours can, and choosing the pairs is design work.

Why this is landing on marketing teams now

If the palette is being audited at all, there is a decent chance a deadline is behind it rather than a designer. The European Accessibility Act has applied since 28 June 2025, and its reach does not stop at the EU border: a UK business whose service is available to consumers in the EU can be in scope.

Read the scope before panicking about it. The Act covers a defined list of products and services rather than the web in general, among them e-commerce, banking services, e-books, telephony, passenger transport services, computers and ticketing machines. A B2B studio's marketing site is not on that list. A consumer checkout, a banking flow or an e-book reader is.

So there are two honest versions of this. If you sell to consumers in the EU, it is a legal question, and you should be taking advice on it rather than reading design writing about it. If you do not, it is a commercial question, which is not the lesser of the two. People who cannot read light grey on white do not complain. They abandon the form, and you file it under conversion.

Fix it in the palette, not in the build

Give every colour in the palette a stated job. Which colours may carry body text. Which are for large headings only. Which are backgrounds that never take text. Which pairings are approved, and which are unavailable however good they look in a deck. That page is short and dull, and it is the whole difference between guidelines a developer follows and guidelines a developer works around.

Most palettes need one addition rather than a rebuild: a darker sibling for the brand accent. Close enough to read as the same colour, dark enough to carry text at normal sizes. The bright original keeps doing the job it was chosen for, on buttons, in illustration, as a block of background. The darker one does the reading. Nobody outside the studio notices the difference, and the combinations pass.

Then test the pairs while the palette is still a palette. A colour can move by a few percent in week two of an identity project. By month six it cannot, because it is in the product, the app store screenshots, the templates, the signage and the slide master, and moving it has become a change request in five places.

If you are mid-rebrand, put this in the palette conversation

Not in the build phase, where it arrives as a developer's problem and leaves as a revision. Constraints introduced early tend to sharpen identities rather than flatten them. We spent a project turning six hundred pages of traffic sign law into something highways engineers could actually use, where not one word of the source was allowed to change, and that constraint was the brief rather than a tax on it. A contrast ratio is a much smaller constraint, and it arrives with a number attached, which makes it one of the easier things to design around.

If a palette genuinely cannot be made to work, that is worth finding out in week two of a brand project rather than after it has been rolled out everywhere.

One line, to whoever owns the website: which colour pairs are approved for body text? If that answer takes more than a day to arrive, the guidelines are missing a page, and the missing page is what the contrast checker actually found.