PDF Accessibility: Making Documents Usable for Everyone

· 12 min read

PDF accessibility isn't just a nice-to-have feature—it's a fundamental requirement for creating inclusive digital content. When PDFs are properly structured and tagged, they become usable by everyone, including the millions of people who rely on assistive technologies like screen readers, keyboard navigation, or magnification software.

This comprehensive guide walks you through everything you need to know about PDF accessibility, from understanding the technical requirements to implementing practical solutions that make your documents truly accessible.

Table of Contents

What Makes a PDF Accessible

An accessible PDF is one that can be read, navigated, and understood by people with disabilities. This includes individuals who are blind or have low vision, those with motor impairments who can't use a mouse, people with cognitive disabilities, and users with color blindness.

The foundation of PDF accessibility rests on several key technical requirements that work together to create a seamless experience for all users.

Requirement What It Means Who It Helps Priority
Tag structure Logical hierarchy of headings, paragraphs, lists, and tables Screen reader users Critical
Reading order Content flows in the correct sequence Screen reader users, keyboard navigators Critical
Alt text Text descriptions for images and graphics Blind and low-vision users Critical
Document language Language attribute set (e.g., "en" for English) Screen readers (pronunciation) High
Color contrast Minimum 4.5:1 ratio for normal text, 3:1 for large text Low-vision users, color-blind users High
Bookmarks Navigation outline for long documents All users, especially keyboard navigators Medium
Table headers Row/column headers marked in data tables Screen reader users navigating tables High
Link text Descriptive link text (not "click here") Screen reader users High
Form fields Labels, tooltips, and tab order for interactive elements Screen reader and keyboard users Critical

Check your documents with our PDF Accessibility Checker to identify issues automatically.

Pro tip: Accessibility benefits everyone, not just users with disabilities. Clear structure, logical reading order, and descriptive links improve the experience for all readers, including those on mobile devices or using search engines.

Understanding Tagged PDF Structure

Tags are the invisible backbone of PDF accessibility. They create a structure tree that tells assistive technology what each element is and how content relates to other elements on the page.

Think of tags as the semantic HTML of PDFs. Just as web developers use <h1>, <p>, and <table> tags to give meaning to web content, PDF tags provide the same semantic information to screen readers and other assistive technologies.

Common PDF Tags and Their Purpose

PDF Tag Purpose HTML Equivalent Usage Example
<Document> Root element containing all content <html> Wraps entire document
<H1> - <H6> Heading levels for document hierarchy <h1> - <h6> Chapter titles, section headings
<P> Paragraph of body text <p> Regular text content
<L>, <LI> List container and list items <ul>/<ol>, <li> Bulleted or numbered lists
<Table>, <TR>, <TD>, <TH> Table structure elements Same as HTML Data tables with headers
<Figure> Image or graphic with alt text <figure> Photos, diagrams, charts
<Link> Hyperlink to another location <a> URLs, cross-references
<Span> Inline text with specific styling <span> Emphasized or styled text
<Artifact> Decorative content ignored by screen readers aria-hidden="true" Page numbers, decorative borders

Why Tags Matter

Without proper tags, a PDF is just a collection of text and images with no semantic meaning. Screen readers will attempt to read the content in visual order (left to right, top to bottom), which often produces nonsensical results in multi-column layouts or documents with sidebars.

Consider a newsletter with a two-column layout. An untagged PDF might read the first line of the left column, then jump to the first line of the right column, then back to the second line of the left column—creating a confusing jumble of text.

Proper tagging ensures that content is read in logical order, regardless of visual layout. It also allows screen reader users to navigate by headings, skip to tables, or jump between list items—just like sighted users can scan a document visually.

Quick tip: You can view the tag structure in Adobe Acrobat by opening the Tags panel (View > Show/Hide > Navigation Panes > Tags). This reveals the hidden structure tree that assistive technologies use.

Accessibility Standards: PDF/UA and WCAG

PDF accessibility is governed by two primary standards that work together to ensure documents are usable by everyone.

PDF/UA (ISO 14289)

PDF/UA (Universal Accessibility) is the international standard specifically for accessible PDFs. Published as ISO 14289-1 in 2012, it defines the technical requirements for creating accessible PDF documents.

Key PDF/UA requirements include:

PDF/UA compliance is binary—a document either meets all requirements or it doesn't. There's no partial compliance.

WCAG 2.1 and 2.2

The Web Content Accessibility Guidelines (WCAG) apply to all digital content, including PDFs. While WCAG was originally designed for web content, its principles translate directly to PDF documents.

WCAG is organized around four principles (POUR):

WCAG has three conformance levels:

Most organizations aim for WCAG 2.1 Level AA compliance, which is the standard referenced in most accessibility laws worldwide.

