PDF Accessibility Guide — Making PDFs Usable by Everyone

PDF accessibility ensures that documents are usable by everyone, including people who rely on assistive technologies like screen readers, magnifiers, voice control software, and Braille displays.

According to the World Health Organization (WHO), approximately 1.3 billion people — 16% of the global population — experience significant disability. Of these, roughly 253 million have vision impairments (including 36 million who are blind), and 466 million have hearing disabilities. When PDFs lack proper accessibility structure, this entire population is effectively locked out of the information.

The business case extends beyond ethics. According to a 2023 study by the WebAIM Foundation, organizations with inaccessible digital content face an average of $25,000 per ADA violation in legal penalties in the United States, with class action settlements frequently exceeding $100,000. The number of digital accessibility lawsuits in the U.S. grew by 12% year-over-year in 2023, surpassing 4,500 federal filings.

Accessible PDFs also benefit all users through improved search indexing, better text selection, more reliable copy-paste, and responsive reflow on mobile devices. According to Microsoft's inclusive design research, accessibility improvements typically benefit 100% of users — not just the 16% with disabilities.

An accessible PDF contains specific structural elements that enable assistive technologies to interpret and navigate the content:

• Tag structure — The most critical requirement. Tags define the semantic structure of a document — headings (H1–H6), paragraphs (P), lists (L, LI), tables (Table, TR, TD, TH), and figures (Figure). Without tags, a screen reader can only read raw text in the order it appears in the content stream, which may not match the visual reading order.
• Alternative text — Every non-decorative image, chart, and graphic must have descriptive alt text that conveys the same information visually sighted users receive.
• Reading order — The order in which content is read by assistive technology must match the logical reading sequence. In complex layouts (multi-column, sidebars, pull quotes), visual order and reading order can diverge unless explicitly defined.
• Language specification — The document's primary language must be set in metadata (e.g., "en-US"), and language changes within the text (foreign words, quotes) should be tagged with the appropriate language code.
• Bookmarks and headings — Longer documents should provide navigational bookmarks corresponding to the heading structure, enabling users to jump between sections.
• Color contrast — Text must maintain a minimum contrast ratio of 4.5:1 against its background for normal text and 3:1 for large text, per WCAG 2.1 Level AA guidelines published by the W3C (World Wide Web Consortium).

According to the PDF Association, tagged structure is the single most impactful accessibility feature — it transforms a flat visual document into semantic content that machines (and therefore assistive technology) can understand.

PDF/UA (Universal Accessibility) is the ISO standard for accessible PDFs, formally designated ISO 14289. First published in 2012, it specifies the technical requirements that PDFs must satisfy to be considered universally accessible.

PDF/UA builds on top of the PDF specification and the WCAG (Web Content Accessibility Guidelines) published by the W3C, adapting web accessibility principles to the fixed-layout PDF format.

Key PDF/UA requirements: • All content must be tagged with appropriate structure tags • All images, figures, and non-text content must have alternative text descriptions • The tag tree must define a logical reading order that matches the intended reading sequence • The document language must be specified • Security settings must not interfere with assistive technology access • All fonts must be embedded and mapped to Unicode for text extraction • No content may rely solely on visual characteristics (color, size, position) to convey meaning

PDF/UA-2 (ISO 14289-2), published in 2024, updates the standard based on WCAG 2.1 and the PDF 2.0 specification, adding requirements for mathematical content (MathML), pronunciation hints, and more sophisticated table structures.

According to the PDF Association, compliance with PDF/UA satisfies the PDF-specific requirements of WCAG 2.1 Level AA — meaning a PDF/UA-compliant document meets the accessibility threshold required by most disability access laws worldwide.

PDF accessibility is legally mandated in most major jurisdictions:

• United States — ADA (Americans with Disabilities Act) — Federal courts have consistently ruled that digital documents, including PDFs, fall under ADA Title III requirements. Organizations serving the public must ensure their digital content is accessible.
• United States — Section 508 (Rehabilitation Act) — All federal agencies must ensure electronic documents are accessible. This applies to any PDF published on a .gov website or distributed as part of federal programs. Section 508 requires conformance with WCAG 2.0 Level AA.
• European Union — European Accessibility Act (EAA) — Effective June 2025, the EAA requires businesses selling products and services in the EU to meet accessibility standards, including document accessibility. The Web Accessibility Directive already requires all public sector websites and documents to be accessible.
• Canada — Accessible Canada Act — Federal organizations must remove barriers to accessibility, including in digital communications and documents.
• United Kingdom — Equality Act 2010 — Requires "reasonable adjustments" for people with disabilities, which courts have interpreted to include making digital documents accessible.

According to a 2024 report by Siteimprove, only 2.4% of PDFs published on government websites fully comply with PDF/UA standards — despite legal mandates requiring accessibility. The gap between requirements and implementation remains significant.

Creating accessible PDFs requires attention throughout the authoring process, not just as a final step:

Creating accessible PDFs in Microsoft Word: 1. Use built-in heading styles (Heading 1, Heading 2, etc.) — never apply formatting manually 2. Add alt text to every image (Right-click → Edit Alt Text) 3. Use the built-in table tool — never simulate tables with tabs or spaces 4. Run the Accessibility Checker (Review → Check Accessibility) before exporting 5. Export as PDF with the "Document structure tags for accessibility" option enabled

Creating accessible PDFs in Adobe InDesign: 1. Set up paragraph styles mapped to PDF tags (Export Tagging in Style Options) 2. Define reading order in the Articles panel 3. Add alt text to placed images via Object Export Options 4. Export with the "Create Tagged PDF" option enabled

Testing accessibility: After creation, test the PDF with multiple tools and methods: • Adobe Acrobat's Accessibility Checker — The most comprehensive built-in tool. Reports tag structure, reading order, alt text, and contrast issues. • PAC (PDF Accessibility Checker) — A free tool by the Swiss foundation Access for All that validates against PDF/UA requirements specifically. • Screen reader testing — Test with NVDA (free, Windows), JAWS (commercial, Windows), or VoiceOver (built-in, macOS/iOS) to experience the document as a screen reader user would. • Manual review — Verify that reading order is logical, tab order follows form fields correctly, and decorative images are marked as artifacts.

According to the International Association of Accessibility Professionals (IAAP), the most common accessibility failures in PDFs are: missing tags (67%), missing alt text on images (52%), incorrect reading order (34%), and insufficient color contrast (23%).