Make Accessible PDF WCAG Compliance Guide: Create ADA Compliant PDFs

Quick start: make a PDF accessible in 5 minutes

If you're starting from a document that needs to be WCAG compliant, here's the fastest workflow to create an accessible PDF:

1. Use a properly structured source document. Create your content in Word, Google Docs, or another word processor using proper heading styles (Heading 1, Heading 2, etc.), not manual formatting.
2. Export with accessibility features. When saving as PDF, choose options that preserve tags and document structure.
3. Verify and remediate. Use accessibility checking tools to identify and fix any issues.
4. Add alternative text. Describe images and visual content for screen readers.
5. Set document language. Specify the primary language in document properties.

What WCAG compliance means for PDFs

The Web Content Accessibility Guidelines (WCAG) are international standards for making digital content accessible to people with disabilities. While WCAG was originally designed for websites, the principles apply equally to PDF documents, which are essentially fixed-layout digital documents.

Why WCAG matters for PDFs

• Inclusive access: WCAG compliant PDFs work with screen readers, screen magnification, and keyboard navigation.
• Legal compliance: The ADA, Section 508, and EN 301 549 require accessible content in many contexts.
• SEO benefits: Accessible documents often rank better because they have clear structure and metadata.
• < broader audience: Accessible PDFs serve users with visual, motor, and cognitive disabilities.

How PDF accessibility works

Screen readers and assistive technologies navigate PDFs through tags—invisible structural elements that define the document hierarchy. A properly tagged PDF tells a screen reader "this is a heading," "this is a paragraph," "this is a link," and "this image has this description." Without tags, screen readers treat all text as plain content with no structure.

WCAG 2.1 PDF requirements checklist

To meet WCAG 2.1 Level AA (the most common compliance target), your PDF must satisfy these requirements:

PDF accessibility basics: tags, reading order, and structure

Understanding the three core concepts of PDF accessibility will help you create compliant documents from the start:

1. Tags

Tags are the structural backbone of an accessible PDF. They define what each piece of content is and how it relates to other content. Common tag types include:

• Document (Root): The container for all other tags.
• H1-H6: Heading levels for document hierarchy.
• P: Paragraph text.
• LI: List items within ordered or unordered lists.
• Table, TR, TH, TD: Table structure with headers.
• Link: Hyperlinks with accessible link text.
• Figure: Images and graphics with alternative text.

2. Reading Order

Reading order determines the sequence in which screen readers announce content. A PDF with correct reading order will make sense when read aloud from beginning to end.

Incorrect reading order often occurs in:

• Multi-column layouts where columns aren't properly tagged.
• Documents with overlaid text or watermarks.
• Forms with fields out of logical sequence.

3. Document Structure

Proper document structure includes:

• Logical hierarchy: H1 for main title, H2 for major sections, H3 for subsections.
• List consistency: All lists should be properly tagged with items.
• Table headers: Tables must have header rows or columns identified.
• Semantic markup: Use actual headings, not oversized bold text.

Step-by-step: create an accessible PDF from scratch

The best approach to accessible PDFs is to build accessibility into your source document. Follow these steps for Word, Google Docs, or similar word processors:

Step 1: Set up document properties

• Set the document title (not just the filename).
• Define the primary language in language settings.
• Use a standard sans-serif font at readable sizes (minimum 12pt body, 14pt if possible).

Step 2: Use styles for formatting

• Always use Heading 1, Heading 2, Heading 3 for hierarchy.
• Use Paragraph style for body text.
• Avoid manual formatting—styles ensure consistent structure.
• Don't use spaces or line breaks to create spacing; use paragraph spacing in styles.

Step 3: Create accessible lists and tables

• Use built-in list formatting (bullet and numbered lists).
• Keep tables simple with clear header rows.
• Avoid merged cells when possible—they complicate accessibility.
• Don't use tables for layout; use them only for tabular data.

Step 4: Add alternative text to images

• Right-click images and select "Alt Text" or equivalent.
• Write concise descriptions (1-2 sentences maximum).
• Describe the information the image conveys, not just what it looks like.
• For decorative images, mark as "decorative" rather than adding alt text.

Step 5: Create accessible links

• Use descriptive link text ("download the annual report" not "click here").
• Avoid URLs as link text when possible.
• Check that links work correctly and go to the intended destination.

Step 6: Export as PDF with accessibility

When saving as PDF:

• Choose "PDF" as the format.
• Select options to "Create bookmarks" and "Use headings."
• Enable "Document structure tags" or "Accessibility."
• Verify the exported PDF with an accessibility checker.

