Learn how to create accessible PDFs that meet ADA, WCAG 2.1, and Section 508 compliance standards. Complete guide to tagged PDFs, alt text, reading order, and screen reader compatibility.
Portable Document Format files are the backbone of digital communication across governments, universities, businesses, and nonprofits. Yet an alarming number of PDFs published online remain completely inaccessible to people who use assistive technologies like screen readers, braille displays, and voice navigation software.
In the United States alone, over 61 million adults live with a disability. Globally, that number exceeds 1.3 billion. When your PDFs lack proper accessibility structures, you are effectively locking out a significant portion of your audience from critical information.
Beyond the ethical imperative, there are serious legal consequences. The Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, and the European Accessibility Act all mandate that digital documents be accessible. Lawsuits related to digital accessibility have surged in recent years, with settlements reaching millions of dollars.
This guide walks you through everything you need to know about making PDFs accessible, from understanding the relevant standards to implementing proper document structure, testing your files, and using the right tools to automate the process.
Before diving into the technical details, it is important to understand the legal and technical frameworks that govern PDF accessibility.
The Americans with Disabilities Act does not explicitly mention PDFs or digital documents. However, courts have consistently interpreted Title II (state and local governments) and Title III (places of public accommodation) to include websites and digital content. If your organization publishes PDFs on a public-facing website, those documents must be accessible.
Section 508 of the Rehabilitation Act applies specifically to federal agencies and organizations that receive federal funding. It requires that electronic and information technology be accessible to people with disabilities. The updated Section 508 standards (2017 refresh) directly reference WCAG 2.0 Level AA.
The Web Content Accessibility Guidelines (WCAG) provide the most widely referenced technical standard for digital accessibility. PDF/UA (Universal Accessibility), formally known as ISO 14289-1, is the dedicated standard for accessible PDF files.
| Standard | Scope | Key Requirements | Enforcement |
|---|---|---|---|
| ADA Title II & III | US public & private sector | Accessible digital content | DOJ enforcement, private lawsuits |
| Section 508 | US federal agencies & contractors | WCAG 2.0 AA conformance | Agency oversight, complaints |
| WCAG 2.1 AA | International best practice | Perceivable, operable, understandable, robust | Referenced by laws worldwide |
| PDF/UA (ISO 14289) | PDF-specific standard | Tagged structure, reading order, alt text | Contractual, regulatory |
| EN 301 549 | European Union | WCAG 2.1 AA + additional | European Accessibility Act |
| AODA | Ontario, Canada | WCAG 2.0 AA by 2025 | Fines up to $100K/day |
Pro Tip: Even if you are not legally required to make your PDFs accessible, doing so improves usability for everyone. Properly structured PDFs are easier to search, reflow on mobile devices, and convert to other formats using tools like our PDF converter.
An accessible PDF is not simply a visual document. It contains a hidden layer of structural information that assistive technologies use to interpret and present the content to users. Understanding this structure is the foundation of PDF accessibility.
Tags are the single most important element of an accessible PDF. They define the logical structure of the document, similar to how HTML tags define the structure of a web page. A tagged PDF includes elements such as:
Without tags, a screen reader encounters a PDF as a flat stream of characters with no indication of headings, paragraphs, lists, or tables. The experience is comparable to reading a wall of unformatted text.
The reading order determines the sequence in which content is presented to assistive technology users. In a visual PDF, elements might appear in columns, sidebars, or floating text boxes. The reading order must ensure that the logical flow of content makes sense when read sequentially.
Every non-decorative image, chart, graph, and diagram must include alternative text that conveys the same information as the visual element. Decorative images should be marked as artifacts so screen readers skip them entirely.
The document must specify its primary language so that screen readers use the correct pronunciation engine. If the document contains passages in other languages, those passages should be tagged with the appropriate language attribute.
The following table maps key WCAG 2.1 success criteria to specific PDF accessibility requirements. Use this as a checklist when auditing your documents.
| WCAG Criterion | Level | PDF Requirement | Pass Criteria | Common Failure |
|---|---|---|---|---|
| 1.1.1 Non-text Content | A | Alt text on all images | Every Figure tag has alt text | Images without alt text or marked as artifact |
| 1.3.1 Info and Relationships | A | Proper tag structure | Headings, lists, tables correctly tagged | Untagged PDF or visual-only formatting |
| 1.3.2 Meaningful Sequence | A | Correct reading order | Content reads logically in sequence | Columns read across instead of down |
| 1.4.1 Use of Color | A | Color not sole indicator | Information conveyed without color alone | Red/green status indicators only |
| 1.4.3 Contrast (Minimum) | AA | 4.5:1 text contrast | All text meets contrast ratio | Light gray text on white background |
| 1.4.5 Images of Text | AA | Real text, not images | Text is selectable, not rasterized | Scanned documents without OCR |
| 2.1.1 Keyboard | A | Keyboard-navigable forms | All form fields reachable via Tab | Form fields without tab order |
| 2.4.1 Bypass Blocks | A | Bookmarks for long docs | Documents 20+ pages have bookmarks | Long PDFs without navigation |
| 2.4.2 Page Titled | A | Document title set | Title property in document properties | Filename used as title |
| 2.4.4 Link Purpose | A | Descriptive link text | Links describe destination | "Click here" or bare URLs |
| 3.1.1 Language of Page | A | Document language set | Language specified in properties | No language attribute |
| 3.1.2 Language of Parts | AA | Language changes marked | Foreign passages tagged with lang | Mixed-language content unmarked |
| 4.1.2 Name, Role, Value | A | Accessible form fields | Labels, tooltips, required states | Unlabeled form fields |
Pro Tip: If your PDF was created from a scanned document, the first step is running OCR to convert the image-based text into real, selectable text. Our PDF OCR tool handles this automatically, producing a fully searchable document that is much easier to make accessible.
The easiest way to create an accessible PDF is to start with a properly structured source document. Whether you are using Microsoft Word, Google Docs, InDesign, or another application, follow these practices:
When you export to PDF, ensure you select the option to create a tagged PDF. In Microsoft Word, this is under "Options" in the Save As dialog (check "Document structure tags for accessibility").
Even when you export a tagged PDF from a well-structured source document, the tags may need refinement. Open the PDF in Adobe Acrobat Pro and inspect the tag tree:
Use the Reading Order tool in Acrobat Pro to verify and adjust the sequence:
For every image that conveys information:
Set the following in File > Properties:
If your PDF contains form fields:
Adobe Acrobat Pro includes a built-in accessibility checker:
Adobe Acrobat Pro is the industry standard for PDF accessibility remediation. It offers the most comprehensive set of tools for tagging, reading order, and form accessibility. However, it comes with a significant price tag and a steep learning curve.
For organizations on a budget, several free tools can help:
Our platform offers several tools that support the accessibility workflow:
Pro Tip: When converting a PDF to Word for remediation, use our PDF to Word converter to preserve as much structure as possible. Fix the accessibility issues in Word, then re-export as a tagged PDF.
Scanned PDFs are essentially images wrapped in a PDF container. They contain no real text, no tags, and no structure. The fix involves two steps:
Tables that span multiple pages often lose their header row associations. Ensure that:
Charts, graphs, and status indicators that rely solely on color to convey information are inaccessible to colorblind users. Always supplement color with text labels, patterns, or shapes.
Long documents (20+ pages) should include bookmarks that mirror the heading structure. In Acrobat Pro, you can generate bookmarks automatically from the tag structure.
Headings must follow a logical hierarchy without skipping levels. Do not jump from H1 to H3 without an H2 in between. Each document should have exactly one H1.
Automated testing catches many issues, but it cannot catch everything. A comprehensive testing strategy includes both automated and manual testing.
| Test Method | What It Catches | What It Misses |
|---|---|---|
| Automated checker | Missing tags, alt text, language, title | Quality of alt text, logical reading order |
| Screen reader | Reading order issues, missing context | Visual contrast, color-only information |
| Keyboard navigation | Inaccessible forms, trapped focus | Visual layout issues |
| Visual inspection | Color contrast, layout problems | Structural tag issues |
| Reflow test | Content loss at zoom, horizontal scroll | Tag quality, semantic correctness |
Google Docs exports tagged PDFs when you use heading styles and built-in lists. However, the tag quality is often inferior to Word exports, and you may need to remediate in Acrobat Pro.
InDesign offers robust accessibility features:
LaTeX users can create tagged PDFs using the accessibility or tagpdf packages. This is still an evolving area, and the output may require additional remediation.
The legal landscape around digital accessibility continues to intensify. Here are real-world examples of enforcement:
Organizations that proactively invest in PDF accessibility avoid these risks while simultaneously improving their content for all users.
Pro Tip: Build accessibility into your document creation workflow from the start. Retrofitting accessibility onto existing PDFs is significantly more expensive and time-consuming than creating accessible documents from the beginning.
Invest in accessibility training for everyone who creates documents. This includes content writers, graphic designers, administrators, and IT staff. A one-time training session is not sufficient — accessibility practices need to be reinforced through ongoing education and documented procedures.
Create accessible document templates that include:
Integrate accessibility checks into your document publishing workflow:
For organizations with large backlogs of inaccessible PDFs, prioritize remediation based on:
PDF accessibility is not optional — it is a legal requirement, an ethical obligation, and a practical improvement to your documents. By understanding the relevant standards, implementing proper document structure, and testing with real assistive technologies, you can ensure that your PDFs reach every member of your audience.
Start with your highest-impact documents, build accessibility into your templates and workflows, and use the right tools to streamline the process. Our PDF tools and document converter can help you create, convert, and optimize PDFs throughout the accessibility workflow.
The investment you make in accessibility today pays dividends in legal protection, broader reach, improved SEO, and a more inclusive digital presence.
ConvertIntoMP4 Team
The ConvertIntoMP4 editorial team — engineers, designers, and media specialists building the fastest free file converter on the web.
