SwitchPDF
All articles
General July 11, 2026 4 min read

Making PDFs Accessible for Screen Readers (Without Adobe)

PDF accessibility is required by law in many contexts. Here's what makes a PDF screen-reader-friendly and how to fix common issues.

Most PDFs are technically readable by screen readers but practically useless without proper structure. Here's what makes the difference — and how to get there.

What screen readers need from a PDF

For a blind or low-vision user to actually use your PDF, the file needs:

  • Real text — not scanned images. Screen readers can't read pixels.
  • Logical reading order — paragraphs in document flow, not random screen positions
  • Proper headings — marked as h1, h2, h3 so users can navigate by section
  • Alt text for images — descriptions of what images depict
  • Form field labels — so users know what each field is for
  • Language tags — so the screen reader uses the right pronunciation

A PDF with all these is "tagged" — has accessibility tags that screen readers interpret.

How to check accessibility

On Mac: Open the PDF in Preview. If text selects normally and the document feels structured, it's at least partially accessible. For real testing, use the VoiceOver screen reader (Cmd+F5) and listen.

On Windows: Adobe Acrobat Reader has an Accessibility Check feature (Tools → Accessibility → Accessibility Check). Other free tool: PAC (PDF Accessibility Checker) from access-for-all.ch.

Common accessibility failures

1. Scanned PDF with no OCR

Problem: Screen reader sees an image, says nothing useful.

Fix: Run OCR PDF. Adds a text layer that screen readers can read.

2. Untagged PDF (exported from older software)

Problem: Screen reader reads text but doesn't know which is heading vs body vs list item.

Fix: Re-export from the source application with accessibility tags enabled:

  • Word: File → Save As → PDF → Options → "Document structure tags for accessibility"
  • Google Docs: File → Download → PDF Document (tagged by default)
  • LibreOffice: File → Export as PDF → "Tagged PDF (add document structure)"

For PDFs you can't re-export, Acrobat Pro can manually add tags. Free tools are limited here.

3. Reading order doesn't match visual order

Problem: PDF has columns or sidebars, screen reader reads them in the wrong sequence (e.g., reads main text then sidebar text mixed together).

Fix: Acrobat Pro's Reading Order tool. Free alternative: re-export from source with simpler layout.

4. Images without alt text

Problem: Screen reader says "image" with no description.

Fix: In the source document, add alt text to every image:

  • Word: Right-click image → Edit Alt Text
  • PowerPoint: Same
  • Re-export to PDF

5. Forms without labels

Problem: User hears "text field" instead of "Email address."

Fix: Re-create the form in Word or InDesign with proper labels, then export. Acrobat Pro can add labels manually if you can't re-export.

When accessibility is legally required

  • Government websites (Section 508 in the US, Web Content Accessibility Guidelines globally)
  • Higher education materials in most jurisdictions
  • Healthcare documents (HIPAA + accessibility regulations)
  • Public-facing financial documents in many countries

Failure to provide accessible documents can lead to lawsuits. For public-facing PDFs, build accessibility in from the start.

Bottom line

Start from a tagged-PDF export (Word, Google Docs, LibreOffice all do this). Run OCR PDF on scanned content. Add alt text in the source application. For complex tagging fixes, Acrobat Pro is the practical option — free tools are limited here.

Related articles