1. The hidden scope: your documents are part of the service
The European Accessibility Act defines its scope at the level of the service, not the page. Directive 2019/882 covers "e-commerce services" and digital services as a whole: an e-commerce service includes its PDF invoice, downloadable T&Cs, subscription contract, catalogue and withdrawal form. The EN 301 549 standard, the compliance benchmark, devotes an explicit clause to "non-web documents" (clause 10) requiring them to meet the same WCAG success criteria as pages.
In practice: if your checkout is flawless but your invoice is an OCR-less scan, a low-vision customer cannot read their own invoice. From that standpoint the service is partially non-compliant — and your accessibility statement must say so (the "partially compliant" status exists precisely for this).
Why nobody thinks about documents
Three reasons recur in our audits: documents are produced by teams that do not do web (accounting, legal, agencies); automated scan tools do not crawl document corpora; and budgets concentrate on high-traffic pages. That is exactly the blind-spot risk profile regulators favour when they want a deterrent example.
2. PDF/UA (ISO 14289): what the standard actually requires
PDF/UA-1 (ISO 14289-1) is the international document accessibility standard. It demands nothing exotic: a PDF must be structured so a screen reader can navigate it in logical order, with the same information a sighted reader gets. Its core requirements:
- Complete, correct tagging: headings (H1-H6), lists, tables with header cells, footnotes, labelled links. No tagging = no accessibility, full stop.
- Logical reading order: the declared reading sequence must follow human reading, including multi-column layouts.
- Replacement text: every meaningful image carries alternative text; decorative images are marked as artifacts (
/Artifact) so they are skipped. - Declared language: the document's main language and foreign passages are tagged — otherwise a screen reader reads French with an English accent.
- Usable forms: every field has an accessible label, coherent tab order and identifiable input errors.
- Colour independence and WCAG 1.4.3-compliant contrast inside the document itself.
- Security without blocking: encryption must not prevent assistive technology from extracting text.
3. The 7 document defects that trigger penalties
- The image-only PDF (scan without OCR): totally opaque to screen readers. Common in contract archives and administrative mail.
- Raw office exports: Word or Excel exported without tagging, where "Heading 1" is just a bigger font — the semantic structure simply does not exist.
- Chaotic reading order: callouts, columns and chapter heads read in an incomprehensible sequence — the most frequent defect in catalogues and annual reports.
- Financial tables without headers: a screen reader rattles off numbers without ever saying which row or column they belong to. Invoices and balance sheets are prime cases.
- Images and infographics without alternatives: result charts, contractual diagrams, clickable logos without labels.
- Unlabelled forms: withdrawal, warranty and refund forms — the service's critical journeys.
- Locked or "signed" PDFs that prevent assistive technology from extracting text.
Each defect is detectable in minutes with the checkers below. What is measured is fixable.
4. Remediation: the industrial workflow and checkers
The strength of document remediation is its mechanical nature: unlike a web journey rebuild, fixing a PDF follows a stable, tooled procedure.
- Inventory: list public documents by use (invoice, contract, T&Cs, catalogue, report) and volume. Prioritise mandatory customer journeys.
- Produce cleanly upstream: structured heading styles in Word/InDesign, export with tagging enabled, alternative text filled at source. An invoice generated by an accessible template engine never needs manual fixing.
- Check: PAC 2024 (free) for PDF/UA checks, Acrobat Pro's Accessibility Checker for editing, veraPDF for batch checks in production pipelines.
- Fix: reading order, headings, alternatives, languages, tables — by batch, starting with high-volume documents (monthly invoices).
- Test with humans: an NVDA (Windows) and VoiceOver (macOS/iOS) pass on critical documents. Automation covers structure, not comprehension.
- Treat scans: quality OCR, re-tagging, and above all stop regenerating image-only PDFs in automated flows (order confirmations, statements).
The single highest-impact target: the invoice
The invoice is the most universally distributed, most frequently regenerated, and most often out-of-quality-process document. It is also, with the e-ticket, squarely within the spirit of the directive (documents linked to a transaction). Fixing invoices first resolves most residual risk for an online merchant.
5. Penalties, statements and how to prioritise
An inaccessible document corpus is analysed as service non-compliance: up to €150,000 per infringement for legal persons, injunctions with daily penalties (up to €1,500/day) and remediation within 30 days. The accessibility statement must cover documents: a statement claiming conformity while leaving invoices unreadable is a false statement, separately penalised. And if your documents serve consent (T&Cs, cookie policy), the GDPR dimension stacks on top.
Our Observatory's recommended order of effort: (1) invoices and transaction documents, (2) contracts and T&Cs, (3) regulatory forms, (4) catalogues and reports, (5) archives. For the web scope, our Digital Accessibility Observatory gathers the complete methodology.