PDF stands for Portable Document Format. It was designed to preserve the appearance of a document across devices and software, making it useful for print-ready material, signed records, designed publications and files whose layout must remain fixed.
That strength can become a weakness on the web. A fixed page designed for A4 paper is often awkward on a phone, harder to navigate, less adaptable and more difficult to maintain than an ordinary web page. Content teams should treat PDF as a deliberate format choice, not the ceremonial final form of anything that once passed through Microsoft Word.
Why it matters for content
PDFs often contain important material: reports, policies, forms, research and guidance. If that content is hard to search, read or use, the format creates a barrier around precisely the information people came for. Long documents need proper headings, bookmarks, links and a logical reading order. Images need alternatives and forms need labelled controls.
Maintenance is another concern. A PDF can be downloaded, copied and linked from elsewhere long after a newer version appears. Updating the website may leave old files circulating without visible context. Teams need clear dates, version information, canonical locations and a retirement process.
A web page is usually better for material that changes regularly, supports an online task or needs to work fluidly across devices. PDFs earn their place when the bounded document itself matters – for example, a printable report, formal record or designed publication – and when an accessible version can be produced and maintained.
How AI changes the picture
An assistant can help someone locate the assumptions behind a finding, compare sections of a report or ask for an explanation of an unfamiliar term. The document becomes easier to question as well as summarise. Answers need references back to the relevant pages, especially where a table, qualification or footnote changes the meaning. Source-based tools such as NotebookLM show one direction this reading experience can take; they don’t establish that every PDF can be interpreted reliably.
PDF extraction needs care. Scanned pages may require optical character recognition, complex layouts can scramble reading order and tables may lose their relationships. Teams should preserve structured source content where possible and check extracted text before relying on it. Help with reading or identifying likely accessibility problems doesn’t make the underlying file accessible.
Dates, versions, titles and metadata help systems select the right file. Where the same facts exist in web pages, PDFs and internal documents, a canonical source should be explicit. Readers should be able to tell which version an answer draws on and return to it to check the detail.
Questions people ask
- Are PDFs inaccessible?
Not inherently, but accessible PDFs require proper structure and testing. Untagged, scanned or badly exported files can be very difficult for screen-reader and keyboard users.
- When should we use a web page instead?
Prefer HTML when content changes often, supports a task, needs responsive layout or should be easy to search, link and reuse. Offer a PDF as an additional format where printing or fixed presentation adds value.
- Can we make a PDF accessible after it has been designed?
Often, but remediation can be laborious and imperfect. Accessibility is easier when the source document has correct headings, reading order, link text and alternatives from the start.
- Can AI safely summarise a PDF?
It can help, but check that the text was extracted correctly and verify consequential claims against the document. A confident summary cannot restore a missing column or unreadable scan.
Learn more
- Creating accessible PDFs – practical guidance and a frank comparison with the accessibility and maintainability of HTML.
- Create and verify PDF accessibility – detailed steps for tagging, checking and repairing documents.
- Longing for longer – Contentious considers how reports can become immersive, navigable digital stories, without making length an end in itself.