PDF Accessibility Guidelines: Creating WCAG-Compliant Documents

Ensure your PDFs are accessible to all users, including those using assistive technologies.

Accessible PDFs aren't just about compliance—they're about inclusion. Over 1 billion people worldwide have disabilities, and many rely on assistive technologies like screen readers to access digital content. An inaccessible PDF excludes these users, violates legal requirements like the ADA and Section 508, and harms your organization's reputation. This comprehensive guide covers everything from WCAG standards to practical implementation, ensuring your PDFs work for everyone.

Why PDF Accessibility Matters

👥 1 Billion People Worldwide

  • • 15% of global population has some form of disability
  • • 285 million visually impaired (39 million blind)
  • • 466 million with hearing loss
  • • Millions with cognitive, motor, or speech disabilities

⚖️ Legal Requirements

  • • ADA (Americans with Disabilities Act)
  • • Section 508 (US federal agencies)
  • • AODA (Ontario, Canada)
  • • European Accessibility Act (EU)
  • • Lawsuits & fines for non-compliance

💼 Business Benefits

  • • Reach 15% larger audience
  • • Improved SEO (search engines read tags)
  • • Better usability for everyone
  • • Positive brand reputation
  • • Competitive advantage in procurement

🎯 Universal Design

  • • Benefits users with temporary limitations
  • • Helps non-native speakers
  • • Improves mobile experience
  • • Enables better content reuse
  • • Future-proofs your content

Understanding WCAG 2.1 Standards

Web Content Accessibility Guidelines (WCAG) 2.1 defines three conformance levels:

🥉

Level A (Minimum)

Most basic accessibility features. Without these, content is largely inaccessible to people with disabilities.

Examples: Text alternatives for images, keyboard accessibility, sufficient color contrast

🥈

Level AA (Target Standard)

Addresses major accessibility barriers. This is the level most organizations aim for and what's legally required in many jurisdictions.

Examples: Enhanced contrast (4.5:1), resizable text, multiple navigation methods

🥇

Level AAA (Enhanced)

Highest level of accessibility. Not always achievable for all content, but provides the best experience.

Examples: Sign language interpretation, extended audio descriptions, very high contrast (7:1)

Recommendation: Target WCAG 2.1 Level AA compliance as the baseline. This satisfies most legal requirements and provides excellent accessibility for the vast majority of users.

The Four WCAG Principles: POUR

👁️ Perceivable

Information must be presentable to users in ways they can perceive.

  • • Text alternatives for non-text content
  • • Captions and transcripts for audio/video
  • • Content adaptable to different presentations
  • • Sufficient color contrast
  • • Distinguishable foreground from background

⌨️ Operable

Interface components must be operable by all users.

  • • All functionality available via keyboard
  • • Users have enough time to read/use content
  • • No content that causes seizures
  • • Navigable via multiple methods
  • • Clear focus indicators

🧠 Understandable

Information and operation must be understandable.

  • • Readable and understandable text
  • • Content appears and operates predictably
  • • Help users avoid and correct mistakes
  • • Clear instructions and labels
  • • Consistent navigation and identification

🔧 Robust

Content must work with current and future technologies.

  • • Compatible with assistive technologies
  • • Proper use of PDF standards
  • • Valid structure and tagging
  • • Name, role, value for all components
  • • Works across different readers

Essential Accessibility Features

1. Document Structure & Tags

Tagged PDFs define the logical reading order and document structure, enabling screen readers to navigate content correctly.

✅ Required Tags:

  • • Headings (H1-H6) for hierarchy
  • • Paragraphs (P) for body text
  • • Lists (L, LI) for structured content
  • • Tables (Table, TR, TH, TD)
  • • Links (Link) with descriptive text
  • • Figures (Figure) for images/graphics

❌ Avoid:

  • • Untagged documents
  • • Incorrect reading order
  • • Fake headings (bold text instead of H tags)
  • • Missing alt text on images
  • • Nested tables (complex structures)

How to check: Use Adobe Acrobat's "Reading Order" tool or accessibility checker. Screen reader users rely entirely on proper tagging.

2. Alternative Text for Images

Alt text describes visual content to users who can't see it. Every image must have alt text or be marked as decorative.

✅ Good Alt Text:

"Bar chart showing 40% increase in sales from Q1 to Q2 2024, with revenue rising from $2M to $2.8M"

Descriptive, specific, conveys meaning

❌ Poor Alt Text:

"chart.png" or "image" or "graph"

Generic, uninformative, unhelpful

Alt Text Guidelines:

  • • Keep under 150 characters when possible (use long description for complex images)
  • • Describe function, not appearance (e.g., "Search button" not "Magnifying glass icon")
  • • Don't start with "Image of..." (screen readers announce it's an image)
  • • Mark decorative images as artifacts (no alt text needed)

3. Color Contrast

Sufficient contrast between text and background ensures readability for users with low vision or color blindness.

✅ WCAG AA

Regular text: 4.5:1

Large text (18pt+): 3:1

✅✅ WCAG AAA

Regular text: 7:1

Large text (18pt+): 4.5:1

❌ Fails

Regular text: <4.5:1

Insufficient contrast

Common failures: Light gray text on white, yellow text on white, dark blue on black. Test with online contrast checkers.

4. Logical Reading Order

Content must flow in a logical sequence matching visual layout. Screen readers follow the tagged order, not visual position.

✅ Correct Order:

1. Document Title

2. Introduction

3. Section 1 Heading

4. Section 1 Content

5. Section 2 Heading

6. Section 2 Content

❌ Incorrect Order:

1. Document Title

2. Sidebar (visual right)

3. Section 1 Content

