Accessibility audit
measured against EN 301 549 and WCAG 2.2 AA.
accessibility · eaa · eu
The European Accessibility Act
The EAA makes digital accessibility mandatory across the EU. I help businesses, including those in the Nordics and companies selling into Europe, meet EN 301 549 and WCAG, with real fixes in the code.
Substance for the web.
Who does the European Accessibility Act apply to? It applies to businesses offering consumer-facing products and services in the EU, such as online stores, banking, booking, ticketing and e-books. It has been enforceable since 28 June 2025, with a transition period until 2030 for existing services. The standard is EN 301 549, which references WCAG.
KI-Suche
Suche über Antwortmaschinen und KI-Systeme, die Inhalte nicht nur listen, sondern direkt zusammenfassen.What the EAA requires
The EAA is implemented through national laws across the EU (for example Germany's BFSG). The technical benchmark is EN 301 549, which for websites and apps points to WCAG. The harmonized version EN 301 549 V3.2.1 references WCAG 2.1 AA; V4.1.1, expected in 2026, moves to WCAG 2.2. Because WCAG 2.2 fully includes 2.1, building to WCAG 2.2 AA now is the safe target. A published accessibility statement is usually part of the obligation.
Who is covered
Mainly consumer-facing services: e-commerce, banking, booking and ticketing, telecommunications, audiovisual services and e-books. The rule of thumb: if your site does more than provide information, allowing a form, a booking, a purchase or a download, it very likely falls under the EAA. Microenterprises providing services may be exempt; products are treated differently.
The Nordics and selling into the EU
The EAA applies across the EU, including the Nordic markets, and it follows the customer. A company based outside the EU that sells to EU consumers can be covered too. One solid WCAG 2.2 AA implementation serves all of these markets.
Why overlays are not a fix
As with the ADA in the US, accessibility overlays rarely create real conformance under EN 301 549. Accessibility belongs in the code, which is also what holds up under scrutiny.
Remediation in code
durable fixes, not overlays.
Accessibility statement
in line with EU expectations.
Ongoing monitoring
accessibility stays tested after every release.
- 01
Audit
assess against EN 301 549 / WCAG 2.2 AA.
- 02
Remediate
fix in the code.
- 03
Statement
publish an accessibility statement.
- 04
Monitor
keep it tested over time.
The deadline has passed for new services. The EAA has applied to new products and services since June 2025; the transition for existing services runs to 2030. Acting early is cheaper than retrofitting under pressure. Fines vary by member state.
FAQ
Since when does the EAA apply?
It has been enforceable since 28 June 2025 for new products and services, with a transition period until 2030 for existing services.
Which standard and WCAG version applies?
EN 301 549, which references WCAG. Today that is WCAG 2.1 AA (V3.2.1); the 2026 update (V4.1.1) moves to WCAG 2.2. Building to WCAG 2.2 AA covers both.
Does the EAA apply in the Nordics?
Yes. The EAA applies across the EU, and EEA/Nordic markets follow the same standard, EN 301 549.
We are outside the EU, are we affected?
Possibly. The EAA follows the customer, so selling to EU consumers can bring you into scope.
Do overlays make us compliant?
No. Overlays rarely create real conformance. Accessibility needs to be solved in the code.
Get an accessibility audit
I will check it against EN 301 549 and tell you plainly what to fix.
Get an accessibility audit