Creating Accessible PDF Documents

An accessible PDF can be read by a screen reader, navigated by keyboard, zoomed without falling apart, and understood by someone who never sees the page the way you do. That covers far more than blind readers: people with low vision, motor impairments, dyslexia, or simply a phone-sized screen rely on the same structural signals.

Accessibility in PDF is not a visual style — the document can look exactly as it does today. It is hidden structure: a tag tree that says which text is a heading, which order the content should be read in, and what an image means. Without that structure, a PDF is a picture of a document rather than the document itself.

Tags are the backbone. Every paragraph, heading, list item, table cell, and image should carry a tag that names its role — H1 for the title, H2 for sections, P for body text, L and LI for list items. Assistive technology uses those roles to announce context: a reader hearing “heading level 2, Security Checklist” knows exactly where they are.

Reading order is the second half. A screen reader follows the tag tree, not the visual layout, so a document whose tags run in the order things were added — not the order they appear — will narrate a sidebar before the paragraph it sits beside. Multi-column layouts are the usual trap; the tag tree should run top to bottom, left to right, and repair is needed whenever the two disagree.

Every meaningful image needs alt text that conveys its information rather than its appearance: “revenue up fourteen percent year over year” beats “line chart”. Decorative images should be marked as artifacts so screen readers skip them. Charts and diagrams often deserve a short description in the surrounding text as well, because alt text has limits.

Links should say where they go — “view the pricing page”, never “click here” — so they make sense when read in isolation from the sentence around them. Keep sufficient color contrast, never encode meaning in color alone, and avoid text baked into images, which no reader can reflow or enlarge.

Accessibility is verifiable. Run this pass before a document goes out:

1. Run an accessibility checker and clear every error it reports — missing tags and missing alt text are usually the top two.
2. Read the document with the tag panel open: does the tree match the visual order on every page?
3. Set the document language so screen readers pronounce it correctly, and give the file a real title so it is identifiable when open.
4. Navigate by keyboard alone: can a reader reach every link, form field, and annotation?
5. Zoom to two hundred percent and confirm nothing important is clipped or overlapping.
6. Save as PDF/UA where your toolchain supports it — the standard formalizes the checks above.