You rarely need a new brand colour. You need a partner shade. Most bright brand colours, oranges, yellows, light blues and greens, fail contrast when used as text on white, but pass easily on a dark background. The usual fix is to keep your main colour for large shapes and highlights, and add a darker version for text and links in light mode (and sometimes a lighter version for dark mode). Check every text-and-background pair against the common benchmark: 4.5:1 for normal text, 3:1 for large text and for things like buttons and icons.
The benchmark, in plain English
The most widely used web accessibility standard is WCAG 2.2. Two of its rules matter for brand colours.
Text (W3C: Understanding Contrast (Minimum), updated 4 October 2026, checked 17 November 2026):
- 4.5:1 for normal text.
- 3:1 for large text, which W3C defines as at least 18 point, or 14 point bold (roughly 24px and 18.5px on screen).
- Logos are exempt. Text that is part of a logo or brand name has no contrast requirement.
- Brand guidelines are not an exemption for anything else. W3C says text with low contrast “due to corporate identity or brand guidelines” is not exempted.
Non-text elements (W3C: Understanding Non-text Contrast, updated 4 October 2026, checked 17 November 2026):
- 3:1 for the parts of buttons, form fields, focus outlines and icons that people need to see to use them.
W3C also says these ratios are thresholds, not approximations: 4.499:1 doesn’t count as 4.5:1.
Why one colour can pass in one mode and fail in the other
Contrast compares how light two colours are. A bright colour is close to white in lightness, so it struggles on white and shines on black. A deep colour does the opposite.
Here are some example colours we measured using W3C’s contrast formula. They’re illustrations, not anyone’s brand.
| Colour | On white (#FFFFFF) | On near-black (#121212) |
|---|---|---|
| Bright orange #F28C28 | 2.45:1 (fails text, fails 3:1) | 7.63:1 (passes) |
| Deeper orange #A84F00 | 5.55:1 (passes) | 3.38:1 (large text only) |
| Mid blue #1F6FEB | 4.63:1 (passes, just) | 4.04:1 (large text only) |
| Light blue #6EA8FE | 2.42:1 (fails) | 7.76:1 (passes) |
Notice the mid blue. It passes as body text on white with little room to spare, then falls just short on dark. A colour that “nearly works” in both modes is often the one that causes trouble, because nobody thinks to check it twice.
The fix: give each colour a partner and a job
This is a hypothetical example. A [Business name] café has a bright orange brand colour, #F28C28. They love it, and customers recognise it. On their website’s white pages, orange links are hard to read (2.45:1). On their dark mode pages, the same orange looks great (7.63:1).
Instead of changing the brand, they write it down like this:
| Job | Light mode | Dark mode |
|---|---|---|
| Links and small text in the brand colour | Deeper orange #A84F00 (5.55:1 on white) | Bright orange #F28C28 (7.63:1 on #121212) |
| Large headings and big shapes | Bright orange is fine for decoration; check any heading text is 3:1 or more | Bright orange |
| Button | Bright orange background with near-black text (7.63:1) | Bright orange background with near-black text |
| Logo | Main logo (exempt) | Light version of the logo (exempt, but make sure it’s visible) |
The orange still owns the brand. It just isn’t asked to do jobs it can’t do.
The white-text-on-bright-button trap
A very common pattern is white text on a bright brand-coloured button. With our example orange, that’s 2.45:1, which fails for normal text. Dark text on the same button gives 7.63:1. If white text matters to your look, you’ll need a deeper button colour instead.
A 20-minute check for your own brand
- List every colour pair you actually use: body text on background, links on background, button text on button, secondary grey text, text on photos.
- Do it twice, once for light mode and once for dark mode, if your website, app or social graphics use both.
- Check each pair with a contrast checker. W3C’s understanding page lists several tools under “Related Resources”, and most design tools have one built in.
- Mark each pair as “any text”, “large text only” or “decoration only”.
- For each failure, try a partner shade: darken the colour for light mode, lighten it for dark mode, and recheck until it passes.
- Write the result into your brand guidelines as a role table, so nobody has to rediscover it.
Grey text is the quiet offender
Brand colours get the attention, but light grey secondary text (captions, dates, placeholder text in forms) fails more often. W3C’s contrast page notes that placeholder text and text shown on hover or focus are covered too. Check your greys in both modes with the same care as your brand colour.
When to change the colour itself
Sometimes a partner shade isn’t enough:
- Your colour is used almost everywhere as text, so a separate shade would mean redoing most of your materials anyway.
- The darker partner looks like a different brand, for example a yellow that turns muddy brown when darkened.
- You’re already planning a refresh. Choosing colours that work in both modes from the start is easier than patching later.
Even then, a small shift often keeps recognition. Customers tend to remember “that orange café”, not an exact hex code.
What this can and can’t do
Checking contrast makes your materials readable for more people, including those with low vision and anyone reading a phone in Singapore sunshine. It doesn’t make a design accessible on its own: colour shouldn’t be the only way you show meaning, and text size, spacing and layout matter too. If you need formal accessibility conformance for a contract or regulator, a full audit goes further than this check.
For what else belongs in a short brand guide, see our brand guidelines checklist for small teams.