Compliance
Annual Reports and Budget Documents: How to Make Long, Data-Heavy PDFs Accessible
The annual report and the budget book are the documents residents, journalists and oversight bodies most want to read, and often the least accessible things an agency publishes. They are long, they mix text with tables and charts, and they are usually produced in a hurry by several people against a deadline.
A 200-page document that cannot be navigated with a screen reader is not just inconvenient. It hides public money from people who have a right to see how it is spent.
Why do these documents fail so often?
Three features of annual reports and budgets cause most problems:
- They are designed, not written. Layout software places text boxes and graphics freely, and the export to PDF may carry no structure at all.
- They are assembled from many sources. One department supplies a table pasted as an image, another a chart from a spreadsheet, another a scanned signature page.
- They are long. Even a small structural flaw repeats on every page.
The result is a file with no headings, a reading order that jumps between sidebars and body text, and tables that read as a stream of numbers with no row or column context.
What does an accessible long report need?
Start with the basics from the PDF remediation guide and add what length demands.
- A real heading structure. Headings should nest logically, so a user can jump through the document. This supports WCAG 1.3.1 (Info and Relationships) and 2.4.6 (Headings and Labels).
- Bookmarks. For long PDFs, WCAG 2.4.5 (Multiple Ways) is met in part by a bookmark panel that mirrors the heading structure. Generate them from headings, then check them.
- A working table of contents with links that go to the right place.
- Correct document title and language, set in the document properties (WCAG 2.4.2 and 3.1.1).
- Page numbers that match. Printed page numbers and PDF page numbers often differ; make sure a reference to “page 42” points to the right place.
- Artifacts marked. Running headers, footers, decorative lines and background graphics should be hidden from assistive technology so they are not read on every page.
How do you handle financial tables?
Budget tables are the hardest element. A table that looks clear on screen can be meaningless when read out cell by cell.
- Mark header cells for rows and columns, and make the scope clear.
- For tables with merged cells or multi-level headings, use the structure that associates each data cell with its headers, or simplify the layout.
- Never present a table as an image. A screenshot of a spreadsheet gives a screen reader nothing.
- State units such as thousands or millions in the table title or header, not only in a footnote the reader might miss.
- Keep totals and subtotals identifiable so a user can find them.
Accessible data tables and dashboards goes deeper on table and chart structure for the web.
What about charts and graphs?
A chart communicates by shape and colour. The accessible version has to communicate the same thing in words and numbers.
- Give each chart a short alternative text that names it and states the main finding.
- Provide the underlying data in an adjacent table or in an appendix, so the full detail is available.
- Do not rely on colour alone to separate series (WCAG 1.4.1) and check contrast for chart elements (WCAG 1.4.11, Non-text Contrast). Check the actual contrast ratios, not just the look.
Alt text best practices explains what makes a description useful rather than decorative.
How do you prioritize across a big document set?
You do not have to fix everything at once, and you should be honest about what is not fixed. A sensible order:
- Documents residents are asked to act on or rely on, such as notices and forms.
- Current-year reports and budgets, before archives.
- Documents with high traffic in your analytics.
- Everything else, with a visible way to request an accessible version.
Triaging a legacy PDF backlog explains this approach, including how some archived material may be treated differently. Accessible board meeting documents applies it to agendas and packets.
What changes when the report is translated?
An annual report is a natural candidate for translation, because it explains services to the whole community. Translation of a designed document brings its own risks.
- Layout breaks. Translated text is longer or shorter than the original, so text boxes overflow, tables reflow and page numbers change. The table of contents and bookmarks must be rebuilt.
- Numbers and dates may need local formatting, and currency and unit notes must be checked.
- Chart labels and alt text need translation, not just the body text.
- Language tags must be set for every translated document and for foreign-language names inside English text (WCAG 3.1.2). Translated documents that fail WCAG 3.1.2 explains this.
- Right-to-left languages require a rebuilt layout rather than a mirrored one. See Arabic and RTL accessible PDFs.
Translating first and remediating afterwards is cheaper than the reverse, because a fixed English file does not carry its accessibility into a translated copy.
Where Taika fits
We remediate long reports and budget documents, including table structure, bookmarks, charts and alternative text, and we translate and rebuild them in your residents’ languages so each version is accessible. Tell us if your source files are available, because working from the original design files is faster and gives better results than repairing a flattened PDF. We meet and exceed ISO 17100, 9001 and 27001 standards.
Have a report to publish? Send us the page count, the number of tables and charts, the languages you need, and whether you have the source layout files, then request a quote. Our document accessibility page explains how we scope long-document remediation.
Need this done right?
Taika Translations provides certified translation, interpretation, and accessibility services in 300+ languages.