If you sell to consumers in the EU, the answer is almost certainly yes, and the deadline passed over a year ago.
This page answers the question properly: who is in scope, which standard actually binds you, what enforcement looks like, and what it takes to fix a site that was not built for it. If you want the specifics for your own site, we will check it and send you the list.
The European Accessibility Act (Directive (EU) 2019/882) covers services offered to consumers in the EU. It has applied since 28 June 2025. There is no transition period left to plan around.
The microenterprise exemption covers services, not products, and it disappears the moment you cross a threshold. There is no grace period on the way up. If you have taken public funding for accessibility, it does not apply to you at all.
One thing companies get wrong: growing out of the exemption is not a future problem to schedule. The obligation attaches when the threshold is crossed, not at the next audit.
The Act says services must be accessible. It does not spell out the technical criteria. Those come from the harmonised European standard, and knowing which version is in force is the difference between a compliant site and a nearly compliant one.
This is the European standard for ICT accessibility, and conformity with it gives you the presumption of conformity with the Act. It references WCAG 2.1 Level AA.
Not AAA, which almost nobody claims and which the Act does not ask for. Not WCAG 2.0, which is superseded. Level AA of WCAG 2.1 is the line you are measured against.
A revision of EN 301 549 that picks up WCAG 2.2 Level AA is expected to publish and then be cited in the Official Journal. It adds success criteria on focus appearance, dragging movements, target size and authentication.
WCAG 2.2 AA is a superset of 2.1 AA in practice. Fixing to 2.2 satisfies today's obligation and means the standard's next revision does not reopen work you have already paid for. Fixing to 2.1 alone means doing this twice.
Each member state names its own market surveillance authority and sets its own penalties, so the number depends on where your customers are. Two things are consistent: the authorities do not wait for a complaint, and the order to fix or withdraw the service usually costs more than the fine.
Procurement is the quieter pressure. Enterprise and public buyers increasingly ask for an accessibility conformance report before they sign, and not having one loses deals long before a regulator ever writes to you.
This is not a guess. WebAIM has run an automated WCAG evaluation across the home pages of the top one million websites every year since 2019. The February 2026 run is the most recent.
Automated detection is the floor, not the ceiling. These figures count only what a machine can prove, which is a minority of WCAG. A site with zero automated errors can still be unusable with a keyboard or a screen reader, which is why the audit below is not just a scan.
Percentages are the share of the top one million home pages carrying each failure in February 2026. If you have never had an audit, assume you have most of these.
Text that does not meet the 4.5:1 ratio against its background, or 3:1 for large text. Usually a brand palette decision nobody re-checked, and the single most common failure on the web.
Images with no alt attribute, or with a filename in it. Decorative images need an empty alt, informative ones need a description. Both cases are wrong more often than they are right.
Inputs with a placeholder instead of a label, or a label not programmatically associated with its field. On a checkout this is the failure that costs you the sale, not just the audit.
A link whose only content is an icon or an empty element, so a screen reader announces it as "link" and nothing else. Common in navigation, social icons and card layouts.
The same failure on a control that does something. Hamburger menus, close buttons and icon-only actions are the usual sources.
No lang attribute on the html element, so assistive technology guesses the pronunciation. A one-line fix that a seventh of the web still has not made.
Every one of these is a source code problem with a source code fix. None of them is fixed by a script you paste into your page.
Accessibility overlays are sold as a line of JavaScript that makes a site compliant. They do not, and buying one is now its own risk.
We fix the source. The result is code you own, that survives your next deploy, and that an auditor can verify.
The free check is a real piece of work, not a lead magnet with a scan attached. It exists because nobody can quote remediation honestly without seeing the code first.
We take your URL and evaluate a representative set of pages: home, a category or listing page, a product or detail page, and your checkout or sign-up flow. Automated evaluation with axe and WAVE, then manual keyboard and screen reader passes on the flows that matter. You get the findings, mapped to the WCAG success criterion each one breaks, whether or not you hire us.
Findings ordered by user impact, legal exposure and effort. Blocking failures in a purchase or sign-up flow come first, because those are both the worst for your users and the ones a regulator reaches for. You get a fixed price and a timeline before any remediation starts.
Our engineers work in your codebase, on your branch, to your review standards. Semantics, focus management, labels and error handling, contrast, ARIA that is correct or removed. Component-level fixes so the same bug does not come back on the next page someone builds.
Re-tested with automated tooling and by hand across NVDA, VoiceOver and TalkBack plus keyboard-only navigation. You receive a report documenting the resolved state against EN 301 549 and WCAG, which is the document procurement asks for and the one you want on file if an authority writes to you.
Accessibility regresses with every release that nobody checked. Optional ongoing work: regression testing, pre-launch review of new features, and developer training so your team stops introducing the same six failures.
Probably, for the EAA specifically, which covers services offered to consumers. Check two things before relying on it: whether any part of your offering can be bought by an individual, and whether your enterprise customers require accessibility conformance in their procurement. The second one catches more B2B companies than the first.
Only if your annual turnover or balance sheet total is also no more than EUR 2 million, and only for services. Both conditions have to hold. The headcount is measured across the whole undertaking, so a small brand inside a larger group is not a microenterprise.
If you are in scope and your service is not accessible, yes, technically. That is uncomfortable but it is not unusual and it is not a reason to wait. Enforcement authorities generally start with an order to remedy, and being able to show a dated audit and a remediation plan in progress is a materially better position than being able to show nothing.
Today, 2.1 Level AA, through EN 301 549 V3.2.1. The revision that adopts WCAG 2.2 Level AA is expected during 2026. We remediate to 2.2 AA so that revision does not reopen the work.
For a typical e-commerce site or SaaS product it is usually a few weeks of engineering, not months, once the audit is done. The variable is not the number of pages, it is the number of distinct components. Fifty pages built from twelve components is a smaller job than eight pages built from sixty.
Yes. React, Next.js, Vue, Angular and Svelte at the component level. WordPress, Drupal, Shopify, Shopware and Magento at the theme and template level. Native iOS and Android for VoiceOver, TalkBack, touch targets and dynamic type.
A URL and, if the flows we need to test are behind a login, a test account. Nothing else. You keep the findings whether or not you go further with us.
We give you everything it has to contain: the conformance status, the criteria assessed, what remains non-conforming and why, and the feedback mechanism. The statement is published by you, in your name, because it is your declaration and not ours.
Tell us where to look. You get the findings back with the WCAG criterion each one breaks, and a fixed quote if you want the fixes.
Book 30 minutes. We will tell you whether you are in scope and roughly what your site is looking at, without the form.