EN 301 549 does not make you EAA compliant, and the Official Journal proves it

If a vendor has told you that conformance with EN 301 549 makes you compliant with the European Accessibility Act, they have sold you a presumption that does not exist. Not "is weak". Does not exist.

Fourteen months after the EAA became applicable, not one harmonised standard has been cited in the Official Journal in support of Directive (EU) 2019/882. Article 15(1) makes the presumption of conformity conditional on exactly that citation. No citation, no presumption.

Most teams get this wrong in three predictable ways:

• they buy an audit against EN 301 549 and file it as proof of compliance, when it is evidence of good practice and nothing more,
• they treat a conformance certificate as a shield, when no accredited certification scheme exists for the EAA at all,
• they never check which directive EN 301 549 is actually harmonised under.

This guide is written for the person who has to defend a compliance position: the founder, the compliance lead, or the advisor being asked "are we covered?"

• Search the Commission's harmonised standards index for Directive (EU) 2019/882. There is no entry. Take a screenshot with the date.
• Open any accessibility audit you have paid for. Check whether it claims conformity with the EAA or conformance with EN 301 549. Those are different sentences.
• Re-anchor your evidence to Annex I of the Directive, requirement by requirement, and keep EN 301 549 as supporting evidence underneath it.
• Record the absence, dated. "No harmonised standard cited as of 14 August 2026" is a defensible statement. "We are EN 301 549 certified" is not.
• If you are a service provider, check your Annex V information actually describes how each applicable Annex I requirement is met, not which standard you tested against.

What a presumption of conformity actually is

Under the New Legislative Framework, EU product and service law sets essential requirements in the legal text, then lets standardisation bodies write technical standards that satisfy them. When the Commission is happy with a standard, it publishes a reference to it in the Official Journal. From that moment, conforming to the standard means you are presumed to conform to the law.

That presumption is the whole reason standards matter commercially. It shifts the burden: a market surveillance authority has to rebut it rather than you having to prove conformity from first principles.

Article 15(1) of the EAA says it plainly:

Products and services which are in conformity with harmonised standards or parts thereof the references of which have been published in the Official Journal of the European Union, shall be presumed to be in conformity with the accessibility requirements of this Directive in so far as those standards or parts thereof cover those requirements.

Read the conditional. The presumption attaches to standards whose references have been published in the Official Journal. It does not attach to standards that merely exist, or that are widely used, or that a vendor calls "the EU accessibility standard".

The verification, four ways

This is a falsifiable claim, so here is how to falsify it yourself.

1. The Commission's harmonised standards index. It is organised by legislation. Open the "Accessibility" sector. It contains exactly one entry, Accessibility of websites and mobile applications of public sector bodies, which supports Directive (EU) 2016/2102. There is no entry for Directive (EU) 2019/882 anywhere in the index.
2. EUR-Lex full-text search. Search the exact phrase "in support of Directive (EU) 2019/882". Zero results. For contrast, the same search for other directives returns the implementing decisions that cite their standards.
3. The secondary legislation register. There are no binding secondary acts based on CELEX 32019L0882. No implementing decision citing standards, and no delegated act elaborating the annexes.
4. EN 301 549's own foreword. The standard states that once it is cited in the Official Journal under Directive 2016/2102, conformance confers a presumption of conformity with the essential requirements of that Directive. The standard itself tells you which law it belongs to.

Legalithm materials are operational guidance only and do not constitute legal advice.

Why the gap exists, and why it is not closing quickly

Article 15(2) required the Commission to request European standardisation organisations to draft harmonised standards for the product accessibility requirements in Annex I, and to submit the first such draft request by 28 June 2021.

The request, M/587 (Commission Implementing Decision C(2022) 6456 final), was adopted on 14 September 2022. That is roughly fifteen months after the deadline in the Directive's own text. Everything downstream inherits that delay.

The current published version of EN 301 549 is V3.2.1, from March 2021. It is cited in the Official Journal by Commission Implementing Decision (EU) 2018/2048, as amended by (EU) 2021/1339, under the Web Accessibility Directive.

A revision aligning to WCAG 2.2 is in progress. As of 12 August 2026 the ETSI deliverables directory shows a public enquiry draft from November 2025 and a final draft for vote dated 24 June 2026. There is no published version. The widely repeated claim that v4.1.1 "will be referenced in the Official Journal in October 2026" has no primary source behind it, and you should not plan around it.

Real-world example: a DACH agency sells a "BFSG-Zertifikat" after an EN 301 549 audit. The audit may be excellent. The certificate still certifies conformance to a standard that carries no legal presumption for the BFSG, and no accredited certification scheme exists for the EAA. The seal is a private mark, not a legal shield.

So what is EN 301 549 good for?

A great deal, as long as you are honest about what it is.