Pro tip: A document can be PDF/UA compliant but still fail WCAG requirements (like color contrast), or vice versa. For full accessibility, aim to meet both standards.

Common Accessibility Issues and Barriers

Even well-intentioned PDF creators often introduce accessibility barriers without realizing it. Understanding these common issues helps you avoid them from the start.

1. Missing or Incorrect Tags

This is the most fundamental accessibility issue. PDFs created by scanning documents, using "Print to PDF," or exporting from applications without accessibility settings are typically untagged.

Even when tags exist, they're often incorrect—headings marked as paragraphs, lists not properly structured, or reading order that doesn't match logical flow.

2. Images Without Alternative Text

Every meaningful image needs descriptive alt text. Screen reader users rely on these descriptions to understand visual content.

Common mistakes include:

3. Poor Color Contrast

Text that doesn't have sufficient contrast with its background is difficult or impossible to read for users with low vision or color blindness.

WCAG requires:

Light gray text on white backgrounds is a frequent offender, as are colored text combinations that look fine to sighted users but fail contrast requirements.

4. Inaccessible Tables

Tables are powerful for organizing data but become confusing without proper structure. Common table issues include:

5. Non-Descriptive Link Text

Links that say "click here," "read more," or "download" provide no context when read out of order. Screen reader users often navigate by jumping between links, so each link needs to be self-descriptive.

Bad: "For more information, click here."

Good: "Read our complete guide to PDF accessibility."

6. Scanned Documents (Image-Only PDFs)

PDFs created by scanning paper documents are essentially images with no selectable text. These are completely inaccessible to screen readers unless OCR (Optical Character Recognition) is applied and the document is properly tagged.

7. Form Fields Without Labels

Interactive PDF forms need proper labels, tooltips, and tab order. Without these, users can't identify what information goes in each field or navigate the form efficiently with a keyboard.

8. Missing Document Properties

Document language, title, and metadata help assistive technologies present content correctly. A missing language attribute causes screen readers to use the wrong pronunciation rules.

Quick tip: Use our PDF Validator to automatically detect many of these common issues before publishing your documents.

How to Test and Check PDF Accessibility

Testing is essential to ensure your PDFs are truly accessible. A multi-layered approach combining automated tools and manual testing provides the most comprehensive results.

Automated Testing Tools

Adobe Acrobat Pro Accessibility Checker

The built-in checker in Adobe Acrobat Pro is the most widely used tool. It checks for:

To run it: Tools > Accessibility > Full Check. The tool generates a detailed report with pass/fail results for each criterion.

PAC (PDF Accessibility Checker)

This free tool from the PDF/UA Foundation provides thorough PDF/UA compliance checking. It's particularly good at identifying structural issues and provides a visual preview of the tag structure.

CommonLook PDF Validator

A professional-grade tool that checks both PDF/UA and WCAG compliance. It offers more detailed reporting than Adobe's checker and includes remediation features.

Online Accessibility Checkers

Our PDF Accessibility Checker provides instant analysis without requiring desktop software. Upload your PDF and receive a comprehensive report highlighting issues and suggested fixes.

Manual Testing Methods

Automated tools catch many issues but can't evaluate everything. Manual testing is essential for:

1. Screen Reader Testing

Test your PDF with actual screen readers:

Listen to how the content is read. Does it make sense? Is the reading order logical? Are images described appropriately?

2. Keyboard Navigation Testing

Try navigating the PDF using only your keyboard:

3. Visual Inspection

Review the document for:

4. Tag Structure Review

Open the Tags panel in Adobe Acrobat and review the structure tree:

Testing Checklist

Use this checklist for comprehensive testing:

  1. Run automated checker (Adobe Acrobat or PAC)
  2. Review and fix all flagged issues
  3. Test with screen reader (NVDA or VoiceOver)
  4. Test keyboard navigation
  5. Check color contrast for all text
  6. Verify alt text quality (not just presence)
  7. Review tag structure in Tags panel
  8. Test on mobile device if applicable
  9. Have someone with disabilities test if possible
  10. Document any remaining issues and workarounds

Pro tip: Testing with real users who have disabilities provides invaluable insights that automated tools and simulated testing can't match. Consider partnering with disability advocacy organizations for user testing.

Fixing Accessibility Issues: Remediation Techniques

Remediation is the process of fixing accessibility issues in existing PDFs. While it's always better to create accessible documents from the start, remediation is often necessary for legacy content.

Adding Tags to Untagged PDFs

In Adobe Acrobat Pro:

  1. Go to Tools > Accessibility > Autotag Document
  2. Acrobat will attempt to add tags automatically
  3. Review the Tags panel to verify structure
  4. Manually correct any errors in tag order or hierarchy

