Documents & PDF

A PDF or office document is not exempt from accessibility just because it isn’t a web page. To assistive technology a document is content like any other, and it has to be built the same way a good page is: tagged with a structure that carries meaning, given a sensible reading order, described where it shows images, and made of real, selectable text. The standard that pins this down for PDF is PDF/UA (ISO 14289) — “Universal Accessibility” — and it sits alongside the same WCAG success criteria you already apply to HTML. A document that looks perfect on screen can still be a locked box to a screen reader if none of that structure is present underneath.

Who this affects

• Screen reader users depend entirely on the document’s tag tree to navigate. Without tags there is no reading order, no headings to jump between, and images speak nothing — the file is read as an undifferentiated wall, or not at all.
• Reflow and zoom users on phones and small screens need the content to reflow from its tags. An untagged or image-only PDF can’t reflow, so they’re left panning a fixed page sideways to read every line.
• Users of any assistive technology reading the document — magnifiers, switch access, voice control, refreshable braille, read-aloud tools — all rely on the same tagged structure and real text to expose the content to the user.

Standards covered

The lesson in this category maps document accessibility to the PDF/UA standard and the WCAG criteria and laws that require it. The same structural fixes satisfy all of them at once.

Lessons

• Accessible documents & PDF

  Tag the structure, add alt text, use real headings and bookmarks, and ship real text instead of a scanned image — the four defects behind most inaccessible documents.

  PDF/UA-1 1.1.1 1.3.1 1.4.5 2.4.1 / 2.4.6

• Accessible Word & Office documents

  Use real heading styles, alt text and header rows in source documents.

• Accessible PDF forms & reading order

  Label PDF fields, fix the tag reading order, and tag lists and tables.