What changed, what has not, and why the gap between them is the cheapest window you will get
On 2 September 2026, ETSI published version 4.1.1 of EN 301 549. If that means nothing to you, it is worth ninety seconds of your attention, because it is the document your European accessibility obligations are measured against.
The change itself is narrow. Version 3.2.1 pointed at WCAG 2.1 Level AA. Version 4.1.1 points at WCAG 2.2 Level AA. It also adds Annex ZB and clause A.2, which map the standard’s requirements directly onto the European Accessibility Act — the first time the two have been explicitly joined up.
Here is the part almost nobody is saying clearly.
Version 4.1.1 is not yet the legal reference. Until the European Commission cites it in the Official Journal, conformity is still demonstrated against version 3.2.1, and that means WCAG 2.1 AA. The citation is expected in December.
So for the next few months you are in a gap: the technical standard has moved, the legal one has not. Most organisations will not notice the gap exists, and will discover the change when someone asks them to prove something in the new year.
Why this matters more than it sounds
WCAG 2.2 added nine success criteria to 2.1. Most are modest. Two are not, in the sense that they routinely break real commercial interfaces:
2.4.11 Focus Not Obscured. When a keyboard user tabs to a control, that control must not be hidden behind something else. In practice this means sticky headers, cookie banners and chat widgets — the three things almost every commercial site has bolted on over the past five years, usually by different teams at different times. The individual components are often fine. The combination is what fails.
2.5.8 Target Size (Minimum). Interactive targets need to be at least 24 by 24 CSS pixels, with some exceptions. Quantity steppers, close buttons on modals, pagination controls and icon-only actions are the usual offenders. Designers shrink these for visual balance, and nobody measures them afterwards.
Neither is exotic. Both are entirely fixable. But both tend to live in shared components rather than individual pages, which means the fix is a development cycle rather than a content edit — and development cycles need planning, budget and a slot in a roadmap that was set months ago.
That is the real reason December matters. Not the compliance date. The lead time.
The question that actually arrives first
Executives tend to plan for accessibility as a legal risk. In my experience it arrives as a commercial one, and it arrives earlier.
The sequence is usually this. A buyer — public sector, a university, a large enterprise with its own obligations — asks for your accessibility conformance report before they will sign. You have two weeks. Nobody in the business has tested anything against the criteria, so the honest document would be mostly gaps, and the dishonest one is worse because they can check it.
The deal does not collapse dramatically. It just goes quiet, and then it goes elsewhere.
I would rather a board heard that version of the story than the litigation version, because it is both more common and more actionable. Lawsuits are unpredictable. Procurement is a calendar you can see.
What I would actually do between now and December
Not a compliance programme. Three things.
Find out which version you are currently being measured against, and by whom. If you sell into the EU, the EAA applies through your customers, not your incorporation. A US company with European buyers is inside it. If you sell to government or large enterprise anywhere, you are also inside whatever their procurement framework demands, which is often stricter and always sooner.
Test against 2.2, not 2.1. You will be measured against 2.2 eventually and the difference is nine criteria, not a rewrite. Testing to the older version now means testing twice.
Ask where the gaps live. This is the question that separates a useful audit from a list. If your failures sit in a design system component used across four hundred pages, that is one fix. If they sit in four hundred individually authored pages, that is a different budget entirely. The number of findings tells you very little. Their distribution tells you nearly everything.
A caution about the easy answer
There is a category of product that promises to resolve this with a script tag. I would not recommend it, and I say that as someone whose business would be simpler if it worked.
Overlay widgets have appeared in US accessibility litigation rather than preventing it, and many people who use screen readers and keyboard navigation daily report that overlays interfere with the tools they already have configured. Accessibility is a property of your code. Something layered on top of your code does not change that property; it changes what an automated scan reports about it.
Which is a different thing, and the difference is exactly what a determined plaintiff or a competent procurement officer will find.
What conformance actually buys
Not immunity. Nobody can sell you that, and anyone offering it is describing something they cannot deliver.
What it buys is a defensible position: evidence of what was tested, what was found, what was fixed, and when. That is a materially better place to be than silence when someone asks. It is also, not incidentally, a product that more of your customers can actually use — which was the point before it was ever a compliance question.
Roughly one in four adults lives with a disability. If your checkout cannot be completed with a keyboard, that is not primarily a legal exposure. It is revenue you are declining, quietly, without anyone in the business noticing.
The standard moved in September. The law follows in December. The work takes longer than either.
Rana Ahson is COO and Partner at EcomBack (https://ecomback.com), a court-approved accessibility provider. He participates in the W3C Accessibility Guidelines Working Group, which authors WCAG, and is DHS Trusted Tester and NVDA Expert certified. He writes about accessibility and compliance at ranaahson.com (https://ranaahson.com).
This article is not legal advice. For your specific obligations, consult qualified counsel.
