Almost every brand has a signature colour. It’s on the logo, the business cards and the shop sign. When a website is designed, that colour naturally goes everywhere: buttons, links, headings, backgrounds. Then someone runs an accessibility check and discovers that white text on the brand’s bright orange is hard to read, light grey body text fails contrast requirements and links are indistinguishable from surrounding text. An accessible colour palette solves this without abandoning the brand.
This happens because brand colours are chosen for recognition, not for readability. A colour that’s striking at logo size can be difficult to read as small text or as a button background.
The solution isn’t to abandon the brand. It’s to build a palette around it: a set of shades and supporting colours designed to work together accessibly, with clear rules for where each one is used.
Understanding contrast
Contrast is the difference in perceived brightness between foreground and background. WCAG measures it as a ratio from 1:1, no contrast, to 21:1, black on white.
The key requirements at WCAG level AA, which most laws and guidelines reference:
- Normal text: at least 4.5:1
- Large text, roughly 24px regular or 18.7px bold and above: at least 3:1
- User interface components and graphics, such as button borders, form field outlines, icons and focus indicators: at least 3:1 against adjacent colours
At level AAA, the stricter standard, normal text needs 7:1 and large text 4.5:1.
These ratios aren’t arbitrary. They’re designed so text remains readable for people with moderately low vision, colour vision deficiencies and in poor viewing conditions like bright sunlight on a phone screen, which affects everyone.
Testing contrast
Several free tools check contrast ratios:
- WebAIM’s Contrast Checker, where you enter two colours
- Browser developer tools, which show contrast ratios when you inspect text in Chrome, Edge and Firefox
- Design tool plugins for Figma and similar tools
- Automated accessibility checkers like WAVE and axe, which flag contrast failures on live pages
Test real combinations as they appear on the site: text on backgrounds, buttons in each state, links within paragraphs and text over images.
Step 1: Start with the brand colours
List your brand’s existing colours. For each one, test contrast against white and against your darkest text colour. You’ll typically find that:
- Dark brand colours, such as navy, deep green and burgundy, work well as text and button backgrounds with white text.
- Mid-tone colours, such as bright blue, teal and red, are borderline. They may work for large text or button backgrounds but fail for small text.
- Light or vivid colours, like yellow, orange, light green and pink, fail as text on white and often fail with white text on top.
That’s normal. It doesn’t mean those colours can’t be used. It means they need a defined role.
Step 2: Build a scale for each colour
Instead of a single shade of each brand colour, create a range from very light to very dark. A common approach uses steps such as 50, 100, 200 through 900, where 50 is a very light tint suitable for backgrounds and 900 is a deep shade suitable for text.
For an orange brand colour, the scale might include:
- A very light orange tint for section backgrounds
- The original brand orange for decorative elements, icons and large accents
- A darker orange that passes 4.5:1 against white, for text links and small text
- A deep orange-brown for headings or hover states
Tools like colour scale generators can create these ranges, but always adjust by eye and verify contrast. Generated scales often need tweaking to keep the hue looking like the brand as it gets darker.
The key insight is that the darker shade is still recognisably your brand colour. Visitors perceive the brand consistently even though the exact shade varies by use.
Step 3: Define neutral colours
Most of a website is text on a background, so neutrals do the heavy lifting:
- Body text: a very dark grey or near-black. Pure black on pure white is fine for contrast but can feel harsh on screens. Something like #1f2937 on white has a high ratio and looks softer.
- Secondary text, for captions and metadata: a mid grey that still passes 4.5:1. Many designs use light greys that fail. Check them.
- Borders and dividers: lighter greys are fine for decorative lines, but form field borders need 3:1 against the background.
- Backgrounds: white, plus one or two very light greys for alternating sections.
Step 4: Assign roles
A palette works best when each colour has a clear job. Define roles such as:
- Primary: the main action colour for buttons and key links
- Primary hover: a darker or lighter variant for hover and active states
- Accent: decorative highlights, icons and illustrations
- Text: body copy
- Text muted: secondary text
- Background: main page background
- Surface: cards and alternate sections
- Border: field and card outlines
- Success, warning and error: for form messages and notices, each with accessible text and background combinations
Write down which combinations are approved. For example: “Primary background with white text: approved. Accent with white text: not approved, use for icons only.”
Step 5: Put the palette into theme.json
In a block theme, or a classic theme with theme.json support, define the palette as presets:
Setting defaultPalette and custom to false removes WordPress’s default colours and the custom colour picker, so editors can only choose from your approved palette. That’s one of the most effective ways to keep a site accessible over time, because editors can’t accidentally pick light yellow text.
Then set global styles, such as body text colour, link colour and button colours, using these presets so everything references the same tokens.
Links
Links need special attention. WCAG requires that links within text are distinguishable from surrounding text by more than colour alone, unless the colour difference itself has at least 3:1 contrast with the surrounding text, plus a non-colour indicator on hover and focus. The simplest approach is to underline links in body text. Underlines are familiar, clear and avoid the problem entirely.
Navigation menus and buttons, where the context makes clear they’re interactive, don’t need underlines.
Button states
Each button state needs to work:
- Default: text on the button background passes 4.5:1
- Hover: still passes, and visibly different from default
- Focus: a clearly visible focus indicator with 3:1 contrast against the surrounding background
- Disabled: often uses low contrast, which is permitted for disabled elements, but make sure it’s obviously disabled
Outline buttons need a border with 3:1 contrast against the background.
Text on images
Text over photographs is a frequent contrast failure, because image brightness varies. Solutions:
- A semi-transparent dark overlay between the image and text
- A solid background box behind the text
- Placing text beside the image rather than on it
Test with the actual image, and remember that responsive layouts may place text over a different part of the image on mobile.
Don’t rely on colour alone
Colour should never be the only way information is conveyed. Error fields marked only in red are invisible to many colour-blind users. Add icons, text messages and borders. Charts should use patterns or labels as well as colour.
Documenting the palette
Write the palette down where designers, developers and editors can all find it. A simple page showing each colour swatch, its name, its hex value, its role and the approved text and background pairings with their contrast ratios is enough. Many teams put this on a hidden page on the site itself, built with the real blocks, so it always reflects what’s actually in the theme. When someone wants to add a new colour for a campaign, the document makes it easy to check whether an existing colour will do, or whether the new one needs accessible variants first.
Re-test after changes
Recheck contrast whenever the brand refreshes its colours or a new section style is added. Small shifts in a hex value can move a combination from passing to failing without anyone noticing.
Check the editor too
Make sure the editor shows the same colours as the front end, so editors see real contrast while writing. An accessible colour palette is one of the few design decisions that improves every page at once.
Frequently asked questions
Do I have to change my brand colours?
Rarely. You usually keep them and add darker or lighter variants for text and interactive elements, keeping the original for logos and decoration.
Is AA or AAA the right target?
AA is the standard required by most regulations and is a sensible target. Meeting AAA for body text is a good bonus where possible.
Does dark mode need its own palette?
Yes. Colours that work on white rarely work on dark backgrounds. Define a separate set of values for dark mode and test them all again.
Can editors still break contrast?
Less easily if you disable custom colours and only offer approved presets. Some combinations may still fail, so document which pairings to use.




