How to Make a PDF Accessible for Screen Readers
Start with an accessible source file, export it as a tagged PDF, then check the tags, reading order, images, tables and forms. A screen reader needs more than selectable text because it also depends on document structure.
Decide if PDF is the right format
Use HTML instead of PDF for web pages, changing information and mobile-first content. HTML usually adapts better to different screens and assistive technologies.
PDF still makes sense for fixed layouts, signed forms, print-ready documents, formal reports and records. If you publish a PDF, provide an HTML version when the content serves a broad online audience.
The UK Government advises publishers to consider HTML before PDF. The US Section 508 program also explains that PDF files need accessibility features, not just visual formatting.
PDF/A does not mean accessible PDF. PDF/A supports long-term archiving, while PDF/UA addresses technical accessibility requirements.
What a screen reader needs from a PDF
A PDF screen reader workflow depends on several parts working together:
- A real text layer that assistive technology can read.
- Tags that identify headings, paragraphs, lists, tables and other structures.
- A logical reading order that matches the intended content.
- Meaningful alternative text for informative images.
- A document language and title.
- Working links with descriptive text.
- Correct table structure and header cells.
- Usable form fields with labels and a logical tab order.
- Security settings that do not block assistive technology.
A searchable PDF is not automatically accessible. Searchability usually shows that the file contains text, but it does not prove that the tags, reading order or table structure work.
Create an accessible source document first
Fixing a PDF after export takes longer than preparing the source file correctly. Use the accessibility tools in Microsoft Word, Google Docs or your design software before exporting.
Use real headings
Apply heading styles such as Heading 1, Heading 2 and Heading 3. Do not create headings only by making text larger, bold or a different colour.
A screen reader can use heading tags to move around a document. A visual change alone does not provide that structure.
Use one clear document title. Use Heading 1 for major sections, then use Heading 2 and Heading 3 in a sensible order.
Build real lists and tables
Use the software's list controls for numbered and bulleted lists. Do not type numbers or symbols manually when the content is a list.
Use a table tool for data tables. Set a header row and keep the table simple. Avoid using tables to position page elements, such as logos or text blocks.
A screen reader needs to know how header cells relate to data cells. Complex tables may need a short explanation or an equivalent data table in plain text.
Add useful alternative text
Describe an image based on its purpose. For example, alt text for a sales chart might say, "Quarterly sales rose from 20,000 pounds in Q1 to 27,000 pounds in Q4."
Mark a decorative border, background shape or repeated ornament as decorative. This lets assistive technology skip it.
A chart may need more than a short description. Include the important trend in alt text, then provide the underlying values or a nearby text summary.
Write descriptive links
Use link text such as "Download the 2025 pricing guide." Avoid link text such as "click here" or a long raw URL when the destination can be named clearly.
Check colour and text
Do not use colour alone to show meaning. Add labels, patterns or text instructions.
Use readable text with sufficient contrast. The Web Content Accessibility Guidelines provide contrast requirements, including a 4.5 to 1 minimum ratio for normal text at Level AA.
Export a tagged PDF
Use the accessibility or tagged PDF export option in your authoring software. Avoid printing the source file to PDF when that process removes headings, links or other structure.
Microsoft Word can export a tagged PDF when you use its accessibility features and suitable export settings. Still, check the resulting file. Exporting does not guarantee a correct tagged PDF.
Google Docs can preserve some structure in a PDF, but complex layouts and tables need careful checking. InDesign and similar design tools can create tagged PDFs, but you must configure structure, reading order and alternative text.
If you need to combine several files, check each file first, merge them, then run the accessibility checks again. FreeToolr's Merge PDF tool can combine PDF files, but merging does not fix missing tags or bad reading order.
Fix the PDF structure
Adobe Acrobat Pro includes tools for tagging and checking PDFs. Other PDF remediation tools may use different names, but the same principles apply.
Add or repair tags
Open the tag tree and check the main elements. Common tags include P for paragraph, H1 for a first-level heading, L for list, Table for a table and Figure for an image.
A tagged PDF can still contain incorrect tags. For example, body text may be tagged as a heading, or a decorative line may be exposed as content.
Keep the tag tree in the same order that a person should read the document. Check every page, including cover pages and appendices.
Correct the reading order
Reading order controls what a screen reader says and when it says it. A two-column report normally reads down the first column before moving to the second.
Visual position does not always define the correct order. Sidebars, captions, pull quotes and footers can appear in the wrong place in the tag tree.
Use the reading order panel or tag tree to correct these items. Then listen to the result with a screen reader.
Set the title and language
Set the document title in the PDF properties. Choose the correct primary language, such as English, French or Arabic.
For a multilingual file, identify language changes when your PDF tool supports that feature. Correct language settings help a screen reader choose suitable pronunciation rules.
The visible file name is not a replacement for the document title. Both should describe the document clearly.
Add bookmarks to long files
Add bookmarks to major sections in long reports, manuals and guides. Bookmarks help people move through the document without reading every page.
Base bookmarks on the heading structure. Check that each bookmark opens the correct page and uses a useful label.
Repair forms
Use real interactive form fields instead of blank lines or text boxes. Give each field a unique, meaningful name, such as "Email address" or "Date of birth".
Add labels, instructions and useful error messages. Set a logical tab order so keyboard users move through the form in a sensible sequence.
Test every field with a keyboard and screen reader. Check radio buttons, checkboxes, drop-down menus, required fields and submit buttons.
Make a scanned PDF accessible
An image-only scan has no readable text layer. A screen reader usually cannot read the page content until you run optical character recognition, or OCR.
OCR creates text from the page image, but it does not create a fully accessible PDF. You still need to check headings, reading order, tables, images and form fields.
OCR can also make mistakes with names, figures, accents and Arabic text. Compare the OCR result with the original page, especially when the document contains legal, financial or medical information.
For a scanned document, use this sequence:
- Run OCR with the correct language settings.
- Check the text against the scanned page.
- Add tags and correct the reading order.
- Add alternative text or mark images as decorative.
- Set the title and document language.
- Test the final file with a screen reader.
Accessible PDF checklist
Use this checklist before publishing a tagged PDF:
- The PDF contains real text, not only page images.
- The file has a clear title and correct document language.
- Headings use the correct levels.
- The tag tree follows the intended reading order.
- Lists use list tags and have sensible item order.
- Tables have header cells and a clear structure.
- Images have useful alt text when they convey information.
- Decorative images are marked as artifacts.
- Links have descriptive names and work correctly.
- Forms have labels, instructions and logical keyboard order.
- Bookmarks help users navigate long documents.
- Security settings allow assistive technology to read the file.
- The file works when zoomed and viewed on a small screen.
- A screen reader test confirms that the content sounds logical.
Test with automated tools and a screen reader
Run an automated accessibility checker first. It can find missing tags, missing titles, some reading order problems and other technical issues.
Do not treat a clean checker result as proof of accessibility. Automated tools cannot reliably decide if alt text is meaningful or if a table makes sense when read aloud.
Use keyboard commands to move by headings, links, tables and form fields. Listen for repeated text, skipped content, strange column changes and unlabeled controls.
On Windows, test with NVDA or JAWS when possible. On Apple devices, test with VoiceOver. Also check the screen reader and browser combinations used by your organisation or audience.
Ask a disabled user or accessibility specialist to review important public documents. Their feedback can reveal problems that a checker and developer may miss.
Worked example: a 12-page report
Imagine a 12-page report with two columns, three charts, two data tables and four form fields.
First, apply heading styles to the title and six section headings. Then set the reading order to finish the left column before the right column on each page.
Next, describe each chart with its main trend and provide the 12 underlying monthly values in a nearby table. Mark the decorative logo as an artifact.
Set the two data tables with header cells. Label the four form fields as Name, Email address, Organisation and Consent.
After export, inspect the tag tree and run an automated checker. Then use NVDA to navigate by the six headings, read both tables and complete all four fields.
If NVDA reads a chart before its heading, or skips a table header, repair the tags and test again. This process checks the structure that a user actually experiences.
Standards and legal context
WCAG describes accessibility outcomes for web content and documents. PDF/UA specifies technical requirements for accessible PDF files. They support each other but are not the same standard.
Section 508 PDF requirements apply to many US federal agencies and covered organisations. UK public-sector publishers have duties under the Public Sector Bodies Accessibility Regulations 2018. EU organisations may need to follow the European Accessibility Act or local rules, depending on the service and organisation.
Legal duties vary by country, organisation and document purpose. Use official guidance for your location, and do not treat a technical checker result as legal advice.
Sources
Questions people ask
Can a screen reader read any PDF?
No. A screen reader may struggle with an image-only scan, missing tags or an incorrect reading order. A usable text layer and correct structure are both needed.
Is a tagged PDF automatically accessible?
No. Tags may be missing, incomplete or placed in the wrong order. Check the tag tree, run an automated test and read the file with assistive technology.
Does OCR make a PDF accessible?
OCR can create selectable text from a scan. It does not automatically create correct headings, tables, alt text, reading order or form labels.
Is PDF/A the same as an accessible PDF?
No. PDF/A is mainly an archival format. It does not prove that a file has tags, usable reading order or accessible forms.
What is the difference between WCAG and PDF/UA?
WCAG defines accessibility outcomes, while PDF/UA defines technical requirements for PDF files. A project may use both standards when it publishes accessible documents.
FreeToolr articles are written and checked by our editors. Found a mistake? Email [email protected]. Read our editorial policy.