A beautiful PDF can still be difficult to read
A PDF needs meaningful structure as well as a readable layout. Headings, logical reading order, useful text alternatives, clear links and properly structured tables help people use the document with different technologies. Build those requirements into the source file, then check the exported PDF manually and with suitable tools. A tagged export or automated pass alone does not establish accessibility.
Put the advice into practice
Make your expertise look as considered as the work behind it
Bring brand, sales material and digital design into one coherent presentation.
Discuss your design briefThe cover can look excellent while the reading experience falls apart. A screen reader may encounter a caption before its heading, a chart may have no useful alternative, or a scanned page may contain no usable text. These issues belong in the design brief, not only in a final compliance conversation.
Why does the source document matter?
Accessibility work is easier to maintain when the source contains the right structure. Use a coherent heading hierarchy, real lists and suitable table structures rather than building their appearance entirely with manual spacing. Give the document an accurate title and set the correct language.
Adobe’s InDesign accessibility guidance explains how paragraph styles, export tags and reading order support the PDF workflow. These are foundations for a usable document, not a certificate that the final output meets every reader’s needs.
Retaining a structured source also matters at the next revision. If someone changes a heading into an oversized paragraph or pastes a chart as an unexplained image, the next export can lose useful meaning even when the template still looks consistent.
What can go wrong in a two-column report?
Imagine a professional association publishing a report with two columns, a pull quote and a chart. The intended order is the section heading, the first column, the second column and then the relevant chart explanation. A visually convincing page does not establish that assistive technology will follow that sequence.
Review the reading order in the exported file and listen to representative pages with the relevant assistive technology. The pull quote should not interrupt a sentence halfway through. A chart needs an accessible explanation of the information that matters, and a complex dataset may need a suitable table or separate resource.
The explanation should convey the point, context and limitations of the chart. Repeating its decorative appearance does not help someone understand the finding. Keep the underlying figures available in a usable form where appropriate.
Which checks belong in the review?
| Area | Check in the exported document |
|---|---|
| Headings | The hierarchy describes the structure and supports navigation. |
| Reading order | Text and meaningful objects follow a logical sequence. |
| Images and charts | Relevant meaning has a suitable text alternative. |
| Tables | Headers and relationships remain understandable, including across pages. |
| Links | Link text describes the destination or action. |
| Text and contrast | Content is readable at relevant viewing settings and is not available only as an image. |
| Forms | Any fields have meaningful labels and can be operated appropriately. |
Use an automated check to identify issues it can test, then investigate the flagged items and the experience it cannot establish. A clean report is evidence about that check, not proof that every page is usable. Include manual review and appropriate user feedback in the agreed scope.
Should the information also be available as a web page?
Ask what the audience needs to do. A short service explanation or application instruction may be easier to maintain and navigate as HTML, while a designed annual report may have a useful role as a downloadable document. Offering both can be sensible when each version is maintained accurately.
Avoid treating a downloadable PDF as the only possible delivery format. W3C’s accessible-material guidance highlights the importance of adaptable formats. The appropriate choice depends on the content and the people using it.
A website summary should carry enough useful information to stand on its own and clearly identify the document it links to. Keep changes consistent across the versions rather than leaving an old PDF to contradict the current page.
What should you ask for before commissioning?
Agree the intended audience, distribution channels, accessibility target, source format, testing responsibilities and remediation process. Identify who supplies alternatives for specialist charts and who approves their accuracy. Technical checking and subject-matter checking are different jobs.
Request a documented handover of the structured source, exported file and issues resolved or still outstanding. If the content changes regularly, agree who will repeat the relevant checks after each revision. This is particularly useful for reports, policy documents and recurring publications.
The annual report design guide covers wider planning choices. Accessibility should be part of that planning so design, content and review have a shared definition of a finished document.
