If you sell to customers in the European Union, the European Accessibility Act almost certainly applies to you — regardless of where your business is registered.
This page explains what the EAA is, who it covers, what it requires of an ecommerce store, who is genuinely exempt, and what compliance involves in practice for a Shopify store.
- What the European Accessibility Act is
- Who must comply
- Exemptions — and why most stores don't qualify
- What the EAA requires of an ecommerce site
- The technical standard: EN 301 549 and WCAG
- EAA vs ADA — how they differ
- EAA compliance for Shopify stores
- Enforcement and penalties
- The accessibility statement requirement
- How AccessoraX brings you into compliance
- Frequently asked questions
What the European Accessibility Act Is
The European Accessibility Act — Directive (EU) 2019/882 — is EU legislation requiring a defined set of products and services to be accessible to people with disabilities.
It is a directive, not a regulation. That distinction matters: each EU member state transposed it into its own national law, so the enforcement body, the complaints process and the penalties differ by country even though the underlying obligations are common.
| Date | What happened |
|---|---|
| April 2019 | Directive (EU) 2019/882 adopted |
| June 2022 | Deadline for member states to transpose it into national law |
| 28 June 2025 | Requirements began to apply. New services must comply. |
| 28 June 2030 | End of the transitional period for services already provided before June 2025 |
On the 2030 date. You may see it described as a grace period for existing websites. Read it carefully before relying on it — it covers services already being provided before June 2025 and continuing largely unchanged. An actively developed ecommerce store that adds products, installs apps and updates its theme is not a frozen legacy service. Most merchants should treat the obligation as current, not as something that begins in 2030.
Who Must Comply
The EAA covers ecommerce explicitly. Under the directive, "e-commerce services" means services provided at a distance, through websites and mobile apps, by electronic means, at the individual request of a consumer, with a view to concluding a consumer contract.
That is an ordinary online store.
The point most merchants miss
The EAA applies based on where your customers are, not where you are. A store registered in Texas, Manchester or Sydney that ships to Germany, France or Ireland falls within scope. There is no requirement to have an EU entity, an EU warehouse or an EU bank account.
If your checkout accepts an EU delivery address, assume you are in scope until you have established otherwise.
Alongside ecommerce, the EAA also covers banking, e-books, transport ticketing, telecoms, and audiovisual media services. This page deals with the ecommerce obligations.
Exemptions — and Why Most Stores Don't Qualify
The microenterprise exemption
Microenterprises providing services are exempt from the EAA's service accessibility requirements. A microenterprise is defined as a business that:
- employs fewer than 10 people, and
- has an annual turnover or balance sheet total not exceeding €2 million
Four things people get wrong about this exemption
- Both conditions must be met. Eight employees and €5m turnover is not a microenterprise.
- It covers services, not products. A microenterprise that manufactures or distributes covered products still has obligations.
- There is no grace period on the way out. Cross either threshold and the obligation attaches immediately.
- It is not a reason to ignore accessibility. Exempt from the EAA is not exempt from the ADA, and it does nothing about the customers you are turning away.
Disproportionate burden
Article 14 allows a business to argue that a specific requirement would impose a disproportionate burden. This is narrower than it sounds. It is assessed requirement by requirement, it must be documented with a reasoned assessment, and it must be re-evaluated periodically. It is not a checkbox and it is not a general exemption.
Archived content
Content genuinely frozen before the deadline and untouched since can fall outside scope. If a section is still being edited or added to, it does not qualify.
What the EAA Requires of an Ecommerce Site
The directive is outcome-based rather than a checklist, but for a store the practical obligations are clear. Our Shopify WCAG checklist covers all 50 criteria in detail.
Perceivable
- Product images carry meaningful alt text
- Text meets contrast requirements
- Video content is captioned
- Information is not conveyed by colour alone
Operable
- Everything works by keyboard alone
- No keyboard traps in menus, modals or the cart
- Focus is always visible
- Sufficient time to complete checkout
Understandable
- Form fields are properly labelled
- Errors are identified and explained in text
- Navigation is consistent across the site
- Page language is declared
Robust
- Semantic HTML that assistive technology can parse
- ARIA used correctly where used at all
- Compatible with current screen readers
- Status changes announced programmatically
Two obligations go beyond the technical standard and are frequently missed:
- Information about accessibility must be provided to consumers — in practice, an accessibility statement.
- Identification of the products and services being offered must itself be accessible, meaning the accessibility of the buying journey, not just the pages.
The Technical Standard: EN 301 549 and WCAG
The EAA does not name WCAG in its text. It sets functional requirements and points to harmonised European standards for the technical detail.
The relevant standard is EN 301 549, the European standard for ICT accessibility. For web content, EN 301 549 incorporates WCAG 2.1 Level AA.
What this means practically. If your store meets WCAG 2.1 Level AA, you have met the substantive technical requirement that sits behind the EAA. The work is the same work — which is why a single remediation project can address the EAA and the ADA together.
Meeting WCAG 2.2 AA additionally puts you ahead of where the standard is heading. See our guide to WCAG 2.2 for Shopify for what the newer criteria add.
EAA vs ADA — How They Differ
| European Accessibility Act | ADA (United States) | |
|---|---|---|
| Type | Statute that names digital services directly | Civil rights law applied to websites through case law |
| Standard | EN 301 549, incorporating WCAG 2.1 AA | No named standard; courts reference WCAG 2.1 AA |
| Enforcement | Market surveillance authorities in each member state | Private lawsuits and DOJ action |
| Trigger | Proactive obligation — you must comply | Typically reactive — a complaint or lawsuit |
| Consequence | Penalties set by national law; orders to remedy | Settlements, legal costs, consent decrees |
| Small business relief | Microenterprise exemption | No equivalent size exemption |
If the US market is your bigger exposure, see our Shopify ADA compliance service. The important practical difference: the ADA usually bites when someone complains. The EAA creates an obligation that exists whether or not anyone has complained. If you sell into both markets, the EAA is the stricter planning assumption — and meeting it covers you for both.
EAA Compliance for Shopify Stores
Shopify's platform gives you an accessible foundation. Its native checkout is built to a reasonable standard. But the platform is not the whole store, and merchants are responsible for what sits on top of it.
In our audits, EAA-relevant failures on Shopify stores cluster in five places:
1. Theme customisations
Custom CSS that removes focus indicators, colour schemes that fail contrast, and heading structures broken during design work.
2. Third-party apps
Popups, review widgets, chat and filter apps introduce a large share of violations. You remain responsible for them.
3. The cart drawer
The most common single failure. Focus does not move into the drawer, Escape does not close it, and the customer cannot reach checkout.
4. Product content
Missing alt text, colour swatches with no text label, and variant selectors that cannot be operated by keyboard.
5. No accessibility statement
The EAA expects consumers to be given information about accessibility. Most stores have nothing.
Where to start
A manual audit of your live store against WCAG 2.1 AA, prioritised by what blocks a purchase. See our methodology.
Related reading: which Shopify apps break accessibility and fixing checkout keyboard navigation.
Enforcement and Penalties
Because the EAA is a directive, enforcement sits with national market surveillance authorities and the penalties are set by each member state's implementing law. The directive requires those penalties to be "effective, proportionate and dissuasive."
Be sceptical of headline fine figures. You will see specific euro amounts quoted widely online. Maximum penalties genuinely differ by country, and the realistic first step in most member states is a complaint, an investigation and an order to remedy rather than an immediate maximum fine. Any vendor quoting you one number for "the EAA fine" is oversimplifying. For the position in a specific country, take local legal advice.
The more immediate commercial risks for most merchants are practical: complaints from customers, exclusion from B2B and public sector contracts that require conformance, and the revenue lost from customers who cannot complete a purchase.
The Accessibility Statement Requirement
The EAA expects service providers to give consumers information about how the service meets accessibility requirements. For a store, that is an accessibility statement.
A useful one sets out:
- The standard you conform to and the conformance level
- Any known limitations, and what you are doing about them
- A contact route for accessibility problems, with a response commitment
- The date of your last assessment
Do not publish a statement claiming full conformance you have not verified. A statement is a public declaration. Claiming WCAG 2.1 AA conformance on a store that fails it puts your claim in writing for a complainant to use. Publish what is true, including the gaps and the plan.
How AccessoraX Brings You Into Compliance
We are not a law firm and we do not provide legal advice on your EAA position. What we do is the technical work that compliance rests on, documented so you can evidence it.
- Audit — your store tested by hand against WCAG 2.1 AA, the standard behind EN 301 549, using real assistive technology. Not a scanner report.
- Prioritised findings — every issue mapped to a success criterion and rated by how much it blocks a purchase.
- Native remediation — fixes made in your theme's code, not layered over with a widget. Overlays do not satisfy EN 301 549.
- Verification — retested with the same methods that found the issues, with a record of what changed and when.
- Accessibility statement — drafted to reflect your actual conformance, including any remaining limitations.
- Ongoing checks — because new apps, products and theme updates introduce new barriers.
Because the EAA and the ADA both rest on WCAG 2.1 AA, one remediation project addresses both. If you sell into the US and the EU, you are not buying two projects.
Find out where your store stands
We'll test your store against WCAG 2.1 AA — the standard behind EN 301 549 — and send back a recorded walkthrough showing exactly where a customer is blocked. Free, and no pitch attached.
Request your free auditFrequently Asked Questions
Does the EAA apply to my US or UK store?
If you sell to consumers located in the EU, yes — the obligation follows the customer, not the company. A store based outside the EU that accepts EU orders is within scope unless an exemption applies.
We have fewer than 10 employees. Are we exempt?
Only if your annual turnover or balance sheet total also does not exceed €2 million. Both conditions must be met, and the exemption covers services rather than products. It also disappears the moment you cross either threshold.
Doesn't the 2030 date give us more time?
The transitional period to June 2030 applies to services already provided before June 2025 and continuing largely unchanged. An actively developed store is difficult to characterise that way. Treat the obligation as current.
Which standard do we actually have to meet?
EN 301 549, which for web content incorporates WCAG 2.1 Level AA. Meeting WCAG 2.1 AA is the practical target.
Will an accessibility widget make us EAA compliant?
No. Overlays modify the page in the browser; they do not fix the underlying code, and they do not produce conformance with EN 301 549. See why accessibility widgets don't work, or our widget removal service.
If we already meet the ADA, are we EAA compliant?
Technically you are most of the way there, because both rest on WCAG 2.1 AA. The EAA adds the accessibility statement obligation and applies proactively rather than on complaint.
How long does compliance work take?
For a typical Shopify store, an audit takes a few days and remediation two to four weeks depending on the number of templates, apps and customisations. Larger or heavily customised stores take longer.
Note: this page is general information about the European Accessibility Act, not legal advice. National implementations differ. For your specific obligations and exposure in a given member state, consult a qualified lawyer in that jurisdiction.