In this article
Colour and type decisions that look attractive in an identity presentation may not work equally comfortably for every reader in practical use. Small explanations, text over photographs and information distinguished only through colour deserve separate attention. Accessibility does not require removing the brand’s character. It requires explaining how the visual language should behave under different conditions. This guide introduces design decisions and review questions without certifying an individual document or an organisation’s overall conformity. Relevant evaluation should enter the identity process early, rather than appear only after templates and digital components have been distributed.
Quick answer
Assess the palette through actual text and background combinations rather than isolated swatches. Consider type size, weight, spacing and information hierarchy together. Include approved combinations and problematic examples in the guide. Web text, physical printing and wayfinding do not share one evaluation environment, so each application needs appropriate review. A successful colour check is useful evidence for that check, not proof that every accessibility requirement has been addressed.
Describe colours through their practical roles
A list of brand colours does not establish that every combination is suitable. Prepare pairings for primary text, supporting text, buttons and backgrounds. A pale grey may work decoratively while creating difficulty in small copy. The guide should explain how colours perform tasks as well as identify which ones belong to the brand. Future designers and editors can then apply an approved relationship instead of making an unsupported assumption every time a new document or component is needed.
Use the web contrast criterion within its proper scope
WCAG 2.2 explains a minimum ratio of 4.5:1 for normal text and 3:1 for defined large text. Logo text is exempt from this criterion, but functional copy does not become exempt merely because it uses corporate colours. These thresholds alone do not establish complete accessibility. The relevant technical review should consider scope, the nature of the text and the actual application rather than turn one numerical result into an unconditional approval of the entire identity.
Treat readability as more than choosing a typeface
Test the relationships between size, line length and spacing discussed in the typography guide using actual copy. Very thin or tightly arranged text may make a reading task difficult even when it is considered elegant. Enlarging the heading does not resolve every body-text problem. Prepare examples for paragraphs, tables and short descriptions. Review them at the expected viewing scale instead of assessing only a highly enlarged design file under unusually comfortable presentation conditions.
Do not leave important distinctions to colour alone
Product variants, document statuses and data can use different colours, but consider how someone identifies the relationship when the colours are difficult to distinguish or the material appears in monochrome. Names, symbols, shapes or direct explanations provide possible additional cues. Every cue need not be used simultaneously. Choose around the task. Distinguish a decorative difference from information necessary for a decision so essential meaning does not disappear when one visual characteristic is unavailable.
Test identity through a hypothetical proposal page
Imagine a service proposal in which included work, additional work and notes rely on faint colours for separation. Reconsider headings, table relationships and text pairings, then examine how a reader finds the distinction. The aim extends beyond selecting a colour that crosses a threshold: the offer needs to be understandable. This is not a formal conformity test or a claim about a client outcome. It is an early exercise connecting identity decisions with a functional reading task.
Update the guide with the people applying it
Digital teams, document editors and production suppliers should know which rules apply to their work. Add examples to avoid and identify the contact for unresolved questions. Share actual problem pages and materials with BOCW. Plan appropriate specialist assessment where technical evaluation is required. The logo and core palette may remain stable while text pairings, templates or layout rules improve. Replacing the entire identity is not automatically the appropriate response to every application problem revealed during review.
Key takeaways
- Document colours alongside real text and background roles.
- Combine contrast checks with readable typography and information hierarchy.
- Review digital and physical applications in their relevant contexts.
Frequently asked questions
Must the corporate colour change?
Not necessarily. Its role, background or accompanying layout may be adapted. Identify the actual application problem before deciding which element needs revision.
Does the logo exception cover the entire page?
No. An exception for logo text does not automatically cover service descriptions or other functional copy on the same page.
Does one colour test establish complete accessibility?
No. Contrast is one area of review. Content, interaction and other relevant requirements need assessment appropriate to the actual application.
