Briefing
The European Accessibility Act Reached Your Manuals
The Deadline That Already Passed
June 2025 Was the Start Line
The EAA's obligations applied from June 28, 2025, across a defined range of products and services sold into the EU — and with them, the digital content those products and services carry: instructions, support documents, customer-facing files. The measuring stick is the harmonized standard EN 301 549, which for documents means WCAG 2.1 Level AA — real headings, explicit reading order, text alternatives, semantic tables. The accepted pattern is at least one genuinely accessible format per content item, plus a statement saying which. And 2026 is the year enforcement became concrete, with national authorities — the Dutch regulator visibly among them — opening cases.
For organizations whose customer content is a library of exported PDFs, this lands on a familiar bruise: those files are photographs of documents, and a photograph has no headings to declare.
The Fork
Remediate Forever, or Fix the Source
The reflex response is remediation: hire the taggers, fix the files. For a small, static set that's correct. For a living estate it's a treadmill — labor applied to output, re-applied at every revision, non-compliant again the moment one untagged export ships. The scalable answer is upstream, and it's the argument this site keeps making with a legal deadline now attached: a screen reader is a machine reader, and machine readers are served by structure, not paint. Content whose headings, order, alternatives, and tables are real at the source renders to accessible HTML and properly tagged PDF through a single-source pipeline — conformance achieved once, in the model and the template, inherited by everything after.
The practical sequence mirrors every estate problem we've written about: serve the library through a platform that can offer an accessible rendition alongside the PDF, move the living document families to structured authoring, and let remediation handle only the static tail. Firms selling into the EU have a compliance clock running either way. The choice is whether each tick costs a tagging invoice — or nothing, because the structure was already true.
FAQ
Questions We Hear
What is the European Accessibility Act, and when did it bite?
An EU directive setting accessibility requirements for a defined range of products and services sold in the EU — consumer devices and terminals, e-commerce, banking, e-books, transport services, and more. Its obligations applied from June 28, 2025, and 2026 is when enforcement stopped being theoretical: national authorities have begun pursuing cases, with the Dutch regulator among the visibly active. For documentation teams the key point is scope: the requirements extend to the digital content around in-scope products and services — the instructions, support documents, and customer-facing files, not just the app's buttons.
What standard are documents measured against?
The harmonized European standard EN 301 549, which for documents effectively means WCAG 2.1 Level AA: real heading structure, reading order, text alternatives for images, sufficient contrast, machine-readable language, tables that are tables. A PDF or download that meets WCAG 2.1 AA is aligned with EN 301 549; providing at least one genuinely accessible format of the content — accessible HTML, EPUB, or a properly tagged PDF — is the accepted pattern, alongside an accessibility statement saying which formats those are.
Why doesn't per-document remediation scale?
Because remediation is manual labor applied to output. Tagging one PDF properly is a real job; doing it for a thousand-file library, and again for every revision of every file forever, is a treadmill — and the moment an untagged revision ships, you're non-compliant again. Remediation vendors are the right answer for a small static set and the wrong economics for a living document estate. The estate-scale answer is upstream: content whose structure is real at the source, so every rendition inherits accessibility instead of having it painted on.
How does structured content change the compliance math?
Structured content is accessibility's raw material: headings that are declared, reading order that is explicit, images with text alternatives as data, tables with semantics. Render that source to HTML and to tagged PDF through a proper pipeline and conformance is substantially a by-product — achieved once in the template and the model, inherited by every document and every revision after. It's the same one battle we keep describing: the structure that serves screen readers is the structure that serves search, integrations, and AI. Regulated accessibility just added a legal deadline to the argument.
Get In Touch
Off the Remediation Treadmill
If EAA compliance currently means a per-PDF invoice, the economics say fix the source. We build the structured pipelines where accessibility is a by-product, not a project.