You sell to consumers in the EU
An online store, a banking app or a booking flow used by EU consumers is likely in scope. An audit records your product's results against EN 301 549, criterion by criterion, and shows what to fix first.
European Accessibility Act compliance
Know what the European Accessibility Act (EAA) asks of your product
The Act has applied since 28 June 2025 to a defined set of consumer products and services sold in the EU. An audit against EN 301 549 shows where your product stands, what to fix first, and forms the basis for the accessibility statement the Act asks service providers to publish.
Start here
Who the Act covers
The European Accessibility Act covers two groups: physical devices, and listed services provided to consumers in the EU, wherever the company behind them is based. Websites, apps and other software fall under the Act through the services they deliver.
Software used only by businesses and their employees usually sits outside the Act. A consumer-facing part, such as a public self-serve checkout, can bring that part into scope, and EU public tenders often require the same standard, EN 301 549, for tools their own staff use.
Devices
Consumer computers and their operating systems; payment terminals, ATMs, ticketing and check-in machines; smartphones, tablets and other consumer devices used for communication or media; e-readers.
Services, including their websites and apps
E-commerce; consumer banking; electronic communications; access to audiovisual media; passenger transport by air, bus, rail and water, including tickets and travel information; e-books and their reading software.
When it applies
When teams look at the EAA
You need an accessibility statement
In-scope services must explain how they meet the accessibility requirements, in their terms and conditions or an equivalent document. The audit gives that statement its facts: the standard applied, current conformance and known limitations.
A tender or an EU buyer asks for VPAT
Public bodies and large enterprise buyers often ask for EN 301 549 conformance, even where the Act doesn't apply. The audit produces that evidence on the VPAT EU edition.
Requirements
What the Act asks for
The EAA sets accessibility requirements; EN 301 549 is the European standard used to meet them. What you need to show depends on whether you provide a service or make a product.
I.
An accessible product or service
Meet the accessibility requirements in Annex I of the Act. For digital interfaces, EN 301 549 is the recognized way to show it: it builds on WCAG and adds requirements for software, documentation and support services.
II.
An accessibility statement, for services
Describe the service, how it works and how it meets the requirements, in the terms and conditions or an equivalent document, in accessible formats. Keep it available for as long as the service runs.
III.
Technical documentation, for products
Manufacturers keep technical documentation, sign an EU declaration of conformity and apply the CE marking, then keep the documentation for five years.
IV.
Conformity that lasts
Service providers keep procedures that maintain conformity through new releases and inform the national authority if the service stops conforming. An exemption for disproportionate burden needs a documented assessment.
From audit to evidence
How the audit supports EAA conformity
-
Audit
Automated testing and expert review against EN 301 549 and WCAG 2.2 AA, with every finding mapped to its clause and rated by its effect on users.
-
Remediation
A roadmap that puts quick wins and critical findings first. Once the findings are in, we can scope the design updates with you.
-
Documentation
An accessibility statement drafted from the results, and a VPAT EU edition for buyers who ask for one, both ready for your legal team to review. After the fixes go live, a re-test brings them up to date.
Related case
Three surfaces, three standards, one audit
Smarttid
Workforce time-registration platform
SmartTID handles clock-ins, collective agreements and payroll sync. We audited its portal, web terminal and mobile app with automated scans plus keyboard and VoiceOver testing, rated each issue and planned the fixes.
210
Checks across WCAG 2.1, WCAG 2.2 and EN 301 549, Levels A and AA
3
Surfaces audited: web portal, web terminal, mobile app
FAQ
Common questions
Does the EAA apply to companies outside the EU?
The audit tests against WCAG 2.2 Levels A and AA plus the EN 301 549 requirements outside WCAG, and reports results against WCAG 2.1 as well. The results hold for the edition in use today and for the new edition, which adopts WCAG 2.2.
Does the EAA apply to B2B software?
The audit tests against WCAG 2.2 Levels A and AA plus the EN 301 549 requirements outside WCAG, and reports results against WCAG 2.1 as well. The results hold for the edition in use today and for the new edition, which adopts WCAG 2.2.
What is the EAA deadline?
The audit tests against WCAG 2.2 Levels A and AA plus the EN 301 549 requirements outside WCAG, and reports results against WCAG 2.1 as well. The results hold for the edition in use today and for the new edition, which adopts WCAG 2.2.
Which edition of EN 301 549 should we test against?
The audit tests against WCAG 2.2 Levels A and AA plus the EN 301 549 requirements outside WCAG, and reports results against WCAG 2.1 as well. The results hold for the edition in use today and for the new edition, which adopts WCAG 2.2.