Briefing
EN 301 549 V4.1.1: What Changes for Accessible Manuals
What Was Published
A New Version, Aligned to WCAG 2.2
EN 301 549, “Accessibility requirements for ICT products and services”, is the harmonized European standard behind EU accessibility law, published jointly by CEN, CENELEC, and ETSI. Version 4.1.1 was adopted on 24 August 2026 and published in early September; it is free to download from ETSI.
The headline change: its requirements for web content, non-web documents, and software (clauses 9, 10, and 11) now align with WCAG 2.2 Level A and AA, where version 3.2.1 used WCAG 2.1. WCAG 2.2 added nine success criteria, six of them at Level A or AA, and removed the old parsing criterion. For documentation teams, two clauses matter most: 10, for documents, and 12, for information about products.
Clause 10
What Changed for Documents
- Six new WCAG 2.2 requirements
- Focus not obscured (minimum), dragging movements, target size (minimum), consistent help, redundant entry, and accessible authentication (minimum). Most bite on interactive documents: fillable forms, interactive PDFs, and documents with embedded controls.
- Consistency across a set of documents
- Consistent navigation and consistent identification were void for documents in V3.2.1. They now apply to a document within a set of documents, which is exactly what a multi-volume manual library is: the same navigation and the same names for the same things, volume to volume.
- Respect for the reader's settings
- A new requirement that a document "shall not block" the user agent's ways of presenting it according to the reader's preference settings: no locking out reflow, zoom, or a reader's own colors and fonts.
- Parsing removed, PDF/UA noted
- The parsing requirement is void, following WCAG 2.2. A new note names ISO 14289-1 and ISO 14289-2, the PDF/UA standards, as useful in meeting the standard.
The set-of-documents change is the one most manual libraries will feel. A service manual split across volumes, or a family of manuals for related products, is now expected to behave like one coherent set, which is far easier to guarantee when every volume is generated from one structured source than when each is formatted by hand.
Clause 12
Information About Products
Clause 12 was renamed from “Documentation and support services” to “Information about products and services” and rewritten. Product information made available in digital form must now meet the web, document, or software requirements that fit its form. Documentation must also link to information on the product's accessibility features, how to use them, and how to get support for them.
Just as important is what was removed. Version 3.2.1 let documentation be provided in at least one of several accessible electronic formats; that wording is gone. Read plainly, an accessible HTML version no longer excuses an inaccessible PDF of the same manual, if you publish both.
Legal Status
What It Does and Does Not Oblige Yet
The obligations themselves come from the European Accessibility Act, which has applied since 28 June 2025. Its Annex I requires instructions for use to be publicly available when a product is placed on the market, available through more than one sensory channel, presented understandably, in text formats that can generate assistive formats, and with an alternative for any non-text content. Our briefing on the EAA and your manuals covers the act itself.
A harmonized standard gives a presumption of conformity only once it is cited in the Official Journal of the EU. As of early October 2026, V4.1.1 has not been cited, and no version of EN 301 549 has ever been cited under the EAA; the earlier V3.2.1 is cited only under the Web Accessibility Directive for public-sector bodies. The Commission's AccessibleEU center says V4.1.1 will give presumption under both once cited, but no date has been announced, and no transition period from V3.2.1 has been set.
The practical reading: V4.1.1 is the yardstick that regulators, customers, and procurement teams will reach for, and building to it now avoids doing the work twice. This is a summary of public documents, not legal advice.
What to Do
Six Steps for Documentation Teams
- Audit manual sets, not just single files, for consistent navigation and naming across volumes.
- Make every digital format you publish accessible, not one accessible copy among several.
- Check interactive documents (forms, interactive PDFs) against the new target size, focus, and authentication requirements.
- Add links from your documentation to information on the product's accessibility features, how to use them, and how to get support.
- Produce tagged PDF to PDF/UA, and test that your PDFs and HTML reflow and honor reader settings.
- Fix it in the source and the publishing pipeline, so every revision inherits the fix instead of needing it again.
The last step is the one that scales. Accessibility applied to each PDF after export has to be applied again at every revision; accessibility built into the source and the single-source pipeline is inherited by every output. Our explainer on how XML becomes a PDF shows where tagging happens in that pipeline.
FAQ
Questions We Hear
What is EN 301 549 V4.1.1?
The September 2026 revision of EN 301 549, "Accessibility requirements for ICT products and services", the harmonized European standard published jointly by CEN, CENELEC, and ETSI. It was adopted on 24 August 2026 and is free to download from ETSI.
What changed in EN 301 549 V4.1.1?
Its web, document, and software requirements (clauses 9, 10, and 11) now align with WCAG 2.2 Level A and AA instead of WCAG 2.1. For documents that adds six requirements, applies consistent navigation and identification across sets of documents, and adds a rule against blocking a reader's display preferences. Clause 12 was renamed "Information about products and services" and rewritten.
Is EN 301 549 V4.1.1 mandatory under the European Accessibility Act?
Not as such. The EAA sets the legal requirements, and a harmonized standard gives a presumption of conformity only once it is cited in the Official Journal of the EU. As of October 2026, no version of EN 301 549 has been cited under the EAA. V4.1.1 is still the clearest statement of what accessible means, and the European Commission's AccessibleEU center has said that once cited it will give presumption of conformity under both the EAA and the Web Accessibility Directive.
Does EN 301 549 apply to PDFs and manuals?
Yes. Clause 10 covers non-web documents such as PDFs and word-processing files, and clause 12 covers information about products, including documentation made available in digital form, which must meet the web, document, or software requirements that fit its form.
Which WCAG version does EN 301 549 use?
WCAG 2.2 Level A and AA from V4.1.1 (September 2026). The previous version, V3.2.1, used WCAG 2.1. WCAG 2.2 became a W3C Recommendation on 5 October 2023 and was updated on 12 December 2024.
Get In Touch
Accessible Manuals, Every Revision
We build structured publishing pipelines where accessibility is designed into the source and the templates, so every output and every revision inherits it.