In short
A brand palette needs fewer colours than most decks contain: one primary, one accent used sparingly for interaction, a considered neutral range, and semantic colours for success, warning and error. Check contrast before committing rather than after, because a primary colour that cannot carry text at accessible contrast will constrain every design that follows.
Fewer colours than you think
A workable palette is small:
One primary carrying brand recognition.
One accent, used sparingly. Its power comes from scarcity — a colour appearing everywhere signals nothing.
A neutral range, from near-white to near-black, in several steps. This is where most of an interface actually lives, and it is the part palettes usually neglect.
Semantic colours for success, warning, error and information. These are separate from your brand colours, because a red brand colour cannot also mean error.
That is roughly four decisions plus a neutral scale. Palettes with twelve equally weighted brand colours produce materials with no hierarchy, because nothing is distinguished when everything is coloured.
Choose neutrals deliberately
The most under-considered part, and the one that determines whether materials feel considered.
A pure grey reads as unconsidered. A neutral with a slight hue bias toward your primary reads as chosen, and holds the palette together. The difference is subtle in isolation and obvious across a whole page.
Build a proper scale — several steps from lightest to darkest — rather than picking two greys. Interfaces need more neutral steps than brand colours: borders, backgrounds, disabled states, secondary text, dividers.
Check accessibility before committing
This is the step that must happen early, because it constrains everything downstream.
Body text needs a contrast ratio of at least 4.5:1 against its background. Large text needs 3:1. Interface components and meaningful graphics need 3:1.
The common failure: a mid-tone brand colour that looks excellent as a large block and cannot carry white or black text at accessible contrast. Discovering that after the palette is approved means either breaking the rules or adding a colour that was not in the brand.
Test the actual combinations you will use — text on primary, primary on white, accent on dark, disabled states — not just the swatches side by side. A palette is a set of relationships, not a row of colours.
If the primary cannot carry text, that is fine as long as you know: it becomes a colour for blocks and marks, and a darker variant carries text. Deciding that deliberately is very different from discovering it later, and it is why accessible contrast belongs in the palette stage rather than in review.
Never rely on colour alone
A significant share of people cannot distinguish certain colour pairs, and everyone loses colour information in bright sunlight or on a poor screen.
So any meaning carried by colour needs a second signal — an icon, a label, a position, a weight change. A red border indicating an error needs the error message. A green dot indicating status needs a word.
This is not only accessibility. It makes interfaces more legible for everyone in imperfect conditions, which is most conditions.
Meaning is contextual
Colour associations vary by culture and by industry, and the standard advice about what colours mean is mostly folklore.
What is worth checking: whether your palette resembles a competitor's closely enough to cause confusion, whether it accidentally matches a political party or a rival in a market you serve, and whether the semantic colours read correctly in your markets — red and green for negative and positive is not universal in financial contexts.
Beyond that, colour acquires meaning through consistent use, much as a name does. Distinctiveness matters more than symbolism.
Test where it will actually be used
A palette approved on a calibrated display in a bright room behaves differently elsewhere.
Check it on a phone outdoors, on a cheap monitor, printed, and in dark mode if you support one. Colours that are distinguishable on a good screen can collapse into each other on a bad one.
If print matters, check the colours are reproducible — some vivid screen colours cannot be printed and will shift noticeably.
Document it as decisions, not swatches
A palette document listing hex codes is not enough. What people need is what each colour is for.
Which colour do headings use? Which is for interactive elements only? What is the background hierarchy? Which colours never touch each other?
Without that, everyone applies the palette differently and the brand drifts while technically staying on-palette.
Better still, encode it. Colours defined as design tokens with semantic names — surface, text, border, interactive — are applied correctly by default, and the document shrinks to explaining the reasoning.
A workable process
Start with the primary, chosen for distinctiveness in your market. Test whether it can carry text; decide its role accordingly. Build a neutral scale biased slightly toward it. Choose an accent that stands out against both, reserved for interaction. Add semantic colours checked against your background range. Verify every real combination for contrast. Then write down what each is for.
That sequence puts the constraints first, which is what prevents the palette being redesigned after the first accessibility review.
If you are building a palette that has to work across a site and a product, book a call.
Common questions
How many colours should a brand have?
Fewer than most palettes contain: one primary, one accent used sparingly, a proper neutral scale of several steps, and semantic colours for success, warning and error. Palettes with a dozen equally weighted brand colours produce materials with no hierarchy, because nothing stands out when everything is coloured.
When should accessibility be checked in a palette?
Before committing, because it constrains everything downstream. Body text needs 4.5:1 contrast and interface components 3:1, and a mid-tone brand colour that looks excellent as a block often cannot carry text at accessible contrast. Test real combinations rather than swatches side by side.
What if our brand colour fails contrast requirements?
That is workable as long as you decide it deliberately: the colour becomes one for blocks and marks, and a darker variant carries text. The problem is only discovering it after the palette is approved, when you either break the rules or add a colour that was never in the brand.
How do you choose neutral colours?
Deliberately, with a slight hue bias toward the primary rather than pure grey, which reads as unconsidered. Build a full scale of several steps rather than picking two greys — interfaces need more neutral steps than brand colours for borders, backgrounds, disabled states and secondary text.
Do colours mean the same thing everywhere?
No, and most advice about colour meaning is folklore. What is worth checking is whether your palette closely resembles a competitor's, whether it matches something unintended in a market you serve, and whether semantic colours read correctly — red and green for negative and positive is not universal.