Remediate existing PDFs for accessibility

If you have an existing PDF that needs accessibility remediation, follow this systematic approach:

Step 1: Run an accessibility check

Use tools to identify what's wrong:

• Adobe Acrobat Pro: Tools > Accessibility > Full Check/Accessibility Check.
• PAC 2024: Free European accessibility validator.
• Online tools: Various web-based accessibility checkers.

Step 2: Add or repair tags

Most accessibility issues stem from missing or incorrect tags:

• Use "Add Tags to Document" in Acrobat or equivalent tools.
• Review the tag tree and fix incorrect parent-child relationships.
• Ensure headings follow proper nesting (H1 → H2 → H3, never H1 → H3).

Step 3: Fix reading order

• Open the Reading Order pane.
• Review the visual order against the tagged order.
• Reorder elements to match logical reading sequence.
• Pay special attention to multi-column layouts and sidebars.

Step 4: Add alternative text

• Select each image in the Reading Order or Content pane.
• Enter alternative text that describes the image's purpose or content.
• For complex charts, provide detailed descriptions beyond the figure.

Step 5: Set document properties

• Open File > Properties > Advanced.
• Set the document language (English, Spanish, etc.).
• Ensure the title field is filled in.

Step 6: Test with a screen reader

The ultimate test is how a screen reader experiences your document:

• NVDA: Free Windows screen reader (nvdaproject.org).
• VoiceOver: Built into macOS (Control + Option + F5 to activate).
• JAWS: Commercial option with trial version available.

Verify accessibility with testing tools

After creating or remediating a PDF, use these tools to verify WCAG compliance:

Desktop Tools

Manual Testing Checklist

Automated tools catch most issues, but manual testing is essential:

• Screen reader test: Navigate the entire document with a screen reader.
• Keyboard test: Try accessing all content using only keyboard navigation.
• Zoom test: Check readability at 200% zoom without horizontal scrolling.
• Color contrast test: Verify text meets 4.5:1 contrast ratio.
• Link test: Confirm all links have descriptive text and work correctly.

Common accessibility issues and fixes

Issue 1: Scanned documents

Problem: Scanned PDFs have no selectable text, only images.

Fix: Run OCR (Optical Character Recognition) to convert images to searchable text, then verify and correct any recognition errors.

Issue 2: Missing alt text on images

Problem: Images are present but have no alternative text descriptions.

Fix: Add alt text to each image, describing its informational content or function.

Issue 3: Improper heading hierarchy

Problem: Document uses bold text for emphasis instead of heading styles, or skips heading levels.

Fix: Use proper heading tags (H1-H6) in sequence without skipping levels.

Issue 4: Complex tables

Problem: Tables with merged cells, nested tables, or missing headers.

Fix: Simplify tables, use row headers, and ensure logical reading order.

Issue 5: Color-dependent information

Problem: Information is conveyed only through color (red/green indicators, gradient scales).

Fix: Add text labels, patterns, or symbols to supplement color cues.

Issue 6: Blank or missing link text

Problem: Links say "click here" or have no text at all.

Fix: Use descriptive link text that indicates the destination or purpose.

Issue 7: Untagged form fields

Problem: Form fields have no labels or accessible names.

Fix: Add proper field labels and ensure fields are tagged correctly.

WCAG compliance levels: A, AA, and AAA explained

WCAG defines three conformance levels, each with increasing requirements:

What level should you target?

For most organizations and use cases, WCAG 2.1 Level AA is the appropriate target because:

• It's the most widely mandated level by law and policy.
• It provides substantial accessibility for most users with disabilities.
• It's achievable for most types of digital content.

Legal requirements: ADA, Section 508, and EN 301 549

Several laws and regulations require accessible PDFs:

Americans with Disabilities Act (ADA)

The ADA prohibits discrimination based on disability and applies to:

• Title III: Places of public accommodation (businesses open to the public).
• Title II: State and local government services.

Courts have consistently ruled that websites and digital documents must be accessible under the ADA, making PDF accessibility a legal requirement for many organizations.

Section 508

Section 508 requires federal agencies to make their electronic and information technology accessible to people with disabilities, including PDFs.

EN 301 549

The European accessibility standard EN 301 549 references WCAG 2.1 and is required for public sector bodies in EU member states under the European Accessibility Act.

Consequences of non-compliance

FAQ (People Also Ask)

Published by LifetimePDF — Pay once. Use forever.