EAA 2026 for E-Commerce: Making Product PDFs Accessible
If your online store serves EU customers, your product catalogs, user manuals, and policy documents are in scope for the European Accessibility Act (EAA). Enforcement started June 28, 2026.
Most e-commerce teams focus on website accessibility — color contrast, keyboard navigation, ARIA labels. Documents are the blind spot. This post explains exactly what EAA requires for PDFs, which e-commerce documents are in scope, and the fastest path to compliance.
Which e-commerce documents fall under EAA?
EAA Article 2 puts your business in scope if you sell products or services online to EU consumers. The documents you publish as part of that commerce relationship must also comply.
Common e-commerce PDFs that fall in scope:
- Product catalogs — downloadable catalogs linked from product pages
- User manuals and installation guides — shipped or linked for physical products
- Terms and conditions — legally required; often published as PDF
- Return and refund policies — frequently PDF on larger retailers
- Warranty documents — mandatory for consumer goods
- Invoice templates — if provided for download
If a customer with a disability cannot access these documents independently using a screen reader or mobile device, that is an EAA violation.
What does “accessible PDF” actually mean under EAA?
EAA requires compliance with EN 301 549, which references WCAG 2.1 Level AA. For documents, that means:
| Requirement | What it means in practice |
|---|---|
| Tagged PDF structure | Text and headings readable by screen readers |
| Alt text on images | Product photos in catalogs need descriptions |
| Correct reading order | Logical flow through multi-column layouts |
| Color contrast ≥4.5:1 | Text on colored backgrounds |
| WCAG 1.4.10 Reflow | No horizontal scrolling at 320px width |
The last requirement is where most e-commerce teams hit a wall.
Why product catalogs almost always fail Reflow
Product catalogs are typically designed in InDesign or similar tools. They use multi-column layouts, embedded tables, overlapping images, and custom typography.
When you export to PDF and run a standard accessibility check (PAC 2024, Adobe Acrobat Accessibility Checker), you can fix the tagging and alt text. But the fixed-layout nature of PDF means the file cannot reflow at 320px width. It requires horizontal scrolling. That fails WCAG 1.4.10.
This is structural, not a remediation failure. No amount of PDF tagging fixes it. The format is the problem.
Two paths to EAA compliance for e-commerce documents
Path 1: Remediate the PDF
- Use Adobe Acrobat Pro or a professional PDF remediation service
- Fix tagging, alt text, reading order, color contrast
- Accept that multi-column catalogs will not pass WCAG 1.4.10 Reflow
- Cost: €50–€200 per document for professional remediation
This works for simple, single-column documents (T&Cs, invoices). For designed catalogs: partial compliance at best.
Path 2: Convert to EPUB3
EPUB3 is HTML5-based and reflowable by design. WCAG 1.4.10 is satisfied structurally — the format adapts to any screen width automatically.
For e-commerce businesses with PDF catalogs or manuals:
- Upload the PDF to toolkit.bot/pdf2epub
- Receive a accessible EPUB3 in under 30 seconds
- Publish the EPUB3 alongside or instead of the PDF
No per-document remediation cost. The accessible version is produced automatically. For large catalogs updated seasonally, the API ($29/month) integrates into your publishing workflow.
Practical checklist for e-commerce compliance
- Audit which PDFs are linked from your EU-facing store pages
- Identify which are simple (T&C, invoices) vs designed (catalogs, manuals)
- For simple documents: run through Acrobat accessibility checker and fix issues
- For designed documents: convert to EPUB3 with toolkit.bot
- Update links on product pages to point to accessible versions
- Add ACE by DAISY validation report to your compliance documentation
Convert any PDF to accessible EPUB3 automatically — no account required for the free tier.
Try free → See pricing