The European Accessibility Act applies to your Shopify store if you sell to consumers in the EU, and it has been enforceable since 28 June 2025. It does not matter where your business is based. If EU shoppers can buy from you, the law reaches you, because the EAA explicitly treats e-commerce as a service within its scope.1
This article explains what the EAA is, exactly who it applies to, the technical standard it points to, the narrow micro-enterprise exemption, how penalties work, and what Shopify merchants actually need to fix.
Key takeaways
- The European Accessibility Act (Directive (EU) 2019/882) became applicable on 28 June 2025 and covers e-commerce as a service.
- It reaches non-EU sellers, including US and UK Shopify stores, when they sell to consumers in the EU.
- The technical standard is EN 301 549, which incorporates WCAG 2.1 Level AA for web content.
- A micro-enterprise providing services is exempt: fewer than 10 staff and annual turnover or balance sheet at or below EUR 2 million. The exemption is narrower for products.
- Penalties are set by each member state and vary widely. Overlays and accessibility apps do not satisfy the EAA. Native theme-code fixes do.
This article is general information, not legal advice. For how the EAA applies to your specific business, consult a qualified lawyer in the relevant member state.
Why you can trust us
We have been in the Shopify space for over four years and built Fudge, an AI store builder and editor with a 5.0 rating on the Shopify App Store. Fudge fixes accessibility issues directly in native theme code rather than hiding them behind a widget, and it has deep experience with multi-locale storefronts, which matters when you sell across the EU’s many markets and languages. Our position matches the consensus among accessibility engineers, and we cite official EU sources throughout.
This post is the EU-specific companion to our broader Shopify ADA and WCAG compliance guide. If you want the full picture across US, EU, and other regimes, start there.
What is the European Accessibility Act?
The European Accessibility Act is Directive (EU) 2019/882. It is an EU directive that sets common accessibility requirements for a defined list of consumer products and services across all 27 member states.1
Because it is a directive rather than a regulation, each member state had to transpose it into its own national law. Member states were required to adopt those national rules by 2022, and the requirements became applicable on 28 June 2025.1
The goal is a single, consistent baseline so that people with disabilities can use everyday products and services. The covered services include e-commerce, consumer banking, electronic communications, transport passenger services, e-books, and access to audiovisual media services.1
Why e-commerce is explicitly in scope
The EAA defines “e-commerce services” as services provided through websites and mobile apps that let a consumer conclude a contract for a product or service. A standard Shopify storefront, where a visitor browses products and checks out, is exactly that.1
That means the obligation covers the whole shopping path: product discovery, product pages, cart, account, and checkout. If a screen-reader or keyboard-only user cannot complete a purchase, that is the precise failure the law is designed to address.
Does the EAA apply to non-EU and US Shopify stores?
Yes, in practice it can. The EAA applies to economic operators that place covered products or provide covered services to consumers in the EU market, regardless of where the business itself is established.
So a Shopify store based in the United States, the United Kingdom, Canada, or anywhere else falls within scope when it sells to EU consumers. The trigger is the market you sell into, not your registered address.
If your store ships to the EU, accepts EU currencies, or markets to EU shoppers, you should assume the EAA is relevant to you.
The technical standard: EN 301 549 and WCAG 2.1 AA
The EAA sets functional accessibility requirements but does not write out every technical rule itself. Instead, conformance is demonstrated against the harmonized European standard EN 301 549.
EN 301 549 incorporates WCAG 2.1 Level AA for web content.1 So for a Shopify storefront, meeting WCAG 2.1 AA is the core of meeting the EAA’s web requirements.
WCAG is organized around four principles, known by the acronym POUR:
- Perceivable. Text alternatives for images, captions for video, sufficient color contrast.
- Operable. Full keyboard access, visible focus, no keyboard traps.
- Understandable. Clear labels, consistent navigation, helpful form error messages.
- Robust. Valid, semantic HTML that assistive technology can interpret.
A practical note: the broader ADA settlement standard in the US is now WCAG 2.2 AA. WCAG 2.2 is a superset of 2.1, so building to 2.2 AA satisfies the EAA’s 2.1 AA requirement and the stricter US benchmark at the same time. We recommend treating 2.2 AA as your single target.
Who is in scope and who is exempt?
The EAA covers most consumer-facing online sellers, but there is a specific exemption for very small service providers.
A micro-enterprise that provides services within the EAA’s scope is exempt from the service requirements. A micro-enterprise is defined as a business with fewer than 10 persons employed and an annual turnover or annual balance sheet total at or below EUR 2 million.1
The nuance worth understanding: this services exemption is what most Shopify merchants would rely on, since running an online store is providing an e-commerce service. The exemption is narrower for products. A micro-enterprise that manufactures, imports, or distributes physical products covered by the EAA is not fully exempt from the product requirements, though it gets lighter documentation duties.
| Who | EAA status |
|---|---|
| Shopify store selling to EU consumers, 10+ staff or over EUR 2M | In scope. Must meet the service requirements. |
| Non-EU store (US, UK, etc.) selling to EU consumers | In scope. Location does not exempt you. |
| Micro-enterprise providing an e-commerce service (under 10 staff and at or below EUR 2M) | Exempt from the service requirements. |
| Micro-enterprise that manufactures or imports covered products | Lighter product duties, but not fully exempt for products. |
Both micro-enterprise conditions must be true. A business with 8 staff but EUR 5 million in turnover does not qualify. Neither does one with 12 staff and EUR 1 million in turnover.
How are the EAA’s penalties enforced?
There is no single EU-wide fine. Enforcement and penalties are set by each member state in its national transposition of the directive.
The directive requires those national penalties to be effective, proportionate, and dissuasive, and it requires that penalties be accompanied by effective remedial action in cases of non-compliance.1 Beyond that principle, the specific amounts, authorities, and procedures differ from country to country.
In practice this means the financial exposure for the same failure can look very different depending on where the complaint is raised. Each member state also designates its own market-surveillance and enforcement authorities. Some national frameworks allow ongoing or daily penalties for continued non-compliance, and authorities can order a non-compliant service to be brought into conformity.
Because the rules and amounts vary by country, the safe approach for a store selling across the EU is to meet the technical standard everywhere rather than betting on a lenient jurisdiction.
What Shopify merchants must fix
The EAA is about your storefront’s actual behavior, so the work is in your theme and content, not in a platform setting. The most common, machine-detectable failures are the same ones that drive accessibility complaints everywhere:
- Low-contrast text. Brand colors used for body or button text that fall below the 4.5:1 ratio for normal text.
- Missing alt text. Product and lifestyle images uploaded without a text alternative.
- Missing form labels. Search, newsletter, and custom inputs with no programmatic label.
- Empty links and buttons. Icon-only controls (cart, menu, social, close) with no discernible text.
- Missing page language. No
langattribute, which matters more on multi-locale EU stores. - Keyboard and focus problems. Controls you cannot reach or operate with the keyboard, or focus states you cannot see.
Each of these is a change to your Liquid, CSS, or JavaScript. Fixing them is theme-code work, not a toggle.
The multi-locale angle
Selling across the EU usually means selling in several languages. Every locale of your store has to meet the standard, and the correct lang attribute and translated alt text and labels have to be present per language. This is where storefronts often slip: an accessible English page does not guarantee an accessible German or French one. Getting accessibility right consistently across locales is part of what we built Fudge to handle.
Why overlays and accessibility apps do not satisfy the EAA
When merchants first read about the EAA, the tempting fix is an overlay: a single script from a vendor that promises automatic compliance. It does not satisfy the law, for the same reasons it does not satisfy the ADA.
An overlay is JavaScript layered on top of your existing HTML. It cannot rewrite the underlying problems, because automated tooling only detects and addresses a subset of WCAG criteria, roughly 30 to 40% by independent testing. The EAA requires the service itself to be accessible, not masked.
More than 1,000 accessibility professionals have signed the Overlay Fact Sheet stating that overlays are unreliable and cannot achieve compliance.2 In 2025, the US FTC finalized a USD 1,000,000 order against the overlay vendor accessiBe for deceptively claiming its widget could make any website WCAG compliant.3 The promise does not hold up technically or legally.
We cover this in depth in our guide on why accessibility overlays fail. The short version: an overlay is a recurring cost that hides the problem instead of removing it.
How to fix it the right way
Every durable EAA fix is a change to your theme code, the part overlays skip and the part that actually meets the standard.
The model we recommend, and the one we built Fudge around, is three steps:
- Surface what needs fixing. Scan the live storefront, across every locale, to find the real issues: low-contrast text, missing labels, missing alt text, keyboard gaps.
- Fix it in native code. Repair the issues directly in your Liquid, CSS, and JavaScript so the page itself is accessible. This is what a developer would do, and what regulators recognize. It also pairs naturally with related work like adding structured data and general store editing.
- Monitor for regressions. A future theme update or content edit can quietly reintroduce a failure, so keep checking.
Because the output is real code rather than an injected layer, it holds up the way a developer’s fix would, and there is no extra script slowing the page down.
Publish an accessibility statement
The EAA expects covered services to provide accessibility information. Publish a clear accessibility statement that names your target standard (WCAG 2.2 AA, which covers the EAA’s 2.1 AA requirement), explains how users can report problems, and gives a contact route.
Keep it honest and specific rather than boilerplate. A vague or copied statement signals little, while an accurate one signals good faith if a complaint ever arrives.
FAQ
It can. The EAA applies to businesses that sell covered products or services to consumers in the EU, regardless of where the business is based. A US Shopify store that sells to EU consumers falls within scope. The trigger is the market you sell into, not your registered address.
The EAA (Directive (EU) 2019/882) became applicable on 28 June 2025. Member states had to transpose it into national law by 2022, and the accessibility requirements became enforceable on that 2025 date across all 27 member states.
Conformance is shown against the harmonized European standard EN 301 549, which incorporates WCAG 2.1 Level AA for web content. Building to WCAG 2.2 AA satisfies the EAA's 2.1 AA requirement and the stricter US ADA benchmark at the same time.
Only if it is a micro-enterprise providing a service: fewer than 10 staff and annual turnover or balance sheet at or below EUR 2 million. Both conditions must be true. The services exemption is narrower for businesses that manufacture or import covered physical products.
There is no single EU-wide fine. Each member state sets its own penalties, which must be effective, proportionate, and dissuasive. Amounts, authorities, and procedures vary by country, so the same failure can carry very different exposure depending on where a complaint is raised.
No. Overlays are JavaScript added on top of your HTML and address only about 30 to 40% of WCAG criteria, so they cannot make the service itself accessible. Over 1,000 accessibility experts reject them, and the FTC fined accessiBe one million dollars in 2025 for claiming otherwise. Fixing the theme code is what meets the standard.
Focus on the common, fixable failures: low-contrast text, missing image alt text, missing form labels, empty icon links and buttons, a missing page language attribute, and keyboard or focus problems. Each is a change to your Liquid, CSS, or JavaScript, and each locale of a multi-language store must meet the standard.
Footnotes
-
Directive (EU) 2019/882 of the European Parliament and of the Council of 17 April 2019 on the accessibility requirements for products and services (the European Accessibility Act). Applicable from 28 June 2025; e-commerce services defined in Article 3; micro-enterprise definition and services exemption in Articles 2-4 and Recital 70; penalties to be effective, proportionate and dissuasive under Article 30. Full text at eur-lex.europa.eu/eli/dir/2019/882/oj. EN 301 549 incorporates WCAG 2.1 AA for web content. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8
-
Overlay Fact Sheet, signed by more than 1,000 accessibility professionals, overlayfactsheet.com. ↩
-
FTC order requiring accessiBe to pay USD 1,000,000, proposed January 2025 and finalized April 2025, ftc.gov. ↩
