Mobile reading
Why PDFs are still so hard to read on phones
The PDF did its job too well. It froze the page. Then we started reading everything on screens that are nothing like pages.
The page is the bug and the feature
People complain about PDFs because they are rigid. People rely on PDFs because they are rigid. That contradiction explains almost everything.
A PDF is excellent when the final page matters. Invoices, signed forms, policy documents, research papers, insurance packets, product sheets: these need to look stable. Send the file to five people and everyone sees the same page.
A phone does not care about the final page. It cares about thumb reach, line length, font size, contrast, and whether the reader can stay oriented. The PDF preserves the wrong thing for that context.
Pinch zoom is not a reading feature
Pinch zoom is a rescue gesture. It helps you inspect a chart or read a footnote. It is not a good way to read 20 pages.
Once you zoom, you have created a viewport inside the page. Now the page is larger than the screen in both directions. Every line asks for small navigation decisions: move right, move left, move down, do not lose the next sentence. W3C describes this as extra physical and cognitive effort. That is exactly how it feels.
The reader is doing layout work by hand. The software should be doing that work.
If a document needs constant pinch zoom, it has opened successfully but failed as mobile reading.
The worst offenders are not always the longest documents
A 120-page novel-style PDF can be tolerable if it is single-column, tagged, and text-heavy. A four-page brochure can be miserable if it is built from tiny columns, decorative callouts, and image-based text.
This is why page count is a poor predictor of mobile comfort. Density matters. Columns matter. Margins matter. Whether the PDF has selectable text matters. The scan quality matters too.
The practical test is simple: open the file on a phone without rotating the screen. If you cannot read a normal paragraph without zooming or dragging sideways, the document needs a different reading layer.
Accessibility and convenience meet in the same place
Accessible PDF standards focus on structure: tags, reading order, meaningful navigation, and compatibility with assistive technology. That is not a niche concern. Good structure also makes ordinary mobile reading better.
A tagged heading helps a screen reader. It also helps a converter build an outline. A correct reading order helps keyboard navigation. It also stops a two-column report from becoming nonsense when extracted.
This is the useful editorial line for PDF work: accessibility is not a separate feature bolted onto documents later. It is the same foundation that makes documents portable across screens.
What actually fixes the phone problem
There are three levels of fix. The first is better authoring: create documents with real structure before exporting to PDF. The second is better viewing: use a reader mode or Liquid Mode-style tool when available. The third is conversion: rebuild the PDF into a responsive article or text format.
The first is ideal but often unavailable because you are reading someone else's PDF. The second is convenient but tied to a viewer. The third is most useful when you want to keep reading later, search the converted text, copy it, or use it in notes.
None of these are anti-PDF. The PDF remains the source of record. The mobile reading layer is the working copy your eyes can live with.