What Are the PDF Accessibility Requirements Under the EAA?

PDF documents remain ubiquitous in business communications—from product specifications and user manuals to invoices, contracts, and marketing materials. Under the European Accessibility Act, businesses must ensure that documents provided as part of covered services are accessible to people with disabilities by the June 28, 2025 deadline. This requirement affects countless PDFs used in e-commerce, banking, transport, and other sectors covered by the EAA. Understanding PDF accessibility under the EAA means knowing what documents are covered, what technical standards apply, and how to create or remediate PDFs to meet compliance requirements.

Key Takeaways

PDF accessibility under the EAA requires businesses to make digital documents usable by people with disabilities.

• PDFs provided as part of covered services must be accessible, including product information, receipts, statements, and support documentation
• EN 301 549 establishes the technical standard for document accessibility, incorporating requirements from WCAG and PDF/UA
• Proper PDF tagging is essential, creating a logical structure that assistive technologies can interpret and convey to users
• Alternative formats may satisfy requirements when creating accessible PDFs isn't feasible, though accessible PDFs are strongly preferred
• Automated tools can help but manual review is necessary for full accessibility, particularly for complex documents

Which Documents Fall Under EAA Requirements?

The EAA doesn't regulate documents in isolation—it covers documents as part of the services it regulates. Understanding which documents are affected requires understanding the service context.

Documents Covered by the EAA

Documents provided as part of covered services must be accessible. This includes:

E-commerce documents:

• Product specifications and datasheets
• User manuals and instructions
• Terms and conditions
• Privacy policies
• Order confirmations and receipts
• Shipping and tracking information
• Return policies and instructions

Banking and financial services documents:

• Account statements
• Transaction records
• Terms of service
• Fee schedules
• Product disclosure documents
• Loan and credit agreements

Transport services documents:

• Booking confirmations
• Tickets and boarding passes
• Travel itineraries
• Terms and conditions of carriage
• Accessibility information

E-books and electronic publications:

• The publications themselves
• Documentation about how to access them
• Help and support materials

Document Delivery Context

The requirement applies regardless of how documents are delivered:

• Downloadable PDFs from websites
• Email attachments sent to customers
• In-app document viewers
• Documents linked from product pages
• Self-service portal documents

If a document is part of the service experience and provided to consumers, it must be accessible.

Documents Not Directly Covered

Some documents fall outside direct EAA scope:

• Internal business documents not shared with consumers
• Documents used exclusively in B2B contexts
• Marketing materials that aren't part of the service delivery (though accessibility best practices still apply)
• Documents for products and services outside EAA categories

However, many businesses choose to make all documents accessible regardless of strict legal requirements, recognizing the broader benefits.

Technical Standards for PDF Accessibility

The EAA points to EN 301 549 as the harmonized standard, which in turn incorporates requirements from multiple accessibility frameworks.

EN 301 549 Document Requirements

EN 301 549 Section 10 covers non-web documents, establishing requirements that parallel WCAG but apply to document formats including PDF. Key requirements include:

Perceivable content:

• Text alternatives for non-text content
• Captions and alternatives for audio/video content in documents
• Adaptable content structure
• Distinguishable visual presentation (contrast, text sizing)

Operable documents:

• Keyboard accessibility for interactive PDF features
• Timing considerations for any time-limited interactions
• Avoidance of content that causes seizures

Understandable documents:

• Readable text (language identification)
• Predictable document behavior
• Input assistance for interactive forms

Robust documents:

• Compatibility with assistive technologies
• Proper tagging and structure

PDF/UA (ISO 14289-1)

PDF/UA (Universal Accessibility) is the ISO standard specifically for accessible PDFs. While EN 301 549 doesn't explicitly require PDF/UA compliance, following PDF/UA provides a clear technical pathway to meeting EN 301 549 requirements for PDF documents.

PDF/UA requirements include:

• All content must be tagged
• Tags must reflect logical reading order
• All meaningful images must have alternative text
• Form fields must have labels and descriptions
• Document must specify its natural language
• Fonts must be embedded and allow text extraction
• Document security must not prevent assistive technology access

WCAG Alignment

For documents accessible via the web (downloadable PDFs, online document viewers), WCAG 2.1 AA requirements apply through EN 301 549's incorporation of those standards. This creates consistent expectations across web content and web-accessible documents.

Creating Accessible PDFs

Creating accessible PDFs from the start is more efficient than remediating existing inaccessible documents.

Source Document Best Practices

Most PDFs originate from other applications—Word, InDesign, PowerPoint—and the accessibility of the PDF depends heavily on the source document.

In Microsoft Word:

• Use built-in heading styles (Heading 1, Heading 2, etc.) rather than manual formatting
• Add alt text to images through the image properties
• Use the built-in table feature with header rows identified
• Create lists using the bullet/numbered list features
• Run the Accessibility Checker before exporting