Autotagging works reasonably well for simple documents but often requires significant manual cleanup for complex layouts.

Adding Alternative Text

To add alt text to images:

  1. Open the Tags panel
  2. Find the <Figure> tag for the image
  3. Right-click and select Properties
  4. Enter descriptive alt text in the Alternate Text field
  5. For decorative images, mark as Artifact instead

Good alt text is:

Fixing Reading Order

Use the Reading Order tool (Tools > Accessibility > Reading Order):

  1. The tool shows numbered regions in the order they'll be read
  2. Drag regions to reorder them
  3. Assign correct types (heading, text, figure, table)
  4. Mark decorative elements as Background/Artifact

For complex documents, you may need to manually reorder tags in the Tags panel by dragging them to the correct position.

Making Tables Accessible

To fix table accessibility:

  1. Right-click the table in the Tags panel
  2. Select Table Editor
  3. Mark header rows and columns
  4. Ensure each cell is properly tagged as <TH> (header) or <TD> (data)
  5. Add table summary if needed for complex tables

Improving Link Text

For non-descriptive links:

  1. Find the <Link> tag in the Tags panel
  2. Right-click and select Properties
  3. Add descriptive text in the Alternate Text field
  4. This text will be read instead of the visible link text

Better yet, edit the source document to use descriptive link text from the start.

Setting Document Properties

Essential document properties:

  1. Go to File > Properties
  2. Set the document Title (not filename)
  3. Set the document Language (e.g., "en-US")
  4. Add Author and Subject if relevant
  5. Ensure "Tagged PDF" is checked in the Description tab

Handling Scanned Documents

For image-only PDFs:

  1. Run OCR: Tools > Scan & OCR > Recognize Text > In This File
  2. Review OCR results for accuracy (especially important for technical terms)
  3. Add tags using Autotag Document
  4. Manually correct tag structure and reading order
  5. Add alt text for images and graphics

Note: OCR isn't perfect. Always review the results, especially for documents with complex layouts, tables, or technical content.

Quick tip: Remediation can be time-consuming for complex documents. Consider using our PDF Editor for batch processing multiple documents with similar issues.

PDF accessibility isn't just good practice—it's legally required in many jurisdictions. Understanding these requirements helps organizations avoid lawsuits and ensures equal access for all users.

United States

Section 508 (Rehabilitation Act)

Requires federal agencies and their contractors to make electronic content accessible. Section 508 was updated in 2017 to incorporate WCAG 2.0 Level AA as the technical standard.

Applies to:

Americans with Disabilities Act (ADA)

While the ADA doesn't explicitly mention digital accessibility, courts have consistently ruled that websites and digital content (including PDFs) must be accessible under Title III (public accommodations).

Applies to:

ADA lawsuits related to inaccessible PDFs have increased significantly, with thousands filed annually.

European Union

European Accessibility Act (EAA)

Requires accessibility for products and services, including digital content. Member states must implement the EAA by June 2025.

EN 301 549

The European standard for digital accessibility, which incorporates WCAG 2.1 Level AA. Public sector bodies must comply with this standard.

Other Jurisdictions

Industry-Specific Requirements

Education

Educational institutions must provide accessible course materials under various laws (ADA, Section 504, IDEA). This includes textbooks, syllabi, assignments, and other PDFs.

Healthcare

Healthcare providers must ensure patient-facing documents are accessible, including medical records, consent forms, and educational materials.

Financial Services

Banks and financial institutions must provide accessible statements, disclosures, and other customer documents.

Consequences of Non-Compliance

Organizations that fail to provide accessible PDFs may face:

Pro tip: Don't wait for a lawsuit to prioritize accessibility. Proactive compliance is far less expensive than reactive remediation, and it demonstrates your organization's commitment to inclusion.

Creating Accessible PDFs from the Start

The most efficient approach to PDF accessibility is building it in from the beginning. Creating accessible source documents ensures your PDFs are accessible with minimal remediation.

Microsoft Word Best Practices

Word is the most common source for PDFs. Follow these practices:

Use Built-in Styles

Add Alt Text to Images

  1. Right-click an image and select "Edit Alt Text"
  2. Enter descriptive alt text
  3. Check "Mark as decorative" for decorative images

Create Accessible Tables

Use Descriptive Link Text

Export Settings

When saving as PDF:

  1. Go to File > Save As > PDF
  2. Click Options
  3. Check "Document structure tags for accessibility"
  4. Check "Create bookmarks using: Headings"

Adobe InDesign Best Practices

InDesign is powerful for complex layouts but requires careful setup for accessibility:

Use Paragraph and Character Styles