Accessibility & Standards

Accessible PDF

Definition

PDF was designed to fix how a page looks, not to describe what it means. An accessible PDF adds the missing layer: a tag tree that marks each block as a heading, a paragraph, a list, a table or a figure, plus alt text on images, a defined reading order, a document title and a stated language. The reference standard is PDF/UA, published as ISO 14289, and the relevant WCAG success criteria apply to a PDF exactly as they apply to a web page. Two PDFs can look identical on screen and differ completely here — one reads out as a structured document, the other as one undifferentiated blob, or as nothing at all. Real text matters just as much: if the page is a scanned image, there are no characters to read, select, search or tag until OCR has produced some. Almost all of this is decided at export time, in the tool the document was written in.

Why It Matters

PDF is one of the most-published file types on the web, and an untagged one is a dead end for anyone using a screen reader — not a degraded experience, a blank wall. Remediation afterwards is slow work: building a tag tree by hand for a 40-page report in Acrobat is most of a day, while enabling the accessibility option before you export from Word takes about ten seconds. Untagged files also cannot reflow, so a reader who needs 200 per cent text size on a phone gets horizontal scrolling on every line. The same missing text layer keeps the document out of search results, because there is nothing for a crawler to index either.

How It Works

Authoring tools build the tags from the structure you already used, so the work happens before the export. Apply real heading styles rather than bigger bold text, use the list and table tools instead of drawing rows by hand, add alt text to every image, then export with the accessibility setting switched on — 'Document structure tags for accessibility' in Word, 'Tagged PDF' in LibreOffice, and the equivalent checkbox in InDesign and Google Docs. The export writes a StructTreeRoot into the file holding elements such as H1, P, L, LI, Table and Figure, and the sequence of that tree is the reading order assistive technology follows, which need not match the visual order. For a scanned original, run OCR first so a genuine text layer exists under the image, then tag the result. Acrobat Pro's built-in checker and the free PAC tool will list what is missing, though a clean report proves the tags exist, not that they make sense.

Real-World Example

A charity exports its 18-page annual report and publishes the 4 MB file at annual-report.99helpers.site. The first upload was a scan of the printed copy: a screen reader announced the page count and then fell silent, and the document returned no results for its own title. Re-exporting from the original Word file with structure tags enabled produced a document with navigable headings, alt text on each chart, and text that could be selected and searched. 99helpers serves whichever file you upload, byte for byte, and keeps the earlier version for rollback — it does not tag or convert anything, so the fix belongs in the authoring tool before upload.

Common Mistakes

  • Scanning a printed page and publishing the result — the file contains an image of text and no characters at all, so assistive technology finds nothing to read and search engines index nothing
  • Styling headings by making text larger and bold instead of using heading styles — the export has no structure to convert, so the whole document comes out as flat body text
  • Treating a passing checker report as the finish line — automated checks confirm that tags are present, not that the order is sensible or the alt text says anything useful

Related Terms

Put a file online in seconds

Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.

Host a file free →