• It is the best available technical specification of what accessible ICT looks like in Europe, and it incorporates WCAG 2.1 Level AA verbatim for web content.
• It is the right thing to test against, because Annex I is written in functional language and does not tell an engineer what to build.
• It is what public sector procurement will ask for, and it is genuinely harmonised under the Web Accessibility Directive, where a presumption does exist.
• It is defensible evidence, provided you present it as evidence rather than as conformity.

What changes is the sentence you write, and what you anchor to.

• ✗ "Our service conforms to EN 301 549, and is therefore compliant with the European Accessibility Act."
• ✓ "Annex I Section III(c) is met. Websites and mobile applications were tested against EN 301 549 clause 9 on 4 November 2026 by an expert reviewer, with results retained."

The second sentence survives a market surveillance request. The first one invites the question you cannot answer.

What to anchor your evidence to instead

Because there is no presumption, conformity is assessed against Annex I directly. Annex I has seven sections, and which of them bind you depends on what you sell:

Article 4(2) applies Sections I and II to products. Article 4(3) applies Section III to all services except urban, suburban and regional transport, and Section IV to all services.

Section VII is the one people miss, and it matters more here than in most instruments precisely because no standard is cited. It is the fallback: where Sections I to VI do not address a function, that function must still be accessible by meeting the functional performance criteria. It also permits substituting a functional criterion for a specific technical requirement, but only where the result is equivalent or better.

Real-world example: a checkout flow uses a novel gesture-based control that no clause of EN 301 549 anticipates. There is no clause to fail. Section VII(g), usage with limited manipulation or strength, still requires at least one mode of operation that does not need fine motor control. The obligation does not disappear because the standard is silent.

Common pitfalls, and how to avoid them

1. Treating a certificate as a defence. No accredited EAA certification scheme exists. Every "certified accessible" mark on the market is a private seal. Some are backed by serious methodology, such as the BIK BITV-Test in Germany. None of them creates a legal presumption.
2. Filing the audit and stopping. An audit is a point-in-time observation. Article 13(3) requires service providers to keep procedures in place so that conformity survives changes in the service, changes in the requirements, and changes in the standards. That third limb is a maintenance obligation.
3. Writing "fully compliant" in the accessibility information. Claiming full conformance while known issues exist converts your own document into evidence against you. Describe what is met, what is not, and what you are doing about it.
4. Assuming a standard will arrive and rescue you. The Directive has been applicable since 28 June 2025. The obligation is live now, and it is measured against Annex I whether or not a standard is ever cited.

Does conformity with EN 301 549 satisfy the European Accessibility Act?

No. EN 301 549 is cited in the Official Journal under Directive (EU) 2016/2102, the Web Accessibility Directive, and not under Directive (EU) 2019/882. Article 15(1) attaches the presumption of conformity only to standards whose references are published in the Official Journal in support of the EAA, and as of 14 August 2026 none has been. Conformity is assessed against Annex I directly.

Is there any EAA certification I can get?

There is no accredited certification scheme for the European Accessibility Act. The Directive runs on self-assessment: for products, the manufacturer performs the conformity assessment in Annex IV, draws up an EU declaration of conformity and affixes the CE marking, with no notified body involved. For services there is no declaration of conformity at all, only the Annex V information.

When will a harmonised standard be cited under the EAA?

Nobody has published a date that is backed by a primary source. The standardisation request M/587 was adopted on 14 September 2022, about fifteen months after the deadline in Article 15(2). EN 301 549 V4.1.0 reached final draft for vote on 24 June 2026 and is not yet published. Claims of an October 2026 Official Journal citation circulate widely and are not supported by any primary source we could find.

If there is no presumption, how do I prove conformity?

Against Annex I, requirement by requirement, with dated evidence and a stated method. Record what was tested, when, by whom, and how, and keep it. For services, Article 13(2) requires information describing how the applicable Annex I requirements are met, and Annex V point 3 separately requires evidence that the delivery process and its monitoring ensure compliance.

Does this mean accessibility audits are worthless?

The opposite. Because there is no shortcut through a certificate, the audit and the evidence trail behind it are the whole case. What changes is how you describe them: as evidence that Annex I requirements are met, not as conformity to a standard that carries no legal weight for this Directive.

Official legal text

• Directive (EU) 2019/882, OJ L 151, 7.6.2019: EUR-Lex HTML · ELI · CELEX 32019L0882
• Article 15, presumption of conformity: EUR-Lex
• Commission harmonised standards index: single-market-economy.ec.europa.eu
• EN 301 549 harmonised under the Web Accessibility Directive: Commission Implementing Decision (EU) 2018/2048, amended by (EU) 2021/1339
• ETSI EN 301 549 deliverables: etsi.org

Disclaimer

Legalithm materials are operational guidance only and do not constitute legal advice. The authentic texts are those published in the Official Journal of the European Union and prevail over this representation in every case.