The Complete Guide to PDF Accessibility

Over 1 billion people worldwide live with some form of disability, and an estimated 2.2 billion have a vision impairment. When you publish a PDF that is not accessible, you are potentially excluding 15% of the global population from your content. Beyond the moral imperative, accessibility is increasingly a legal requirement—organizations in the United States, European Union, Canada, and many other jurisdictions face lawsuits and fines for publishing inaccessible digital documents. This guide covers everything you need to know about making your PDFs accessible to everyone.

Why PDF Accessibility Matters

PDFs are one of the most widely used document formats in the world. Government agencies publish regulations as PDFs. Banks send statements as PDFs. Universities distribute course materials as PDFs. Companies share contracts, invoices, and reports as PDFs. When any of these documents is inaccessible, entire groups of people—including those who use screen readers, braille displays, or keyboard-only navigation—are locked out.

Accessibility is not just about compliance. Accessible PDFs are better structured, easier to search, more reliably indexed by search engines, and more usable on mobile devices. The same structural tags that make a PDF readable by a screen reader also make it reflow gracefully on a phone screen. Investing in accessibility improves the experience for everyone.

If you work with PDFs regularly, our PDF Tools let you merge, split, and compress documents right in your browser—a great starting point before tackling accessibility. For step-by-step merging instructions, see our guide on how to merge PDFs online for free.

Understanding the Standards: WCAG, Section 508, and PDF/UA

Several standards govern digital accessibility, and they overlap significantly when it comes to PDFs:

• WCAG 2.1 / 2.2 (Web Content Accessibility Guidelines): Published by the W3C, WCAG is the international standard for web accessibility. It defines three conformance levels: A (minimum), AA (recommended for most organizations), and AAA (highest). WCAG principles—Perceivable, Operable, Understandable, and Robust—apply directly to PDF documents.
• Section 508 (United States): A federal law requiring that electronic and information technology used by federal agencies be accessible. Section 508 was updated in 2017 to incorporate WCAG 2.0 Level AA as the benchmark.
• EN 301 549 (European Union): The EU’s accessibility standard for ICT products and services, which also references WCAG 2.1 Level AA.
• PDF/UA (ISO 14289): A technical standard specifically for accessible PDFs. PDF/UA defines the requirements for tagged PDF structure, alternative text, reading order, and other accessibility features. It is the most detailed and prescriptive standard for PDF accessibility.

In practice, if you conform to PDF/UA, you will meet the PDF-specific requirements of WCAG 2.1 AA, Section 508, and EN 301 549. PDF/UA should be your target standard.

Tagged PDFs: The Foundation of Accessibility

A “tagged PDF” contains a hidden structure tree that describes the logical organization of the document. Tags are the PDF equivalent of HTML elements—they define headings, paragraphs, lists, tables, figures, and other semantic elements. Without tags, a PDF is just a collection of text and graphics placed at specific coordinates on a page, with no information about what each element represents or how they relate to each other.

Here are the essential tags every accessible PDF should include:

• <Document>: The root element wrapping the entire document content.
• <H1> through <H6>: Heading levels that create a navigable outline. Screen reader users rely on headings to jump between sections, just as sighted users scan visual headings. Heading levels should be nested logically—never skip from H1 to H3.
• <P>: Paragraphs of body text.
• <L>, <LI>, <Lbl>, <LBody>: List structures with individual list items, labels, and body content.
• <Table>, <TR>, <TH>, <TD>: Table structures with header cells and data cells properly distinguished.
• <Figure>: Images and illustrations that require alternative text.
• <Link>: Hyperlinks with descriptive link text.

Most PDF authoring tools (Adobe Acrobat, Microsoft Word, Google Docs, LibreOffice) can generate tagged PDFs automatically if you use built-in heading styles and structural formatting rather than manual visual formatting.

Reading Order, Alt Text, and Color Contrast

