EN 301 549 adds 42 website requirements beyond WCAG among 64 total.
“One voluntary means of conforming to the essential requirements.”
That is how Europe’s own standard, EN 301 549, describes itself — and this week at the Axe-con accessibility conference, two specialists argued that the fine print matters more than most organisations realise.
The session, Beyond WCAG: Understanding Europe’s extra accessibility requirements, was presented by Hidde de Vries, a web standards and tech ethics specialist at the Dutch Ministry of Interior, and Wilco Fiers, director of accessibility automation at Deque Systems, Axe-con reported.
Their argument: Europe’s legal accessibility standard points to the familiar Web Content Accessibility Guidelines (WCAG) for most web requirements, but it contains many others — for authoring tools, real-time communication, product documentation and more — that no WCAG check will ever catch.
Here is why that matters. Two EU directives govern digital accessibility, and EN 301 549 is the harmonised standard that carries legal weight under them — not WCAG on its own. As the analysis published by axall.digital puts it, the common belief that WCAG is Europe’s legal standard is a misconception worth correcting.
The presumption that decides everything
The standard is not strictly mandatory, and specialists are right to say so. Any organisation could, in principle, take a different technical approach and argue independently that it meets the requirements of the Web Accessibility Directive or the European Accessibility Act.
But there is a catch, and it is decisive in practice. Once a version of EN 301 549 is cited in the Official Journal of the EU, meeting it creates a legal presumption of conformity, axall.digital reported. A monitoring authority presumes you comply; the burden of proof shifts, and any dispute narrows down to whether you met the standard’s clauses — not whether your whole approach counts.

Choose any other route, and that presumption does not exist. You would have to demonstrate, case by case, that your alternative meets the same essential requirements, with no institutional benefit of the doubt.
Forty-two requirements WCAG never tests
The gap is not a legal technicality alone. It shows up in the technical clauses themselves. The International Association of Accessibility Professionals’ Nordic Chapter compiled a list of EN 301 549 requirements that go beyond WCAG 2.1, axall.digital reported, and the count is striking.
Of 64 such requirements, 42 apply to websites and 22 to mobile apps only. That means 42 legally relevant requirements for websites have no WCAG equivalent at all — no success criterion, no “how to meet” guidance. An audit built only on WCAG can look thorough and still leave them untested and unmet, per the axall.digital analysis.
These are not obscure clauses. They cover real, user-facing areas: real-time text and interoperability between communication services; video playback, synchronisation and user controls, not just the presence of captions; accessible use of biometric verification such as fingerprint and facial recognition — a category WCAG does not address at all; a dedicated requirement that user accessibility settings be respected; authoring tools that support accessible output; and documentation and support that make accessibility features discoverable.
The testing guidance gap
Then there is the problem the Axe-con session was designed to tackle. Most of those extra requirements lack comprehensive testing guidance, de Vries and Fiers said in the session description — which is why they are working on the Understanding EN 301 549 project to fix it. Without shared test methods, even a well-intentioned auditor cannot easily verify conformance with the non-WCAG clauses.
And the list is about to grow. A new version of EN 301 549 is moving through standardisation now, axall.digital reported, adding further requirements on top of a shift from WCAG 2.1 to WCAG 2.2.
Why a Brussels standard reaches beyond Europe
For international readers, the reach of this standard is wider than the EU’s borders. The European Accessibility Act applies to products and services sold into the EU market, so any global company shipping software, banking apps, e-commerce platforms or self-service terminals to European customers now faces these clauses.
A vendor in California or Singapore whose compliance programme checks only WCAG can pass every audit it runs internally and still fall short of what an EU monitoring authority presumes.
The economics follow the law. Because meeting EN 301 549 — cited in the Official Journal of the EU — is the only route with a legal presumption behind it, procurement teams across the bloc are writing it into tenders. Suppliers who cannot evidence the non-WCAG clauses lose contracts to those who can.
The axall.digital analysis frames the relationship precisely: this is not “EN 301 549 versus WCAG,” and the standard is not mandatory either — it is simply the only route with the presumption attached, and WCAG is one part of what it covers.
What organisations should do next
The practical step the sources converge on is straightforward: test against EN 301 549 as a whole, rather than treating WCAG as a stand-in for it. An accessibility statement or vendor requirement built only on WCAG covers the WCAG-derived portion of the standard and leaves the rest untested.
The Axe-con 2027 call for presenters has now closed, so the next round of sessions — and the next iteration of the Understanding EN 301 549 project’s guidance — will define how the standard’s newer requirements get tested in practice.
Nobody is required to use EN 301 549, as axall.digital concludes. But choosing not to means giving up the only legal presumption of conformity Europe offers — and for the 42 website requirements with no WCAG equivalent, it means flying without instruments.