What a PDF Looks Like to a Screen Reader
A PDF stores where each character sits, not what it means. Here is what that leaves a screen reader to work with, and what it cannot recover.
Written against the Jul 16, 2026 release·what has changed since
A word processor document knows that a line is a heading. A PDF, in the general case, does not. What it stores is where each character sits on the page, in what font, at what size. The word Introduction in 24 point at the top of a page is not marked as a heading anywhere; it is simply large text that happens to be above other text.
That is the trade the format makes, and it is the reason a PDF looks identical everywhere. It is also why reading one aloud is harder than it looks.
What the software has to guess
A screen reader, given an untagged PDF, has to reconstruct meaning from position. Most of the time it manages. The places it struggles are predictable:
- Columns. Two columns of text are just characters at different horizontal positions. Read strictly left to right and you get the first line of column one, then the first line of column two, then the second line of column one.
- Tables. A table is usually lines and text placed near them. Nothing says which cell belongs to which header.
- Headers and footers. A running page header repeats on every page and is read every time unless something marks it as decoration.
- Images of text. A scan carries no characters at all. There is nothing to read.
What you can still do
- 1
Start from text, not from a photograph
A document exported from a word processor carries real characters. A photographed page carries none until somebody recognises them. If you have a choice of source, that choice matters more than anything you do afterwards.
- 2
Put the pages in reading order
Reading order and page order are different things, but a document whose pages are out of order is unreadable to everybody. Fix that first because it is cheap.
- 3
Keep one column where you can
A single column removes the hardest guess. If the document is yours to design, this is the highest-value decision in it.
- 4
Say what an image shows in the text
Nothing here writes alternative text into a PDF. A sentence near the picture that says what it shows survives every reader and every export.
None of this makes a PDF as accessible as a well-marked web page. The honest summary is that PDF was designed to preserve appearance, and appearance is exactly what a screen reader cannot use. When the choice is open, a web page is the more accessible format, and a PDF is what you send when the layout has to survive.
- A PDF stores character positions, not meaning, so structure is inferred rather than read.
- Columns, tables, running headers and scans are where inference goes wrong.
- Tagged PDF solves it; this site does not produce tagged output and does not claim to.
- Real text, sensible page order and a single column help every reader.
Was this article helpful?
Your answer stays in this browser. Nothing is sent to us. See how it works.
Keep reading
Reviewed and maintained by
Novus Stream Solutions Editorial Team
The Novus Stream Solutions Editorial Team maintains Novus PDF Studio's product documentation, tutorials and PDF explainers. The team checks product claims against the current browser-local implementation and tests, prefers primary specifications and vendor documentation, and corrects material errors openly. The byline identifies the responsible organization; it does not imply a named expert or professional adviser.
Privacy note: every tool mentioned in this article runs entirely in your browser. Nothing is uploaded or queued on a server. A PDF stays in the tab unless you explicitly use Save on this device, which stores that session in this browser without storing passwords. More on the how it works page.