If you’ve read this series from the beginning, a pattern will be clear: most accessibility failures in research organisations don’t happen at the point of publication. They happen much earlier, in decisions made about colour palettes, document templates, heading styles and chart designs – decisions that were never tested against accessibility requirements because accessibility wasn’t part of the brief.
The result is organisations that are perpetually fixing accessibility problems document by document, project by project, after the fact. It’s slow, it’s expensive, and it doesn’t solve the problem. It just manages it.
This final article in the series makes the case for a different approach: embedding accessibility into the brand system itself, so that compliant output becomes the default rather than the exception.
Why fixing it later always costs more
Retroactive accessibility remediation is one of the least efficient uses of design resource. Taking an existing PDF that wasn’t built with accessibility in mind and making it accessible requires re-examining every structural decision: heading tags, reading order, alt text, colour contrast, table headers, metadata. For a 60-page research report, that’s a significant investment.
Multiply that across an organisation publishing dozens of reports a year, and the cumulative cost of not having accessible templates becomes substantial. The same organisation could have invested once in accessible templates and eliminated most of that remediation work entirely.
The economics of accessibility are straightforwardly in favour of going upstream. Fix the system once, and the system produces accessible output by default. Fix documents individually, and you’re paying indefinitely. For research organisations, accessible brand systems are the most cost-effective intervention available.
How brand systems determine accessibility for research organisations
Brand systems determine the conditions in which documents are produced. The colour palette sets the contrast ratios available for text and data visualisation. The typography choices determine whether text is legible at small sizes and across devices. The heading hierarchy determines whether documents have navigable structure. The templates determine whether accessible output is easy or hard to produce.
When these decisions are made without accessibility in mind, they create constraints that make compliance difficult for everyone downstream. The designer trying to use the brand palette for a chart is working with colours that fail contrast checks. The researcher using the report template is working with heading styles that don’t map to proper semantic structure. The comms team producing the annual review is working with a layout that creates reading order problems in PDF export.
None of these people caused the problem. The problem was created upstream, in the brand system, and inherited by everyone who uses it.
What changes when accessibility is built in from the start
When accessibility brand systems are designed for research organisations from the outset, the downstream experience is fundamentally different.
Colour palettes are tested against WCAG contrast requirements as part of the design process, not after the fact. That means the palette that gets signed off is one that works for body text, for data visualisation, for diagrams – not one that looks great on a moodboard but fails in practice.
Typography is chosen for performance across formats: legible at small sizes, readable in long documents, functional in templates that non-designers will use. Variable fonts and font families with strong legibility at text sizes are prioritised over distinctive display fonts that only work at large sizes.
Heading hierarchies are defined as functional document structure, not just visual styling. H1, H2, H3 are assigned semantic roles and built into templates so that applying them produces structurally accessible documents automatically.
Report templates, slide decks and document systems are built with accessible output as a design criterion. Reading order is defined. Paragraph styles map to PDF tags. Chart templates use accessible colour combinations. Export settings are configured correctly.
The result is that accessibility is embedded in what the system produces, not added at the end by whoever happens to remember.
The series in a single argument
This series has moved through the specific to the systemic. Article 1 established what the regulations require and why most organisations are exposed. Article 2 looked at why university documents fail at scale. Article 3 covered where PDF production fails. Article 4 examined how brand colour decisions create chart accessibility problems. Article 5 addressed the compliance infrastructure that most organisations are missing.
The thread running through all of them is this: accessibility failures in research organisations are almost never the result of individual carelessness. They’re the result of systems that were never designed to produce accessible output. And the most effective intervention is always upstream, at the system level, not downstream at the document level.
What accessible brand systems look like for research organisations
In practice, working with Watercat Creative on a brand or document system project means accessibility is part of the design criteria from day one. That means:
- Colour palettes tested against WCAG 2.2 AA contrast requirements for text, UI and data visualisation use cases
- Typography selected for legibility across formats and tested in document contexts
- Heading hierarchies defined with semantic structure as well as visual hierarchy
- Report and document templates built with tagged heading styles, accessible chart templates and configured export settings
- Accessibility review at sign-off, not as an afterthought
The output is a brand system that makes compliant work easier to produce, consistently, across every person and project that uses it.
Accessibility isn’t a constraint. It’s a quality standard.
The organisations that treat accessibility as a constraint – something to comply with, a limitation on design freedom – end up with the most expensive and fragile compliance position. Constant remediation, inconsistent output, documents that fail audits.
The organisations that treat accessibility as a quality standard – a measure of whether their work actually functions for the people it’s meant to reach – end up with better design, more consistent output, and a compliance position that holds.
For research organisations, where the purpose of the work is to make knowledge available and useful, accessible design isn’t in tension with the mission. It’s an expression of it.
If you’re ready to approach accessibility at system level, rather than document by document, we’d like to talk.