In Adobe InDesign:

• Define articles to establish reading order
• Apply paragraph styles that map to PDF tags
• Add alt text to graphics through Object Export Options
• Set document language in File > File Info
• Export with tagged PDF option enabled

In Google Docs:

• Use heading styles from the toolbar
• Add alt text to images (right-click > Alt text)
• Create proper tables with header rows
• Use built-in list formatting

PDF Export Settings

When creating PDFs from source documents:

Adobe Acrobat PDF export:

• Enable "Create Tagged PDF"
• Include document structure
• Create bookmarks from headings
• Set document language
• Include alternative text

Microsoft Office export:

• Use "Save as PDF" with "Document structure tags for accessibility" checked
• Enable "Create bookmarks using Headings"
• Verify the accessibility checker shows no issues before export

Direct PDF Authoring

When creating PDFs directly in Acrobat Pro or similar tools:

• Add tags manually using the Tags panel
• Establish reading order through the Order panel
• Set document language in File > Properties > Advanced
• Add alt text to figures and decorative images
• Create form fields with proper labels
• Run the Accessibility Checker

PDF Tagging Deep Dive

Tagging is the foundation of PDF accessibility. Tags create a logical structure that assistive technologies use to present document content.

Essential Tag Types

Document structure tags:

• `<Document>` - Root element containing all content
• `<Part>` - Major document divisions
• `<Sect>` - Document sections
• `<Div>` - Generic container

Heading tags:

• `<H1>` through `<H6>` - Heading hierarchy
• Must reflect logical document structure, not visual appearance
• H1 typically used for document title

Paragraph and text tags:

• `<P>` - Paragraphs
• `<Span>` - Inline text variations
• `<Quote>` - Quotations
• `<Note>` - Notes and annotations

List tags:

• `<L>` - List container
• `<LI>` - List item
• `<Lbl>` - List item label (bullet or number)
• `<LBody>` - List item content

Table tags:

• `<Table>` - Table container
• `<TR>` - Table row
• `<TH>` - Table header cell
• `<TD>` - Table data cell

Figure and formula tags:

• `<Figure>` - Images and graphics (must have alt text)
• `<Formula>` - Mathematical expressions

Link and reference tags:

• `<Link>` - Hyperlinks
• `<Reference>` - Cross-references
• `<Annot>` - Annotations

Reading Order

Tags must be arranged in logical reading order—the order a screen reader should present content. This may differ from the visual layout, particularly for:

• Multi-column layouts
• Sidebars and callout boxes
• Headers and footers
• Floating images and captions

Use Acrobat's Reading Order tool or Order panel to verify and adjust reading sequence.

Common Tagging Errors

Missing tags: Content appears visually but has no tag structure. Screen readers may skip it or present it out of order.

Wrong tag types: Using `<P>` for headings or `<Span>` for paragraphs breaks the logical structure.

Incorrect nesting: Tags must nest properly (e.g., list items inside lists, table cells inside rows).

Decorative content not marked: Purely decorative images should be marked as artifacts, not tagged as figures.

Missing alt text: Figures without alternative text provide no information to screen reader users.

Remediating Existing PDFs

Many businesses have extensive libraries of existing PDFs that need accessibility remediation.

Assessment Process

Automated checking: Use Adobe Acrobat's Accessibility Checker or tools like PAC (PDF Accessibility Checker) to identify technical issues.

Manual review: Automated tools can't catch everything. Manually verify:

• Logical reading order
• Quality of alternative text
• Appropriate heading hierarchy
• Table header associations
• Color contrast
• Meaningful link text

Prioritization: With limited resources, prioritize:

1. High-traffic documents (most downloaded)
2. Essential service documents (terms, receipts, statements)
3. Recently updated documents
4. Documents in active use

Remediation Techniques

In Adobe Acrobat Pro:

Adding tags to untagged PDFs:

1. Open the PDF in Acrobat Pro
2. Go to Accessibility > Autotag Document
3. Review and correct auto-generated tags in the Tags panel
4. Manually adjust reading order in the Order panel
5. Add alt text to figures
6. Run the Accessibility Checker

Fixing tag structure:

1. Open the Tags panel
2. Drag tags to correct positions
3. Change tag types using right-click > Properties
4. Delete empty or redundant tags
5. Add missing tags by selecting content and choosing "Create Tag from Selection"

Adding alternative text:

1. Select the figure tag in the Tags panel
2. Right-click > Properties
3. Enter alternative text in the Alternate Text field
4. For decorative images, mark as artifact instead

When to Start Over

Sometimes remediation isn't practical. Consider recreating the PDF when:

• The source document is available and well-structured
• The PDF was created from scanned images without OCR
• The tag structure is so broken that fixing requires more effort than recreation
• The document is scheduled for update anyway

Accessible Alternatives to PDF

The EAA allows for accessible alternatives when making the primary format accessible isn't feasible, though accessible PDFs are preferred.