Reading order determines the sequence in which a screen reader presents content. In a visual PDF, the reading order may seem obvious—top to bottom, left to right. But PDFs store content as positioned objects, not as a linear flow. A two-column layout, a sidebar, a pull quote, or a floating figure can all disrupt the logical reading sequence. The tag structure must explicitly define the correct reading order so that assistive technologies present content in a meaningful sequence.

Alternative text (alt text) for images is one of the most critical accessibility features. Every meaningful image, chart, graph, diagram, and illustration must have descriptive alt text that conveys the same information a sighted user would gain from looking at the image. Decorative images that do not convey information should be marked as artifacts so screen readers skip them entirely.

Writing effective alt text is an art. Describe what the image communicates, not just what it looks like. For a bar chart, don’t write “bar chart”—write “Bar chart showing Q1 revenue of $2.4M, Q2 of $3.1M, Q3 of $2.8M, and Q4 of $3.5M.” For a photo of a team, don’t write “team photo”—write “The engineering team at the 2025 company retreat, standing in front of the office building.”

Color contrast affects readability for people with low vision, color blindness, and even users reading in bright sunlight. WCAG requires a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text (18pt or 14pt bold). Use our Color Tools to check contrast ratios between text and background colors. For a deeper dive into color choices, read our guide on color theory for web developers.

Form Accessibility in PDFs

Fillable PDF forms present unique accessibility challenges. An accessible form must include:

1. Descriptive labels for every field: Each text input, checkbox, radio button, and dropdown must have a programmatically associated label that a screen reader can announce. A field labeled visually as “Name” must also have “Name” as its accessible label in the tag structure.
2. Logical tab order: When a user navigates the form with the Tab key, the focus should move through fields in a logical sequence that matches the visual layout. Test this by tabbing through the entire form without using a mouse.
3. Clear instructions and error messages: If a field has specific requirements (date format, character limit, required status), those instructions must be perceivable by all users, not just conveyed through color or position.
4. Keyboard operability: Every form control must be fully operable with a keyboard alone. Dropdown menus, date pickers, and buttons must all respond to keyboard input.
5. Tooltips and help text: Adding tooltips to form fields provides additional context for screen reader users. The tooltip text is announced when the field receives focus.

For generating secure credentials to protect form data, use our Password Generator.

Testing PDF Accessibility

Creating an accessible PDF is only half the battle—you must also verify that it works correctly with assistive technologies. Here are the tools and techniques for testing:

• Adobe Acrobat Accessibility Checker: Built into Acrobat Pro, this tool runs an automated check against PDF/UA requirements and flags issues like missing alt text, incorrect reading order, and untagged content. It produces a detailed report with links to each issue.
• PAC (PDF Accessibility Checker): A free tool from the PDF/UA Foundation that performs a thorough PDF/UA conformance check. PAC is considered the gold standard for PDF accessibility testing and provides a preview of how the document structure appears to assistive technology.
• Screen reader testing: Automated tools catch structural issues, but only manual testing with an actual screen reader reveals usability problems. Test with NVDA (free, Windows), JAWS (Windows), or VoiceOver (macOS/iOS). Navigate the entire document using only the keyboard and verify that all content is announced in the correct order.
• Color contrast analyzers: Tools like the Colour Contrast Analyser (CCA) or our Color Tools verify that text meets WCAG contrast requirements.
• Manual reading order verification: In Acrobat, use the Order panel or the Tags panel to walk through the document structure and verify that the reading order matches the intended content flow.

Start Creating Accessible PDFs Today

PDF accessibility is not an afterthought—it is a fundamental aspect of document quality. The good news is that most of the work happens during document creation, not after. By using built-in heading styles, adding alt text as you insert images, and testing with automated tools, you can create accessible PDFs without significantly changing your workflow.

Start with your most important documents: public-facing reports, customer contracts, and regulatory filings. Use the PDF/UA standard as your benchmark, test with PAC and a screen reader, and iterate until every element is properly tagged and labeled. Our PDF Tools can help you merge and organize your documents, and our Color Tools ensure your contrast ratios meet WCAG standards. Together, these resources give you everything you need to publish documents that are truly accessible to everyone.