A PDF reads well on screen when the work is done before you export it. Build the source file with real headings, real lists and alt text. Export it with tags turned on. Keep the text as text, set a title and a language, then run a checker.
A PDF cannot fix a messy source. Whatever is wrong in the Word or other file will be wrong in the PDF. This page goes through the steps in the order you do them.
Start with a clean source file
A public-sector publishing guide says to make the source document accessible before you convert it. It lists the habits that matter most.
- Headings are real heading styles, not bold text. Start with the title and do not skip levels. See using headings.
- Lists and tables use the program's own list and table tools. Tables hold data only, with header cells.
- Every image that adds meaning has alt text, and decoration is marked as decoration. See writing alt text.
- Link text says where the link goes. Avoid "here" and "more". See link text.
- Text has enough contrast with its background.
- The file name is short and says what the document is.
- No important words sit inside pictures.
The same guide also asks for a plain sans serif font at 12 points or larger, left-aligned text and a meaningful title.
Export with tags
Tags are the hidden structure inside a PDF. They tell a screen reader what is a heading, a list or a table. Microsoft says its apps can add tags automatically when you save a file as PDF.
In Microsoft 365 on Windows, for example in Word, the steps are these:
- Run the Accessibility Checker and fix what it finds.
- Choose File, then Save As or Save a Copy.
- Pick PDF as the file type and select Options.
- Make sure "Document structure tags for accessibility" is ticked, then confirm.
On a Mac, the page points to the option "Best for electronic distribution and accessibility", which uses an online Microsoft service to convert the file. Word for the web has its own Download as PDF route. Menu names can differ by version.
Exporting through a browser print window is a different route. It is covered in saving a page as a PDF from your browser.
Keep real text, not scans
A scan is a picture of a page. The public-sector guide warns that people cannot search a scanned document, and a screen reader will not read it. Its advice is to run optical character recognition (OCR) on the scan first, so the words become text.
A quick test: open the PDF and search for a word from the middle of a page. If the search finds it, the text is real. If you can select a single word with the cursor, that is a good sign too.
| What you have | What to do |
|---|---|
| A document you wrote | Export it from the source file with tags |
| A scan of paper | Run OCR, then check the result against the page |
| A flyer saved as a picture | Rebuild it with real text, or publish the text separately |
| Text inside an image | Retype it as real text; the guide says screen readers cannot read it |
Set the title and the language
Two settings are easy to forget. The W3C has a technique for each.
Title. The W3C's PDF18 says a descriptive title identifies the document without making readers interpret the page content. In Acrobat Pro, the example uses File, then Properties, then the Description tab. A second setting, on the Initial View tab, shows the document title in the title bar of the window.
Language. PDF16 says that setting the document's default language helps screen readers load the right pronunciation rules. In the Acrobat Pro example, you find it under File, Properties, Advanced, then Reading Options. Both techniques apply to tagged PDF files and mention that other tools offer similar settings.
After you export, open the properties of the PDF and check both. The Easy-Read Editor can help you shorten the title and headings before you export.
Run a checker, then look yourself
The guide asks you to run an accessibility checker once the PDF exists, in case you missed something. Most software has a basic one. A checker finds missing structure, but it cannot judge whether a description makes sense or whether the reading order feels natural.
The guide is also honest about a limit. It says PDF cannot be made fully accessible to every user of assistive technology, and it recommends publishing an accessible version alongside it. In practice, that means a web page or an editable file with the same content.
One more note from the guide: the "A" in PDF/A stands for archiving. It does not relate to accessibility.
If you are sending the file by message, see sending a document without confusing anyone.
Common mistakes
- Exporting first and fixing later. Fix the source. The PDF inherits every flaw.
- Using bold lines as headings. A screen reader may not treat them as headings.
- Scanning a paper page and calling it done. Without OCR, it is a picture.
- Leaving the title empty. The PDF then has no descriptive title to show.
- Trusting the checker alone. It cannot judge alt text or reading order.
- Offering only the PDF. Add a web or editable version.
FAQ
Is a PDF accessible just because I exported it?
No. Export with tags, then run a checker and look at the result yourself. The source file decides most of the quality.
Does PDF/A mean accessible?
No. The guide says the "A" stands for archiving and has nothing to do with accessibility.
Should I use a PDF at all?
If readers will mainly read on screen, a web page often serves them better. The guide puts HTML first. A PDF suits a copy that people keep or print.
How can I tell if my PDF contains real text?
Search for a word from inside a page. If the search finds it, the text is real. If it finds nothing, the page may be a picture.
Sources
Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.
- Publishing accessible documents - GOV.UK Checked November 19, 2026
- Create accessible PDFs - Microsoft Support Checked November 19, 2026
- PDF16: Setting the default language using the /Lang entry in the document catalog of a PDF document Checked November 19, 2026
- PDF18: Specifying the document title using the Title entry in the document information dictionary of a PDF document Checked November 19, 2026
This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.