PDF

Making PDFs Accessible: What It Actually Takes

Most PDFs are accessibility disasters. Screen readers can't navigate them, tab order is wrong, and images have no alt text. Here's what accessible PDF creation actually involves.

7 min readJanuary 11, 2026By FreeToolKit TeamFree to read

Whoever invented the habit of exporting a complex Excel spreadsheet to PDF and uploading it to a website owes a debt to every screen reader user who's encountered the result. PDFs can be done right. Most aren't.

Why Most PDFs Fail Screen Readers

Printing to PDF creates a flat image of a document — no text, no structure, just pixels. Screen readers can't read images unless OCR is applied. Even 'save as PDF' from Word creates a PDF without proper tag structure if the source document uses manual formatting instead of styles.

The result: a screen reader user encounters a PDF, hears 'document' and then nothing, or gets a wall of text with no headings, no logical reading order, and no way to navigate.

The Right Starting Point: Source Document Structure

Accessibility is much easier to build in than to retrofit. In Microsoft Word:

  • Use Heading 1, Heading 2, Heading 3 styles — not bold + font size changes
  • Use actual List styles — not manual bullet characters
  • Add alt text to every meaningful image (right-click image → Edit Alt Text)
  • Use descriptive link text — 'Download the annual report' not 'Click here'
  • Run the Word Accessibility Checker before export

What 'Tagged PDF' Means

Tags are metadata embedded in the PDF that describe its structure to assistive technology. A paragraph tag tells the screen reader 'this is body text.' An h1 tag means 'this is the main heading.' An image tag with alt text tells the screen reader what the image shows.

Without tags, screen readers have no way to understand document structure. The text is present but there's no semantic meaning — it's like reading HTML with all the tags stripped out.

Testing PDF Accessibility

Adobe Acrobat Pro's Accessibility Checker is the quickest automated check. For manual testing, install NVDA (free on Windows) and navigate the PDF using only the keyboard. Try to navigate by headings (H key in NVDA). Try to read the alt text of an image. Try to submit a form using only Tab and Enter. What you encounter is what users with visual impairments experience.

Frequently Asked Questions

What makes a PDF accessible?+
Accessible PDFs have several key characteristics: tagged document structure (headings, paragraphs, lists marked so screen readers understand the hierarchy), reading order that matches visual order, alt text for all meaningful images, actual text rather than scanned images (or OCR applied to scanned content), meaningful link text (not 'click here'), properly identified form fields with labels, and appropriate document language set in properties. The PDF/UA standard (ISO 14289) defines the technical requirements. Tagged PDFs that meet PDF/UA can be navigated effectively by screen readers like JAWS, NVDA, and VoiceOver.
Can I fix an inaccessible PDF after creating it?+
Sometimes. Adobe Acrobat Pro has an Accessibility Checker and auto-tagging feature that can improve accessibility after the fact. For scanned documents without text, you'd need to run OCR first to create actual text content. Manual tagging of a complex existing PDF — fixing reading order, adding alt text, correcting tag structure — can be very time-consuming. For simple documents, Acrobat's auto-fix handles most issues. For complex reports with tables, charts, and mixed layouts, rebuilding from an accessible source document (Word or InDesign with proper structure) is often faster than remediation.
Is exporting from Word to PDF accessible by default?+
Better than you might expect, if your Word document uses proper structure. Word documents that use Heading styles (Heading 1, Heading 2, etc.) instead of manual bold/large text, have alt text on images, use proper list formatting, and have meaningful link text — these export to fairly accessible PDFs. The key is using Word's built-in structure features, not just visual formatting. When exporting, use 'Save as PDF' with the 'Document structure tags for accessibility' option checked. The resulting PDF will have the tag structure needed for screen readers.
Does WCAG apply to PDFs?+
PDFs that are part of web content need to meet WCAG 2.1 (or 2.2) success criteria, just like HTML content. For public-facing websites, this is a legal requirement in many jurisdictions under ADA (US), EN 301 549 (EU), and similar regulations. The PDF/UA standard (ISO 14289) is the technical specification for PDF accessibility, and conforming to PDF/UA typically satisfies WCAG 2.1 Level AA requirements for document accessibility. Government agencies, educational institutions, and businesses providing public services have the strongest legal exposure for inaccessible PDF content.

🔧 Free Tools Used in This Guide

FT

FreeToolKit Team

FreeToolKit Team

We build free browser-based tools and write practical guides that skip the fluff.

Tags:

pdfaccessibilitywcagdocuments