Why Annual Reports Must Be Accessible
Annual reports are public-facing documents that communicate an organisation's performance, strategy, and governance to shareholders, regulators, and the wider public. For financial services firms, listed companies, and public bodies, they are often a regulatory requirement.
The European Accessibility Act requires accessible digital content for EU consumers. An annual report published on a company website, distributed to investors, or filed with a regulator in PDF format falls within this scope.
Beyond the legal obligation, accessible annual reports serve a wider audience. Investors and analysts using assistive technologies need the same access to financial data, strategic commentary, and governance disclosures as any other reader.
Accessibility Challenges in Annual Reports
Annual reports are designed to be visually compelling — which often creates accessibility challenges. The more complex the design, the more work is required to make the document accessible.
Complex Multi-Column Layouts
Annual reports frequently use two or three-column layouts with pull quotes, sidebars, and callout boxes. Without a defined reading order, assistive technologies present this content in the wrong sequence — reading across columns instead of down them.
Charts, Infographics & Data Visualisations
Financial charts, performance graphs, and infographics convey critical information visually. Each requires meaningful alternative text that describes what the visual communicates — not just “chart” or “graph” but the trend, comparison, or key data point it illustrates.
Embedded Tables & Financial Data
Financial statements, balance sheets, and performance tables require proper header-cell associations. Complex tables with spanning cells, nested headers, or multiple levels of hierarchy need careful structure to be navigable with assistive technologies.
Design Agency Handoff
Most annual reports are produced by design agencies who prioritise visual presentation. The PDF exported from InDesign, Illustrator, or other design tools often lacks any accessibility structure. The remediation work typically happens after the design is finalised, creating a separate workstream.
Large File Sizes & Page Counts
Annual reports routinely run to 100+ pages with high-resolution images and embedded fonts. The size and complexity make manual remediation slow and expensive — a single report can take days of specialist work.
Annual Report Accessibility Requirements
To meet European Accessibility Act compliance, annual reports must satisfy the following requirements:
Document Structure & Headings
A clear heading hierarchy (H1 for the report title, H2 for major sections, H3 for subsections) that reflects the logical structure. Assistive technology users navigate annual reports primarily by heading, so the hierarchy must be accurate and complete.
Table Markup for Financial Data
Balance sheets, income statements, and performance tables must have tagged header cells with proper associations. Complex tables with merged cells need row and column scope attributes.
Alternative Text for Charts & Graphics
Every chart, graph, and infographic needs alt text that describes the information conveyed — trends, key figures, comparisons. Purely decorative images and backgrounds must be marked as artefacts.
Reading Order Through Complex Layouts
The tag structure must define a logical reading sequence through multi-column layouts, sidebars, and callout boxes. The reading order may differ significantly from the visual layout.
Bookmarks & Navigation
Long reports must include bookmarks for all major sections, enabling users to navigate directly to the content they need without scrolling through 100+ pages sequentially.
Language Tags
The document language must be declared. If the report contains content in multiple languages, language changes must be tagged at the element level.
Design vs Accessibility: Working with Design Agencies
Annual reports are typically produced by external design agencies who create visually polished layouts in InDesign or similar tools. The challenge is that the PDF exported from these tools rarely includes accessibility structure.
There are two approaches to resolving this:
Accessible at Source
Train the design agency to create accessibility-ready PDFs from the outset — using tagged headings, proper export settings, and structured layouts. This is the ideal but requires the agency to have accessibility expertise.
Post-Design Remediation
Remediate the PDF after design is complete. This is the more common approach — the design agency delivers the final visual PDF, and remediation adds the accessibility structure afterwards. ComplyLoft automates the bulk of this work.
In practice, most organisations use post-design remediation because it does not require changes to the design workflow. The trade-off is that certain issues — particularly colour contrast and tables that span pages without repeating headers — must be addressed at the design stage and cannot be fixed in remediation.
How ComplyLoft Makes Annual Reports Accessible
The ComplyLoft Accessibility tool handles the heavy lifting of annual report remediation — tagging complex layouts, structuring tables, repairing reading order, and prompting for alternative text on charts and graphics.
- •Automated tagging of complex multi-column layouts and nested content
- •Table structure repair with header-cell associations for financial data
- •Reading order repair through design-heavy pages
- •Detection and flagging of images requiring alternative text
- •Validation against WCAG 2.1 AA and PDF/UA standards
For complex design-heavy documents like annual reports, ComplyLoft typically remediates to approximately 90% accessibility. The remaining work — reviewing alt text quality, confirming reading order through unusual layouts, and verifying complex table structures — is completed by an accessibility specialist.
ComplyLoft automates the groundwork. A qualified human always reviews, adjusts where needed, and signs off on all outputs. ComplyLoft does not guarantee compliance.