EN 301 549

What it is, what it requires and how it affects e-learning?

EN 301 549 is the European standard that sets out the accessibility requirements for information and communication technology ?(ICT) products and services. Published jointly by CEN, CENELEC and ETSI, it is the technical document that turns accessibility guidelines into enforceable requirements within the European Union, and the usual reference in public procurement specifications. In corporate training, it is the standard against which an LMS, an authoring tool or an e-learning course is assessed when a legal requirement or a public tender is involved.

What EN 301 549 is and who publishes it

It is developed jointly by the three European standardization bodies: CEN, CENELEC and ETSI, through a joint working group on human factors and eAccessibility. It is not a law and no parliament approves it: it is a technical standard.

What makes it legally relevant is its status as a harmonised standard. When the European Commission cites a standard’s reference in the Official Journal of the European Union in support of a directive, complying with that standard grants a presumption of conformity with the requirements of that directive. It is a convenient mechanism for everyone involved: the legislator sets the objective — that products be accessible — and the standard spells out how that is demonstrated. For a company, the practical consequence is that it can evidence compliance through a technical standard instead of having to interpret a legal text.

That mechanism comes with important small print, and it explains much of the confusion you will see below: the presumption only exists if the standard has been cited, and only for the directive it was cited under.

What EN 301 549 requires: its structure by clause

The standard isn’t a single list of requirements, but a set of clauses that apply depending on the type of product or service. That organization is what makes it possible to assess an LMS, a mobile app or a downloadable document against different criteria. These are the ten main clauses and what each one implies in a training context.

Of those ten clauses, three account for almost all of an L&D team’s work: clause 9 for whatever is published on the web, clause 10 for whatever is downloaded and clause 11 for whatever is installed. And one frequent mistake is worth underlining: it is very common to meet clause 9 and breach clause 10. An organization can have an impeccable campus and hand out its supporting material as PDFs with no structural tagging, no reading order and no alternative text, which puts those documents out of reach of a screen reader. As far as the standard is concerned, that is every bit as real a failure as one on the web.

How EN 301 549 relates to WCAG

Clauses 9, 10 and 11 don’t invent criteria of their own: they incorporate WCAG by reference. That is why the two frameworks are always cited together, and also why they get confused. The useful distinction is this: WCAG says how accessible content has to be; EN 301 549 says which parts of an ICT product or service have to meet it and what else is required on top.

Each version of the standard freezes a specific version of the guidelines, which is why the question of which version applies isn’t a bureaucratic detail: it determines which criteria are enforceable.

Which version carries legal weight today

Verified in October 2026. This section depends on a European Commission decision and is worth checking before using it as a reference: the situation was expected to change in late 2026.

The version with legal effect is V3.2.1, from March 2021, which incorporates WCAG 2.1 Level AA. Its reference is cited in the Official Journal through Commission Implementing Decision (EU) 2018/2048, as amended by Implementing Decision (EU) 2021/1339, in August 2021, in support of Directive (EU) 2016/2102 on the accessibility of public sector websites and mobile applications.

V4.1.1 exists but does not yet grant a presumption of conformity. It was published on 2 September 2026 and incorporates WCAG 2.2 — six new Level A and AA criteria — reworks the user preference requirements, updates real-time communication and adds annexes mapping it to European accessibility legislation. But a harmonised standard has no effect until its reference is cited in the Official Journal, and at the time of writing that citation had not been published. It was expected around 30 November 2026, with a window for withdrawing conflicting national standards running to May 2028.

What to do in the meantime. The sensible approach is to treat V3.2.1 as the enforceable minimum and design against V4.1.1. The difference between the two is the criteria added by WCAG 2.2, which will be mandatory at some point; building them in now avoids redoing the work, and none of them makes a course that already meets the earlier version any less accessible.

EN 301 549 and the European Accessibility Act: a frequent confusion

