Creating Accessible PDF Documents (PDF/UA Standard)

Creating Accessible PDF Documents (PDF/UA Standard)

Since its invention in the early 1990s, the Portable Document Format (PDF) was designed with one primary goal: to ensure a document prints exactly as it looks on the screen, regardless of the machine or operating system being used.

However, this absolute focus on "visual presentation" makes PDF the natural enemy of accessibility. A raw PDF lacks logical structure (like HTML tags). For a Screen Reader, a PDF is often just a blank canvas populated with random floating letters. Extracting from the literature Guide to Digital Accessibility (Rae Mancilla), this article discusses how to tame the PDF format to comply with the PDF/UA (ISO 14289) standard.

---

1. The "Print to PDF" Myth

The most common way people create PDFs is by finishing a document in Microsoft Word, pressing Ctrl + P (Print), and selecting Save as PDF.

This is an accessibility disaster. The "Print to PDF" process "flattens" the entire document into a single visual layer. All semantic information (such as Heading 1, List structures, Alt Text on images, and Table structures) is permanently stripped away.

The Correct Solution: Structured Export

Always use the source application's native export feature (e.g., Save As -> PDF in Microsoft Word, and ensure the "Document structure tags for accessibility" option is checked). This will inherit your document's hierarchical logic into the PDF's metadata.

---

2. The Heart of PDF Accessibility: Document Tags

The key to creating a PDF that can be read by assistive technology is Tags. Just like HTML tags (<h1>, <p>, <table>), PDF tags provide structure to the document.

If you open Adobe Acrobat Pro and open the Accessibility Tags panel, you should see a neatly organized document tree:

• <Document>
  • <H1> (Document Title)
  • <P> (Paragraph)
  • <Figure> (An image containing Alt Text)

If you receive a PDF that has no tags (often called an Untagged PDF), modern Screen Readers are forced to guess the reading order using artificial intelligence, which has a very low accuracy rate on complex multi-column layouts.

---

3. The Z-Pattern Reading Order

PDFs are heavily used for annual reports or two-column brochures. Visually, the human eye reads the left column from top to bottom, then moves to the right column. This is visual order.

However, without explicit Reading Order remediation via Adobe Acrobat Pro, a Screen Reader might read horizontally straight across the screen from left to right, mashing a sentence from the left column with a sentence from the right column into one meaningless string (like reading a book where the pages are torn across).

You must use the Reading Order Tool in Acrobat to manually lock the text flow, ensuring the machine reads an entire narrative block completely before jumping to the next block.

---

4. The PDF/UA (Universal Accessibility) Standard

If WCAG is the guideline for websites, then PDF/UA (ISO 14289) is the international technical specification for PDF document accessibility.

To achieve PDF/UA certification, a document must strictly meet:

1. Real Text: It must not be a scanned image of a piece of paper. If you cannot highlight/copy the text with your mouse, a Screen Reader cannot read it either (Unless you run an Optical Character Recognition / OCR process).
2. Color Contrast: The same as WCAG (4.5:1 ratio for regular text).
3. Document Language: The language metadata (e.g., en-US or id-ID) must be set globally in the Document Properties so the Screen Reader knows which pronunciation engine to use.
4. Bookmark Navigation: For long documents (more than 9 pages), there must be an interactive Bookmark outline to facilitate direct navigation to specific chapters.

---

5. Conclusion

Do not use PDFs unless absolutely necessary. The best, most accessible digital document is a standard HTML-based document (a Web Page).

However, if corporate regulations force you to distribute PDF reports, be prepared to use advanced professional software (like Adobe Acrobat Pro) to remediate its Tagging and Reading Order. A beautiful-looking PDF means absolutely nothing if it is locked shut to people with visual impairments.

---

References

The discussion on logical document structure (Tagging), the inherent problems of the PDF format post-print-conversion, and Reading Order methodologies are extracted from the structural guide Guide to Digital Accessibility coordinated by Rae Mancilla. The ISO 14289 (PDF/UA) compliance standards refer to the industry benchmarks detailed in that literature.