PDF Accessibility: WCAG & Section 508 Requirements for Documents

Why PDFs Fail Accessibility More Than Web Pages

PDFs are the single largest source of accessibility failures in most organizations' digital estates, yet they often receive far less attention than websites. A web page is rendered live by a browser; a PDF is a fixed-layout document where structure, reading order, and semantic meaning must be explicitly embedded by the author or a remediator. When a PDF is created by printing to PDF from Word, exported without accessibility settings, or scanned from paper, it is almost entirely inaccessible to screen readers.

PDF/UA vs WCAG: Understanding the Standards

Two standards govern PDF accessibility: WCAG 2.1 (Web Content Accessibility Guidelines) and PDF/UA (ISO 14289-1, Universal Accessibility). WCAG applies broadly and includes guidance on non-web documents; PDF/UA is a precise technical standard specifically for PDF documents, defining exact requirements for structure, tagging, reading order, and metadata. Section 508 of the Rehabilitation Act applies to electronic documents including PDFs and now references WCAG 2.0 Level AA through the 2017 Revised 508 Standards.

Creating Accessible PDFs from Word

The best time to make a PDF accessible is before it becomes a PDF — during authoring in Microsoft Word or Adobe InDesign. A well-structured source document will produce a well-tagged PDF when exported correctly.

• Use built-in Heading styles (Heading 1, Heading 2, Heading 3) rather than manual bold/font-size formatting
• Add alt text to all images, charts, and SmartArt using the Format Picture dialog
• Use true lists (bulleted/numbered) rather than manually typed dashes or numbers
• Set the document language in File > Options > Language
• Use table headers (Table Properties > Row > Repeat as header row) for data tables
• Run the built-in Accessibility Checker (Review > Check Accessibility) before export
• Export via File > Save As > PDF with 'Document structure tags for accessibility' checked — never print to PDF

Using Adobe Acrobat Pro for Remediation

When a PDF arrives already created — from a third party, a legacy system, or a print-to-PDF workflow — Adobe Acrobat Pro is the primary tool for remediation. The remediation process involves adding or correcting tags, setting reading order, adding alt text to untagged images, creating form field labels, and setting document metadata.

Testing PDFs with PAC 2024 and Screen Readers

PAC (PDF Accessibility Checker) 2024 is a free tool from the PDF Association that tests a PDF against PDF/UA-1 requirements. After automated testing, manual testing with a screen reader remains essential — NVDA or JAWS on Windows are the most representative tools.

• PAC 2024 (free): Tests against PDF/UA-1; download from pdfua.foundation
• Adobe Acrobat Pro Accessibility Checker: Good for quick checks; less rigorous than PAC
• JAWS + Adobe Acrobat Reader: Most representative of real-world screen reader PDF usage
• NVDA + Adobe Acrobat Reader: Free option; good for heading navigation and reading order verification

The Scanned Document Problem

A scanned PDF is not a PDF with text — it is an image of a page, and without OCR processing it is completely inaccessible to screen readers. Adobe Acrobat Pro's 'Recognize Text' tool can convert a scanned PDF to a tagged, searchable PDF, but the output quality depends heavily on scan resolution and OCR accuracy. After OCR, the document must still be reviewed for reading order, tagging, and accuracy.

Section 508 Document Exceptions and Disproportionate Burden

Section 508 applies to all electronic content created, procured, or used by US federal agencies, including PDFs. Archival content not actively used is generally exempt. The Section 508 'undue burden' exception requires a written determination and must still provide alternative means of access. Under WCAG and EAA frameworks, 'disproportionate burden' is a formal process — not a general excuse — and organizations invoking it must document their reasoning.