
A brand colour can look excellent on a presentation slide and become difficult to use on a website. Pale lettering disappears against a photograph. A bright accent works as a decorative stripe but makes a poor background for a small button label. A form looks tidy until an error appears in a shade that some visitors cannot distinguish.
These are practical design problems worth resolving before a website build. An accessible brand colour system gives designers and editors usable combinations, rather than a handful of swatches and instructions to make them work everywhere. The following process helps business owners commission that system and review the result without pretending that a colour check alone establishes website accessibility.
Start with the jobs your colours must do
Collect examples of the things customers actually read and use: service descriptions, enquiry buttons, navigation, prices, form instructions, confirmation messages and downloadable documents. Include real copy. A two-word sample heading will not reveal the problems created by a long service name or an explanatory paragraph.
Then separate identity colours from interface roles. Your signature colour can remain prominent in photography, graphics and large decorative areas while another approved colour handles body text. This lets the brand stay recognisable without making every element carry the same visual treatment.
A useful starting list of roles includes page background, standard text, secondary text, links, button background, button label, borders, error messages and confirmation messages. Give each role a name that describes its purpose. Editors can understand “text on dark backgrounds” more readily than an unexplained numbered swatch.
Check colour pairs, not colours in isolation
Contrast depends on the relationship between foreground and background. Under WCAG 2.2’s minimum text contrast criterion, ordinary text generally needs a contrast ratio of at least 4.5:1, while large text needs at least 3:1. Large text means at least 18 point, or 14 point when bold. The criterion includes exceptions, including text that forms part of a logo. See the W3C explanation of minimum contrast.
The practical implication is to review combinations at their intended sizes. Do not approve a palette because the colours look sufficiently different on a designer’s monitor. Ask for measured results for the actual pairings and record which uses are allowed.
For example, an illustrative palette might allow dark navy text on a pale background, reserve a vivid accent for decorative panels, and use a darker variant for links. Those are design options to test, not pre-verified combinations. Exact colour values, backgrounds and type treatments still need checking.
Preserve recognition without forcing one colour everywhere
A business does not necessarily need a complete rebrand because one existing combination is unsuitable for website text. First look at how much recognition depends on that exact pairing. The logo, imagery, layout, language and repeated graphic shapes may already carry much of the identity.
Ask the designer to develop a small set of functional variants. A darker text shade can sit alongside a brighter signature shade. A neutral background can support detailed information while coloured sections introduce services. A reverse logo can work on a dark panel without turning every paragraph into light text.
The decision should be documented in the brand guide, so another supplier does not undo it later. Branding Experts’ brand strategy and identity service connects visual identity with its practical applications. A project brief can specifically ask for colour usage rules that carry through to the website, rather than stopping at the logo files.
Build a small colour-usage matrix
A matrix is a simple way to make the system usable. Put approved backgrounds down one side and common content roles across the top. Record the foreground colour, intended text size, measured contrast and any limitations. Keep the working measurement file alongside the brand guide so future changes can be checked.
- Standard content: paragraph text, headings and captions on the main page background.
- Dark sections: headings, supporting copy and links inside a reversed panel.
- Action controls: button labels in default, hover, focus and other relevant states.
- Feedback: errors, warnings and success messages with wording and any supporting symbols.
- Campaign material: text over photographs, promotional graphics and downloadable PDFs.
Keep the approved choices limited enough to use consistently. A long list of nearly identical shades creates unnecessary judgement calls. Include a few “do not use” examples where an attractive pairing fails in a common application.
Make meaning understandable without colour alone
Colour can reinforce information, but it should not be the only way to identify an action, response or distinction. W3C’s use-of-colour guidance explains this requirement. In practice, a form error needs useful text rather than just a red border, and a status display needs labels rather than unexplained green and amber dots.
Review the language as carefully as the visual treatment. “Please enter your email address” tells the customer how to continue. “Invalid” leaves them guessing. Likewise, a selected service option can include a clear selection indicator and readable name rather than relying on a subtle background change.
For a business comparison table, put the included features into words. Visitors should not need to decode a legend of coloured blocks to understand a proposal. If a chart appears in a report, label the series or provide an accompanying explanation that preserves the important information.
Review components in context
Request sample page sections before approving the colour system. A service introduction, navigation menu, enquiry form and footer provide a more useful test than an isolated mood board. Use a narrow screen as well as a wide one, and check longer content that wraps onto several lines.
Pay particular attention to photographs and gradients. A text colour that works over one part of an image may become unreadable over another. Ask how the design will behave when a future editor uploads a different photograph. An approved solid text panel may be more reliable than a complex overlay that depends on careful image selection every time.
W3C’s accessibility tips for designers also cover visible interactive elements, consistent navigation, labelled forms and layouts for different viewport sizes. These checks belong in the website design conversation alongside colour. Passing a few contrast tests does not demonstrate that every interaction works for disabled users.
Agree the handover and maintenance rules
Ask for the editable source of the palette, a short usage guide, the tested component examples and a named owner for future changes. If the website uses reusable design settings, confirm that those settings reflect the approved roles. Editors should not have to remember hexadecimal values or recreate button styles manually.
Make the approval process specific. Who can introduce a new colour? Who tests a new promotional banner? What happens when a third-party booking widget has different controls? These questions help the team recognise which changes need design or development review instead of treating every page update as harmless.
After launch, include representative pages in periodic checks, especially after theme changes, new forms or campaign templates. Record issues by the affected component and customer task. That gives the team a repair list they can act on, rather than a vague instruction to make the website more accessible.
What to put in your next design brief
Ask for a recognisable identity with tested text and background combinations, clear rules for functional colours, sample components and an editor-friendly handover. State the accessibility target and ask what evaluation is included. If specialist accessibility testing is needed, agree that scope explicitly; do not assume a visual design review covers it.
When planning website design and development, bring the existing brand files and examples of problem pages. The useful outcome is a system that customers can read and the business can maintain. That is a stronger approval standard than choosing the palette that looks best on a single presentation slide.
