Home / Learn
By PDFWix Editorial Team · November 2025
PDF accessibility guide — how to produce screen-reader-friendly tagged PDFs that meet WCAG 2.1 and Section 508, plus a free accessibility validation checklist.
An accessible PDF rests on four pillars: a logical reading order so screen readers traverse the page in the intended sequence; real text instead of images of text so assistive tech can speak it; descriptive alt text on every meaningful image; and a declared document language so the screen reader picks the right voice and pronunciation.
Miss any one of those and the file will technically open in Acrobat but be unusable for someone navigating with a keyboard, a screen reader, or a refreshable braille display.
WCAG 2.1 is the accessibility standard most regulators (ADA in the US, EAA in the EU, AODA in Ontario) point at. For PDFs the practical translation is PDF/UA-1 (ISO 14289-1): a tagged document tree, marked-up tables with header cells, bookmarks for documents over a few pages, and explicit reading order via the Tags panel.
Adding alt text in Acrobat: open the Tags pane, right-click the figure tag, choose Properties, and fill in Alternate Text. For purely decorative images, mark them as artifacts so screen readers skip them entirely.
Adobe Acrobat Pro's Accessibility Checker (Tools → Accessibility → Accessibility Check) is the industry default but costs ~$20/month. The free alternative is PAC 2024 (PDF Accessibility Checker) from access-for-all.ch — it runs locally on Windows, audits against PDF/UA and WCAG, and produces a clickable report mapping each failure back to the offending tag.
For a quick smoke test, open the file in Acrobat Reader, press Ctrl+Shift+5 to launch Read Out Loud, and listen. If the order is wrong or images are skipped without explanation, you have work to do.
The fastest free check is PAC 2024 from access-for-all.ch — install it on Windows, drag your PDF in, and you get a per-rule pass/fail report mapped against PDF/UA and WCAG 2.1 AA in under 30 seconds. The report tells you exactly which tag is missing alt text, which heading level was skipped and where the reading order breaks.
On macOS, use Adobe's online Accessibility Checker (free to upload one file at a time) or run Acrobat Reader's Read Out Loud (Ctrl+Shift+5 / Cmd+Shift+5) and listen — if a screen reader cannot follow the page, the file is not accessible regardless of what an automated checker claims.
Exporting from Word or InDesign with the 'tagged PDF' option turned off is the single most common mistake. Without tags, the PDF has no structure at all — every heading, list and table is just visual styling to a screen reader. Turn tagging on in your authoring tool's PDF export settings.
Other frequent failures: scanned PDFs without OCR (use PDF OCR to add a real text layer), images used in place of text for headings or buttons, decorative images without an artifact tag, tables built from positioned text instead of real table tags, and missing document language metadata.
Form fields need a tooltip (Acrobat: right-click field → Properties → Tooltip) so screen readers announce 'First name' instead of 'edit text'. Required fields should be marked required, and tab order should follow the visual reading order rather than the random order Acrobat sometimes assigns.
Scanned PDFs are completely invisible to a screen reader until you run OCR. That alone moves the file from 0% accessible to roughly 70% — you still need to add tags afterwards for full PDF/UA compliance, but text extraction is the unblocking step.
Tools that preserve existing structure (Merge, Split, Compress, Extract Pages) keep the source document's tags intact. PDFWix does not yet auto-generate tags for untagged PDFs — for new tag trees, export with tagging enabled from Word or InDesign, then validate with PAC 2024.
WCAG 2.1 is the general web-accessibility standard; PDF/UA (ISO 14289) is the PDF-specific implementation. A PDF/UA-compliant file satisfies WCAG 2.1 AA for the document content, but a webpage embedding it still needs separate WCAG compliance for navigation and chrome.
OCR is necessary but not sufficient. It makes text selectable and screen-readable, but full accessibility also needs tagged headings, alt text on figures and an explicit reading order — typically added in Acrobat Pro after OCR.