Here is a nuance that almost no explanatory content picks up and that can have practical consequences if taken for granted. The question is whether complying with EN 301 549 is enough to evidence conformity with the European Accessibility Act — Directive (EU) 2019/882 — applicable since June 2025 and covering products and services aimed at consumers. Sources disagree, and it is worth knowing both positions.

The argument that it isn’t enough rests on Article 15(1) of that directive, which grants a presumption of conformity only to harmonised standards whose reference is published in the Official Journal in support of that particular directive. EN 301 549 is cited in support of a different one — the public sector web directive — so, on that reading, it produces no presumption for the EAA and conformity has to be evidenced directly against the requirements in its Annex I. Those who hold this position also point out that, although the corresponding standardization request was adopted in 2022, as of mid-2026 no harmonised standard had been cited for that directive.

The argument that it is enough is the one much of the industry assumes, resting on the fact that the Commission expressly commissioned the update of the standard to support the EAA and that V4.1.1 includes annexes mapping its essential requirements. It is a reasonable position, but it rests on an expectation: that the citation will eventually happen.

What follows from all this in practice. While the situation remains unresolved, the prudent approach is to:

• Use the results of testing against EN 301 549 as supporting evidence, not as a certificate of compliance.
• Tie that evidence to the applicable Annex I requirements, one by one, if your service falls within the scope of the EAA.
• Avoid writing “fully conformant” in an accessibility statement. An honest statement says what is met, what isn’t and with what remediation plan, and that is what is expected of it anyway.
• Not wait for a future version to get started: the legal obligations are already in force regardless of the state of the standards.

This entry is explanatory and does not constitute legal advice. For a specific decision on scope and on your organization’s obligations, consult specialist counsel.

EN 301 549 and the U.S. accessibility framework

In the United States the equivalent requirements come from two different places, and they apply to different organizations. Neither of them is EN 301 549, but all three work the same way: the law sets the obligation and a technical standard says how it is demonstrated.

Federal procurement. Section 508 of the Rehabilitation Act, through the ICT Standards and Guidelines refreshed in 2017, is the reference for federal agencies that develop, procure, maintain or use ICT. It incorporates WCAG 2.0 Level A and AA by reference, and applies it not only to web content but also to non-web documents and software. If you sell a training platform to a federal agency, this is the standard they will ask you about. Note the version gap: the refresh still references WCAG 2.0, not 2.1 or 2.2.

State and local government. The Department of Justice’s final rule under Title II of the ADA, published in April 2024, sets WCAG 2.1 Level AA as the technical standard for the web content and mobile apps of state and local government entities. The compliance dates were later extended: 26 April 2027 for entities serving 50,000 people or more, and 26 April 2028 for smaller entities and special districts.

Where EN 301 549 still matters for a U.S. organization. If you sell training products or services into the European Union — whether through public sector tenders or as consumer-facing services under the European Accessibility Act — EN 301 549 is the standard you will be measured against, regardless of whether you already meet Section 508. The overlap is substantial, because all three frameworks lean on WCAG, but the versions differ and EN 301 549 adds clauses that Section 508 handles differently.

The consequence for a training team is that the level of requirement depends less on the type of content than on who it is for: internal training at a private company, training sold as a service to consumers, and training delivered to a public body sit in three different frameworks.

What EN 301 549 means for an L&D team

Translated into concrete decisions, the standard shows up in three places: what you require of your suppliers, how you produce content and what you state publicly.

What changes in content production

The practical requirement is that the tool produce accessible output by default — semantic HTML, correct ARIA labels, a coherent focus order, export that screen readers can read — because if every course needs manual intervention in the code after publishing, compliance doesn’t hold up over time. You have the detail in our guide on how to create accessible content and in the article on accessible e-learning design, with the overview in accessibility in e-learning.

What to declare and how

A useful accessibility statement is one that distinguishes between what is conformant, what is not and what is exempt, with an assessment date and method. Saying “fully conformant” when you have not audited clause by clause is the riskiest of the three mistakes, because it turns a technical gap into a false claim. If you want a first measurement of the state of your courses, you can start with an accessibility test.