4. Introduction (out of order)

5. Section 2 Heading

6. Footer content

5. Document Language

Specify the document's language so screen readers use correct pronunciation.

Set primary language in document properties (e.g., "en-US", "es-ES", "fr-FR"). Mark language changes inline for multilingual content.

6. Form Field Labels

Interactive forms need proper labels, descriptions, and navigation order.

  • • Every field has a descriptive label (not just placeholder text)
  • • Tooltips provide additional help where needed
  • • Tab order follows logical sequence
  • • Required fields clearly marked
  • • Error messages are clear and specific

7. Tables

Accessible tables use proper structure to convey relationships between data.

✅ Accessible Tables:

  • • Header rows marked as TH (table header)
  • • Data cells marked as TD
  • • Simple structure (avoid nested tables)
  • • Headers associated with data cells
  • • Caption or summary provided

❌ Inaccessible:

  • • Tables used for layout (use columns instead)
  • • No header row designation
  • • Merged cells creating confusion
  • • Empty cells without explanation

8. Bookmarks and Navigation

Bookmarks provide navigation for long documents, especially important for screen reader users.

  • • Create bookmarks from heading structure
  • • Descriptive bookmark names
  • • Hierarchical organization mirrors document structure
  • • Link to specific sections, not just pages

Creating Accessible PDFs: Step-by-Step

Method 1: Start with Accessible Source (Best)

Creating accessibility in the source application (Word, InDesign) is more efficient than remediation.

In Microsoft Word:

  • 1. Use built-in heading styles (Heading 1, Heading 2, etc.)
  • 2. Add alt text to all images (right-click → Edit Alt Text)
  • 3. Use Word's table tools with header rows
  • 4. Run Accessibility Checker (Review tab)
  • 5. Export as PDF with "Document structure tags for accessibility" checked

Method 2: Remediate Existing PDFs

Use Adobe Acrobat Pro to add accessibility features to existing PDFs.

Adobe Acrobat Pro Steps:

  • 1. Run Full Check (Accessibility → Full Check)
  • 2. Auto-tag document (Accessibility → Autotag Document)
  • 3. Fix reading order (Accessibility → Reading Order)
  • 4. Add alt text to images (Right-click image → Edit Alternate Text)
  • 5. Set document language (File → Properties → Advanced)
  • 6. Re-run Full Check to verify fixes

Method 3: OCR for Scanned Documents

Scanned PDFs are just images—they need OCR (Optical Character Recognition) to become accessible.

OCR Process:

  • 1. Open scanned PDF in Acrobat Pro
  • 2. Run OCR (Tools → Enhance Scans → Recognize Text)
  • 3. Choose correct language
  • 4. Make text searchable and selectable
  • 5. Add tags and structure (as in Method 2)
  • 6. Verify OCR accuracy manually

Testing for Accessibility

Automated Testing Tools

  • Adobe Acrobat Full Check: Comprehensive automated test
  • PAC 2021: Free PDF accessibility checker
  • PAVE: Free checker from Commonlook
  • axesPDF: Automated testing tool

Automated tools catch 30-50% of issues but miss context and logic problems.

Manual Testing

  • Screen Reader Test: Use NVDA (free) or JAWS to navigate document
  • Keyboard Navigation: Navigate using only Tab, Enter, Arrow keys
  • Zoom Test: View at 200-400% magnification
  • Color Blindness Sim: Test with color blindness simulators

Manual testing is essential—if you can't use it, neither can your users.

Quick Accessibility Checklist:

☐ Document is tagged

☐ Logical reading order

☐ All images have alt text

☐ Sufficient color contrast

☐ Document language set

☐ Headings used properly

☐ Tables have headers

☐ Links have descriptive text

☐ Forms have labels

☐ Passes screen reader test

Common Accessibility Mistakes

❌ Using Images of Text

Screenshots of text aren't accessible. Use actual text whenever possible. If you must use images, provide full text alternative.

❌ "Click Here" Links

Links need descriptive text. "Click here" means nothing to screen reader users browsing links. Use "Download Q3 Report (PDF, 2MB)" instead.

❌ Color as Only Indicator

Don't rely solely on color to convey meaning. "Red items are urgent" fails for colorblind users. Add icons, labels, or patterns.

❌ Untagged Scanned Documents

Scans are just images. Without OCR and tagging, they're completely inaccessible to screen readers.

❌ Complex Tables for Layout

Using tables to arrange content confuses screen readers. Use proper columns or formatting instead.

Resources and Tools

📚 Guidelines

  • • WCAG 2.1 (W3C)
  • • PDF/UA Standard (ISO 14289)
  • • Section 508 Guidelines
  • • Adobe Accessibility Resources

🛠️ Tools

  • • Adobe Acrobat Pro
  • • NVDA Screen Reader (free)
  • • PAC 2021 (free checker)
  • • Color Contrast Analyzers

🎓 Training

  • • W3C WAI Tutorials
  • • Deque University
  • • WebAIM Resources
  • • Adobe Accessibility Training

Conclusion

Creating accessible PDFs is both a legal requirement and a moral imperative. By following WCAG 2.1 Level AA guidelines—ensuring proper document structure, adding alternative text, maintaining sufficient contrast, establishing logical reading order, and testing with assistive technologies—you create documents that work for everyone. Start accessibility at the source document level, use automated tools to catch common issues, and always test with real users and assistive technologies. Remember: accessibility benefits everyone, not just people with disabilities. Clear structure, good contrast, and logical navigation improve usability across the board. Make accessibility a standard part of your document creation workflow, not an afterthought.

Create Accessible PDFs

Build inclusive documents that work for everyone with our accessibility tools.

Get Started