PDF Accessibility: Making PDFs Screen Reader Friendly
Mike ยท ยท 9 min read
Most PDFs look fine on screen โ but for the roughly 7.6 million Americans who are blind or have low vision, a poorly structured PDF can be completely unreadable. Screen readers like JAWS, NVDA, and VoiceOver don't read what a document looks like โ they read the underlying structure. If that structure is missing or wrong, users get a jumbled mess, or silence.
The good news: making a PDF accessible isn't complicated once you know what to fix. This guide covers the key requirements, how to check your current PDFs, and how to correct the most common problems โ without expensive software.
What Makes a PDF "Accessible"?
An accessible PDF is one that assistive technologies can read, navigate, and interact with in a meaningful way. The standard most organizations follow is WCAG 2.2 AA (Web Content Accessibility Guidelines) and the PDF/UA-1 specification (ISO 14289). In practice, an accessible PDF must have:
- Real, selectable text โ not a scanned image of text. Screen readers can't read images.
- PDF tags โ structural markers that tell assistive tech what each element is (heading, paragraph, list, table, figure, etc.).
- Logical reading order โ the order content is read aloud should match the visual order on the page.
- Alt text on images โ a text description of any image that conveys meaning. Decorative images should be marked as artifacts so they're skipped.
- Proper heading structure โ H1, H2, H3 etc. used correctly, so users can skim by jumping between headings.
- Accessible form fields โ if the PDF has forms, every field needs a label.
- Sufficient color contrast โ text should have at least a 4.5:1 contrast ratio against its background.
- Document language set โ so screen readers use the correct pronunciation rules.
- A document title โ the document properties should have a meaningful title, not just the filename.
Miss any of these, and the experience for a screen reader user ranges from frustrating to completely inaccessible.
Step 1: Check Whether Your PDF Has Real Text
The first thing to check is whether your PDF contains actual text or just images. This is especially common with scanned documents.
Here's a quick test:
- Open the PDF in any PDF viewer.
- Try to click and drag to select some text on the page.
- If you can highlight individual words, you have real text. If the entire page gets selected as a single image, the PDF is image-only.
If your PDF is image-only: You need to run OCR (Optical Character Recognition) first to extract the text layer. See our guide on how to make a PDF searchable with OCR to fix this before doing anything else. Without real text, no accessibility fix will work.
Step 2: Check for PDF Tags
PDF tags are invisible structural markers embedded in the file. They're what screen readers actually interpret. A PDF without tags is like a webpage with no HTML โ the content might be there, but without structure it's impossible to navigate.
To check if your PDF is tagged:
- In Adobe Acrobat Reader: Go to File โ Properties โ Description tab. Look for "Tagged PDF: Yes" in the Advanced section.
- In a browser: Open the PDF, right-click โ "Open in PDF viewer". If headings, lists, and paragraphs are clearly structured in the accessibility tree, it's likely tagged.
- Quick test: If you paste the PDF text into a text editor and it comes out in the correct reading order (not scrambled columns), the tagging is likely reasonable.
Step 3: Fix the Most Common Accessibility Issues
Problem: No Tags (Untagged PDF)
If a PDF was created by printing to PDF from a browser or old application, it often arrives untagged. The fix depends on your source:
- Microsoft Word / PowerPoint: Re-export the original document using File โ Save As โ PDF, and check the "Document structure tags for accessibility" option in the export settings. This is by far the most reliable method โ fix it at the source.
- Google Docs: Use File โ Download โ PDF Document. Google Docs exports reasonably tagged PDFs for simple documents.
- Adobe InDesign: Export with "Tagged PDF" enabled and map your paragraph styles to heading levels before exporting.
- Scanned documents: Run OCR first, then add tags โ or use a remediation service for large volumes.
Problem: Wrong Reading Order
Multi-column documents, sidebars, and complex layouts often have a scrambled reading order in the PDF tag tree. The visual layout might look correct, but a screen reader reads columns left-to-right across the page instead of down each column.
For example: imagine a two-column newsletter where column 1 discusses topic A and column 2 discusses topic B. A screen reader with a bad reading order might read: "Topic A headline, Topic B headline, first sentence of A, first sentence of B..." โ completely incoherent.
Fixing this typically requires Adobe Acrobat Pro's Reading Order tool or a PDF accessibility remediation tool. In Acrobat Pro: View โ Show/Hide โ Navigation Panels โ Reading Order, then drag the tagged elements into the correct sequence.
Problem: Images Without Alt Text
Any image that conveys meaning โ a chart, photo, diagram, logo โ needs a text description so screen reader users know what it shows. Purely decorative images (divider lines, background textures) should be tagged as "Artifact" so the screen reader skips them.
Good alt text describes what the image communicates, not just what it looks like. Instead of "Bar graph image," write "Bar graph showing sales growth from $1.2M in Q1 to $1.8M in Q4 2025."
Problem: Form Fields Without Labels
PDF forms are a frequent accessibility failure. A form field that visually shows "First Name" next to it will read as a blank input to a screen reader if the label isn't programmatically attached to the field.
When creating forms, use proper form-building tools that attach labels correctly. If you're fixing an existing PDF, Acrobat Pro lets you edit field properties to add tooltip text, which functions as the accessible label.
Problem: Missing Document Title
When a screen reader user opens a PDF, the first thing announced is the document title. If this is empty, they hear the filename โ often something unhelpful like "Doc_v3_FINAL_PRINT.pdf."
Set a meaningful title in the document properties. In most PDF creation tools, this is under File โ Properties or Document Settings before export.
Step 4: Test Your PDF with a Screen Reader
The only way to truly know if a PDF is accessible is to test it with actual assistive technology. Here are free options:
- NVDA (Windows, free): Download from nvaccess.org. Open your PDF in a browser or Adobe Reader and press Ctrl+Home, then let NVDA read through it. Press H to jump between headings.
- VoiceOver (Mac / iPhone, built-in): Enable VoiceOver in System Settings โ Accessibility. Open the PDF in Preview and use VoiceOver to navigate.
- TalkBack (Android, built-in): Enable TalkBack and open the PDF in Google Drive or Chrome.
When testing, ask yourself: Does reading order make sense? Can you navigate by headings? Are images described? Can you fill out forms without visual reference?
Step 5: Use an Automated Checker
Manual testing is important, but automated checkers catch structural issues quickly:
- PAC 2024 (PDF Accessibility Checker) โ free tool that checks against PDF/UA-1 and WCAG 2.2 criteria. Reports specific failures with page numbers.
- Adobe Acrobat Pro Accessibility Check โ built-in checker under Tools โ Accessibility โ Full Check.
- WAVE โ if your PDF is embedded on a webpage, WAVE can flag accessibility issues in the surrounding context.
Run automated checks first to get a baseline, then do manual screen reader testing to catch issues automated tools miss (like alt text that technically exists but is completely uninformative).
Quick Checklist Before Publishing a PDF
- โ Text is real and selectable (not an image)
- โ Document is tagged (Tagged PDF: Yes)
- โ Heading levels (H1, H2, H3) are used correctly
- โ Reading order is logical, top to bottom
- โ All meaningful images have alt text
- โ Decorative images are marked as artifacts
- โ Form fields have descriptive labels
- โ Document language is set
- โ Document title is set in properties
- โ Tested with a screen reader
- โ Passed automated accessibility check
Legal Requirements: Who Needs to Worry?
In the United States, PDF accessibility requirements apply broadly:
- Federal agencies and contractors โ Section 508 of the Rehabilitation Act requires all electronic documents to be accessible. This was updated in 2017 to align with WCAG 2.0 Level AA.
- State and local governments โ Title II of the ADA now explicitly covers web content and documents, following 2024 DOJ regulations that cite WCAG 2.1 AA.
- Private businesses โ Title III of the ADA covers places of public accommodation, which courts have increasingly applied to websites and documents.
- Educational institutions โ Section 504 and Title II of the ADA require accessible course materials.
Even if none of these apply to you directly, accessible PDFs rank better in search engines (Google can index tagged content more accurately), load more reliably on all devices, and simply work better for everyone โ including users on mobile, low-bandwidth connections, or who just prefer keyboard navigation.
The Easiest Fix: Start With an Accessible Source
Retrofitting accessibility into existing PDFs is time-consuming. The most efficient approach is to build accessibility in from the start:
- Use heading styles in Word, Google Docs, or InDesign (not just big bold text).
- Add alt text to images before exporting.
- Export to PDF using the accessibility-preserving export option (not "Print to PDF").
- Run a quick automated check before distributing.
Five minutes of attention during creation saves hours of remediation later.
Need to Edit an Existing PDF?
If you're working with PDFs that someone else created โ EditPDFs.app lets you edit text, add annotations, reorganize pages, and more, directly in your browser. No software to install, no account required. For PDFs that need OCR to become searchable, the OCR guide here walks through the process.
Accessible PDFs aren't just the right thing to do โ they're better documents, full stop. Clear structure, searchable text, and logical organization make any PDF easier to use for everyone.
