Accessible PDFs ensure that everyone, including people with disabilities, can read and interact with your documents. This guide covers WCAG compliance for PDFs in 2026, from tagging to reading order and alt text.
PDF accessibility is about ensuring that everyone, including people with visual, motor, or cognitive disabilities, can read, navigate, and interact with your documents. In many jurisdictions, accessibility is not just good practice — it is a legal requirement. This guide covers how to make PDFs WCAG compliant in 2026.
Why PDF Accessibility Matters
Legal Requirements
ADA (Americans with Disabilities Act): Requires businesses to provide accessible digital content.
Section 508: Requires US federal agencies to make electronic documents accessible.
EN 301 549: European accessibility standard for public sector documents.
AODA: Accessibility for Ontarians with Disabilities Act.
WCAG 2.1/2.2: Web Content Accessibility Guidelines, the international standard for digital accessibility.
Practical Benefits
Wider audience: Accessible PDFs can be read by more people, including the 15% of the world's population with disabilities.
Better SEO: Accessible PDFs are more easily indexed by search engines.
Improved usability: Accessibility features like proper heading structure and reading order benefit all users.
Professional standards: Many organizations require accessible documents from vendors and partners.
Understanding WCAG for PDFs
WCAG is organized around four principles: Perceivable, Operable, Understandable, and Robust (POUR). For PDFs, this translates to:
Perceivable
Text alternatives: Images have alt text describing their content.
Color contrast: Text has sufficient contrast against the background (4.5:1 for normal text, 3:1 for large text).
Resizable text: Text can be zoomed to 200% without loss of content or functionality.
No color dependence: Information is not conveyed by color alone.
Operable
Keyboard accessible: All interactive elements (form fields, links) can be accessed via keyboard.
Reading order: The document has a logical reading order that screen readers follow.
Navigation: Bookmarks, headings, and a table of contents enable navigation.
No time limits: Content does not have time-sensitive interactions.
Understandable
Readable: The document uses clear language and defines abbreviations.
Predictable: Navigation and interactive elements behave consistently.
Input assistance: Form fields have labels and instructions.
Robust
Compatible: The document works with assistive technologies (screen readers, magnifiers).
Tagged: The PDF has a proper tag structure that defines the document's semantics.
Step 1: Create a Tagged PDF
Tags are the foundation of PDF accessibility. They define the document's structure — headings, paragraphs, lists, tables, images — so that assistive technologies can interpret it correctly.
What Are PDF Tags?
Tags are invisible metadata that describe the role of each element:
`
`, `
`, `
`: Headings (different levels)
`
`: Paragraph
``, `
`: List and list items
`
`, `
`, `
`, `
`: Table elements
``: Image
``: Hyperlink
`
How to Create a Tagged PDF
From Microsoft Word:
Use built-in heading styles (Heading 1, Heading 2, etc.) for all headings.
Add alt text to all images (right-click image > Format Picture > Alt Text).
Use built-in list styles for bulleted and numbered lists.
Use built-in table styles and specify header rows.
When saving as PDF, ensure "Document structure tags for accessibility" is checked.
From Adobe Acrobat Pro:
Open the PDF in Acrobat Pro.
Go to Tools > Accessibility > Autotag Document.
Review and fix the tags in the Tags panel.
Add missing tags manually if needed.
Verifying Tags
In Acrobat Pro:
Go to Tools > Accessibility > Full Check.
Run the accessibility checker.
Review and fix any reported issues.
Step 2: Set the Reading Order
Reading order determines the sequence in which a screen reader reads the content. Even if the visual layout is correct, the reading order may be wrong if the tags are not in the right sequence.
Checking Reading Order
In Acrobat Pro, go to Tools > Accessibility > Reading Order.
The Reading Order panel shows the document with zones indicating reading order.
Check that the zones follow a logical sequence.
Drag zones to reorder if needed.
Common Reading Order Problems
Multi-column layouts: Screen readers may read across columns instead of down. Use the Reading Order tool to define column zones.
Sidebars and callouts: These may interrupt the main content flow. Define them as separate zones.
Headers and footers: These should be marked as artifacts (not read by screen readers) or placed in the correct reading order.
Tables: Ensure table cells are read in the correct order (left to right, top to bottom).
Step 3: Add Alt Text to Images
Alt text (alternative text) describes images for users who cannot see them. Screen readers read alt text aloud.
Writing Good Alt Text
Be concise: 125 characters or less is ideal.
Be descriptive: Describe what the image shows, not what it looks like.
Be contextual: Include information that is relevant to the surrounding text.
Do not state the obvious: If the image is decorative, mark it as an artifact instead.
Do not start with "Image of": The screen reader already announces it is an image.
Examples
Good: "Chart showing quarterly revenue growth from Q1 to Q4 2025"
Bad: "Image of a chart"
Good: "Screenshot of the PDF compression tool interface"
Bad: "Screenshot"
Adding Alt Text in Acrobat Pro
Open the Tags panel.
Find the `` tag for the image.
Right-click and choose "Properties."
Enter the alt text in the "Alternate Text" field.
Step 4: Ensure Sufficient Color Contrast
Color contrast is crucial for users with low vision or color blindness.
WCAG Contrast Requirements
Normal text (below 18pt or 14pt bold): Minimum 4.5:1 contrast ratio.
Large text (18pt+ or 14pt+ bold): Minimum 3:1 contrast ratio.
Non-text elements (icons, charts): Minimum 3:1 contrast ratio.
Checking Contrast
Use a color contrast checker tool (WebAIM Contrast Checker, Colour Contrast Analyser).
Enter the foreground and background color values.
The tool calculates the contrast ratio and indicates whether it passes WCAG.
Common Contrast Issues
Gray text on white: Light gray may not have sufficient contrast.
Color-coded information: If color is the only way to distinguish elements, add text labels or patterns.
Background images: Text over background images may have inconsistent contrast.
Step 5: Make Forms Accessible
Accessible PDF forms have properly labeled fields that screen readers can identify.
Form Accessibility Checklist
Labels: Every form field has a descriptive label.
Tooltips: Add tooltips to fields for additional context.
Tab order: Fields can be navigated in a logical order using the Tab key.
Field types: Use appropriate field types (text, checkbox, radio button, dropdown).
Instructions: Provide instructions for completing the form.
Error messages: If validation is used, error messages should be clear and accessible.
Making Forms Accessible in Acrobat Pro
Open the form in Acrobat Pro.
Go to Tools > Prepare Form.
For each field, right-click > Properties.
Add a tooltip (this serves as the label for screen readers).
Set the tab order (right-click > Show Tab Numbers).
Run the accessibility checker to verify.
Step 6: Add Bookmarks and Navigation
Bookmarks provide a navigation structure that helps all users, especially those using screen readers.
Adding Bookmarks
In Acrobat Pro, open the Bookmarks panel.
Navigate to the first heading.
Click the "Add Bookmark" button.
Name the bookmark to match the heading.
Repeat for all major sections.
Best Practices for Bookmarks
Match heading structure: Bookmarks should mirror the document's heading hierarchy.
Use nested bookmarks: Sub-sections should be nested under their parent sections.
Include all major sections: Every significant section should have a bookmark.
Step 7: Set Document Language and Metadata
Document Language
Setting the document language helps screen readers use the correct pronunciation and language rules.
In Acrobat Pro, go to File > Properties.
In the "Advanced" section, set the "Language" field.
Save the document.
Document Metadata
Accessible metadata includes:
Title: A descriptive title (not just the filename).
Author: The document author or organization.
Subject: A brief description of the document.
Keywords: Relevant keywords for searchability.
Step 8: Test with Assistive Technology
After making a PDF accessible, test it with actual assistive technology:
Screen Reader Testing
NVDA (free): Open source screen reader for Windows.
JAWS (commercial): Popular screen reader for Windows.
VoiceOver (built-in): Screen reader for macOS and iOS.
TalkBack (built-in): Screen reader for Android.
Navigate through the document using the screen reader and verify:
The reading order is logical.
Headings are announced correctly.
Images have alt text.
Form fields are labeled.
Tables are read correctly.
Other Testing Tools
PAC 3 (PDF Accessibility Checker): Free tool that checks PDF accessibility.
Adobe Acrobat Pro Accessibility Checker: Built-in checker that identifies accessibility issues.
CommonLook: Commercial tool for PDF accessibility testing and remediation.
Conclusion
Making PDFs accessible is a multi-step process that requires attention to structure, reading order, alt text, contrast, forms, and navigation. While it requires effort, the benefits are significant: legal compliance, wider audience reach, better SEO, and improved usability for all users. Start by creating tagged PDFs from the source application (Word, InDesign), then verify and fix issues in Adobe Acrobat Pro. Always test with assistive technology before publishing. Accessibility is not a one-time task — make it part of your document creation workflow.
Lisa specializes in content strategy and SEO for tech products. She helps creators and businesses optimize their digital workflows for maximum efficiency.
6+ years in digital marketing and content strategy
Skills & Expertise
SEO StrategyContent MarketingAnalyticsDigital Workflows
Frequently Asked Questions
What is a tagged PDF?
A tagged PDF contains invisible metadata tags that describe the document structure — headings, paragraphs, lists, tables, and images. These tags allow assistive technologies like screen readers to interpret and navigate the document correctly.
What WCAG level should PDFs meet?
Most regulations require WCAG 2.1 Level AA compliance. This includes proper tagging, reading order, alt text, color contrast (4.5:1 for normal text), and accessible forms. Level AAA is the highest but is not always required.
How do I add alt text to images in a PDF?
In Adobe Acrobat Pro, open the Tags panel, find the Figure tag for the image, right-click > Properties, and enter the alt text. If creating the PDF from Word, add alt text to images before converting (right-click image > Format Picture > Alt Text).
Can I make an existing PDF accessible?
Yes. Open the PDF in Adobe Acrobat Pro and use the Accessibility tools to autotag the document, fix the reading order, add alt text, and set the document language. However, it is easier to create accessible PDFs from the source application.
How do I test if my PDF is accessible?
Use Adobe Acrobat Pro's built-in Accessibility Checker, test with a screen reader like NVDA or VoiceOver, and use tools like PAC 3 (PDF Accessibility Checker). Navigate through the document to verify reading order, headings, alt text, and form labels.
