Short answer: The European Accessibility Act applies to non-EU businesses too: if you sell covered services, such as e-commerce, to consumers in the EU, the rules have applied since 28 June 2025. For a website or app, the practical design target is WCAG 2.2 Level AA, which the new EN 301 549 standard adopts. Confirm your exact scope and any exemption with a qualified adviser.
Key takeaways
- Where you are based does not decide it: the Directive covers anyone offering a covered service to consumers in the EU.
- Online stores, consumer banking, e-books and passenger transport booking are among the covered services. Services sold only to businesses are generally outside its consumer scope.
- EN 301 549 V4.1.1, published in September 2026, aligns its web, document and software clauses with WCAG 2.2. Meeting WCAG 2.2 AA is the clearest design benchmark.
- The law also asks for paperwork: a public description of how your service meets the requirements, kept for as long as the service runs.
Does the European Accessibility Act apply to non-EU businesses?
In many cases, yes. Directive (EU) 2019/882 applies to listed services "provided to consumers after 28 June 2025", and it defines a service provider as a person who provides a service on the Union market or makes offers to consumers in the Union, according to the official text on EUR-Lex (2019). A US, UK, Gulf or Asian company that runs an online store taking orders from EU shoppers fits that description on its face.
For websites and apps, the key covered services are e-commerce, consumer banking, e-books and passenger transport booking. The European Commission lists these alongside computers, smartphones, self-service terminals and telephony on its European Accessibility Act page (2026).
Who is likely to be out of scope?
- Pure B2B services. The Directive's "consumer" is a natural person acting outside their trade or profession, so a portal used only by business customers may sit outside it.
- Microenterprises providing services. Article 4(5) exempts service providers with fewer than 10 staff and an annual turnover or balance sheet not above EUR 2 million, per the Directive text on EUR-Lex (2019). The exemption is for services, not products.
- Older contracts. Service contracts agreed before 28 June 2025 may continue unaltered until they expire, but for no longer than five years from that date.
Each of these turns on facts a lawyer should review, such as your group structure and whether a site serving both consumers and trade buyers counts as consumer-facing. Each member state writes the Directive into its own law and sets its own penalties.
What does the law ask a website or app to do?
The Directive does not name WCAG. Its Annex I asks that services be perceivable, operable, understandable and robust, and for e-commerce it adds three concrete points: give the accessibility information that the responsible operator supplies about the products you sell, make identification, security and payment functions accessible, and do the same for identification methods, electronic signatures and payment services.
There is also a documentation duty. Under Article 13 and Annex V, a service provider has to publish, in its general terms and conditions or an equivalent document, a description of the service and an assessment of how it meets the requirements, and keep that information available for as long as the service operates.
A business that believes full compliance would be a disproportionate burden or a fundamental change to its service must assess and document that, renew the assessment at least every five years, and inform the relevant market surveillance authorities. Penalties are set nationally and must be "effective, proportionate and dissuasive", in the Directive's words. The burden route needs documented evidence, so it is not a shortcut.
How do WCAG 2.2 and EN 301 549 fit together?
EN 301 549 is the European standard for accessible ICT. Version 4.1.1, dated September 2026, was prepared under the Commission's standardization request to support the Act, and its foreword says clauses 9, 10 and 11 were updated to align with WCAG 2.2, according to the ETSI, CEN and CENELEC standard EN 301 549 V4.1.1 (2026). It states that WCAG 2.2 Level AA conformance is equivalent to meeting its web clauses 9.1 to 9.4 plus the conformance requirements in 9.6.
One legal detail: the standard gives a presumption of conformity with the Act only once it is cited in the Official Journal of the EU. As of November 2026, check whether that citation exists before relying on it. The design target is the same either way.
The standard also notes that WCAG 2.2 is identical to ISO/IEC 40500:2025, and that native apps, including web views inside them, are assessed under the software clauses (clause 11), so app teams need their own test plan.
What is new in WCAG 2.2 for designers?
WCAG 2.2 became a W3C Recommendation on 5 October 2023 and added nine success criteria, six of them at Levels A and AA, according to the W3C overview of what is new in WCAG 2.2 (2023). It also removed 4.1.1 Parsing as obsolete. The six that a Level AA target includes:
CriterionLevelWhat it means in a design file 2.4.11 Focus Not Obscured (Minimum)AASticky headers, chat widgets and cookie banners must not completely cover the element that has keyboard focus. 2.5.7 Dragging MovementsAASliders, sortable lists and map pins need a click or tap alternative to dragging. 2.5.8 Target Size (Minimum)AAPointer targets of at least 24 by 24 CSS pixels, or enough spacing around smaller ones. 3.2.6 Consistent HelpAContact links, chat or help pages appear in the same relative order on every page. 3.3.7 Redundant EntryADo not make users retype what they already entered in the same flow, such as a shipping address. 3.3.8 Accessible Authentication (Minimum)AANo memory or puzzle test to log in unless there is an alternative; allow paste and password managers. The older criteria still apply, and they cause most problems. WCAG 2.2 keeps the contrast minimum of 4.5:1 for normal text and 3:1 for large text, and still requires content to reflow at a width equal to 320 CSS pixels and text to resize to 200 percent without loss of function, per the W3C WCAG 2.2 Recommendation (2024).
A practical European Accessibility Act checklist for design teams
The WebAIM Million study of one million home pages found detectable WCAG 2 failures on 95.9% of them in February 2026, led by low-contrast text (83.9%), missing image alt text (53.1%) and missing form labels (51%), according to WebAIM: The WebAIM Million (2026). Automated tools catch only part of the problem.
- Color and contrast. Check every text and background pair, including placeholders and text over images.
- Focus states. Give every interactive component a visible focus style that sticky elements never hide.
- Targets. Size icon buttons, close icons and filter chips to 24 by 24 CSS pixels, or space them out.
- Forms. Visible labels, error messages next to the field, and autofill for repeated details.
- Login. Allow paste and password managers; offer passkeys or email links instead of puzzle-style challenges.
- Checkout and payment. Test the whole path with a keyboard and a screen reader, third-party payment widgets included.
- Media and images. Alt text written for meaning, captions for video, and no information carried by color alone.
- Layout. Content that reflows on narrow screens and at 200 percent zoom without horizontal scrolling, as described in the W3C WCAG 2.2 Recommendation (2024).
- Language and structure. A correct page language, one H1, logical headings and real buttons rather than clickable divs.
- Accessibility statement. Publish how the service meets the requirements and how to report problems.
Our website UI/UX design service works these checks into the design system, so new pages inherit them. For stores, pair this list with the guide to checkout problems for international customers, since an inaccessible checkout loses sales and creates legal risk at the same step.
Should you fix, redesign or rebuild?
Your situationReasonable next step Modern site with a design system and a few audit issuesFix in the components, re-test key journeys, publish the statement Older theme with hard-coded colors and custom widgetsPlan a phased website redesign that starts with checkout, login and forms Store on a hosted platformCheck the platform's own accessibility documentation, then audit your theme, apps and content Native mobile app plus websiteTest both separately; the app falls under the software clauses of EN 301 549 Ask any vendor which WCAG version and level they test against, whether testing covers screen readers and keyboard-only use, and who fixes issues in third-party widgets. The e-commerce development team at Alive Inc. can include such an audit in a project.
What should you confirm with a qualified adviser?
This article is not legal advice. Ask an EU-qualified lawyer or compliance adviser to confirm:
- whether each of your sites and apps counts as a covered consumer service, and in which member states;
- whether the microenterprise exemption or a transitional rule applies to you;
- what your accessibility information must contain and where it should be published;
- how national penalties and complaint routes work in your main EU markets.
Frequently Asked Questions
Does the European Accessibility Act apply to US or UK companies?
It can. The Directive covers service providers that offer covered services, such as e-commerce, to consumers in the EU, wherever the company is registered. Selling only to businesses, or qualifying as a microenterprise providing services, may take a company out of scope. A qualified adviser should confirm your position for each market.
Is WCAG 2.2 legally required under the European Accessibility Act?
The Directive itself sets functional requirements and does not name WCAG. The European standard EN 301 549 V4.1.1 aligns with WCAG 2.2 and gives a presumption of conformity once it is cited in the Official Journal. In practice, WCAG 2.2 Level AA is the benchmark auditors and authorities are likely to use.
Does an accessibility overlay make a website compliant?
An overlay script does not fix inaccessible code, missing labels, poor contrast or broken checkout flows. Compliance depends on how the site itself is built and tested. Treat any tool that promises instant compliance with caution, and rely on audits that include assistive-technology testing.
What is the first thing a non-EU store should do?
Run an audit of the main buying journey against WCAG 2.2 Level AA: home page, search, product page, cart, checkout, login and account. Fix issues in shared components first, then draft the accessibility information the Directive asks for, and have an adviser review scope and wording.
Sources
- EUR-Lex: Directive (EU) 2019/882 on the accessibility requirements for products and services (2019)
- European Commission: European Accessibility Act (2026)
- ETSI, CEN and CENELEC: EN 301 549 V4.1.1 Accessibility requirements for ICT products and services (2026)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (2024)
- W3C WAI: What's New in WCAG 2.2 (2023)
- WebAIM: The WebAIM Million (2026)