When Alternatives May Be Appropriate

Legacy documents: Historical documents that aren't worth the remediation investment.

User-generated content: Documents uploaded by users that can't be automatically remediated.

Highly complex documents: Technical drawings or specialized formats that are inherently difficult to make accessible.

Interim solutions: Temporary alternatives while working toward full PDF accessibility.

Types of Accessible Alternatives

HTML versions: Web-based versions of documents offer native accessibility features and often provide better experiences than PDFs for screen reader users.

Large print versions: For users with low vision, providing large print versions may supplement (not replace) accessible PDFs.

Audio versions: Audio descriptions or recordings of document content can provide access for some users.

Human assistance: Offering to provide information through customer service can be an interim measure, though it shouldn't be the only option.

Requirements for Alternatives

When providing alternatives:

• The alternative must contain equivalent information
• The alternative must be as easy to access as the original
• Users should be able to choose their preferred format
• The existence of alternatives should be clearly communicated

Note that providing alternatives doesn't fully satisfy EAA requirements if creating accessible PDFs is feasible. Alternatives are meant for exceptional cases, not as a general substitute for document accessibility.

Testing PDF Accessibility

Regular testing ensures ongoing compliance and catches issues before they affect users.

Automated Testing Tools

Adobe Acrobat Accessibility Checker:

• Built into Acrobat Pro
• Checks tag structure, reading order, alt text, and more
• Generates reports with issues and remediation suggestions

PAC (PDF Accessibility Checker):

• Free tool for checking PDF/UA compliance
• Provides detailed technical feedback
• Available from the PDF/UA Foundation

CommonLook PDF Validator:

• Comprehensive accessibility testing
• Checks against multiple standards (WCAG, PDF/UA, Section 508)
• Detailed remediation guidance

Manual Testing Checklist

Automated tools catch many issues but miss others. Manual testing should verify:

• [ ] Reading order matches logical content sequence
• [ ] Heading hierarchy is correct and complete
• [ ] Alt text is accurate and sufficiently descriptive
• [ ] Tables have properly associated headers
• [ ] Links have meaningful text (not "click here")
• [ ] Form fields have labels and instructions
• [ ] Language is correctly specified
• [ ] Color contrast is sufficient
• [ ] No content is conveyed by color alone
• [ ] Document can be navigated with bookmarks

Screen Reader Testing

Test with actual screen readers to verify user experience:

NVDA (Windows): Free, widely used screen reader JAWS (Windows): Commercial screen reader VoiceOver (Mac/iOS): Built into Apple devices TalkBack (Android): Built into Android devices

When testing with screen readers, verify:

• All content is read in correct order
• Headings, lists, and tables are announced correctly
• Images are described appropriately
• Forms are usable
• Links can be navigated

Frequently Asked Questions

Do all my PDFs need to be accessible by June 28, 2025?

PDFs provided as part of covered services must be accessible by the deadline. This includes documents currently being distributed and those that will be distributed after June 28, 2025. Prioritize documents that are actively used in service delivery.

Is it acceptable to provide information as an HTML page instead of a PDF?

Yes, HTML pages can be more accessible than PDFs and are a valid way to provide document-based information. However, if you offer a PDF download option, that PDF should also be accessible. Don't provide inaccessible PDFs alongside accessible HTML versions.

What about scanned PDFs of paper documents?

Scanned image PDFs are inherently inaccessible because they contain images of text rather than actual text. For compliance, scanned PDFs must be OCR-processed (optical character recognition) to create actual text content, then properly tagged. The OCR quality must be verified for accuracy.

How do I handle third-party PDFs that I distribute?

If you distribute PDFs created by third parties (manufacturers, partners, regulators), you're still responsible for their accessibility when they're part of your covered service. Work with third parties to obtain accessible versions, or create accessible alternatives.

Can I use automated tools to make PDFs accessible?

Automated tools help but can't achieve full accessibility alone. Tools can add basic tags and identify issues, but human review is needed to verify reading order, write appropriate alt text, and ensure logical structure. Consider automated remediation as a starting point requiring human refinement.

What's the relationship between PDF/UA and EAA compliance?

PDF/UA is a technical standard specifically for PDF accessibility. EN 301 549 (the harmonized standard for EAA) doesn't explicitly require PDF/UA, but following PDF/UA provides a clear pathway to meeting EN 301 549's document accessibility requirements. PDF/UA compliance is generally considered best practice for EAA compliance.

Related Resources

• ADA vs. EAA Compliance Comparison: Understanding Both Standards
• WCAG 2.2 Compliance Guide: Meeting the Latest Standards
• Best Shopify Accessibility Tool 2025: Automated Testing Solutions

This article was crafted using a cyborg approach—human expertise enhanced by AI to deliver practical guidance on PDF accessibility compliance under the European Accessibility Act.