The European Accessibility Act for online stores selling into the EU

For most of the last decade, accessibility on a European storefront was a reputational question. A retailer could choose to invest in it, publicize it, or quietly ignore it. The European Accessibility Act changed the category: for online stores that sell to consumers in the EU, accessibility is now a condition of offering the service at all, in the same family of obligations as product safety or consumer information rules.

The change caught many cross-border sellers off guard because the directive is usually discussed as a European compliance topic, and plenty of American, British and Canadian merchants assumed it was aimed at European companies. It is not. This article explains what the Act covers in e-commerce, who is in scope, how the micro-enterprise exemption really works, what the technical requirements look like in practice, and how enforcement is organised. It is written for teams that ship into the EU from outside it, and it complements our broader guide to accessible retail and the rules that now apply on both sides of the Atlantic.

One framing note before the detail. This is an information piece, not legal advice: the directive is implemented through 27 national laws, and the details that decide a specific case (who the regulator is, what the penalty is, which exemptions are recognised) live in those national texts.

What the European Accessibility Act covers in e-commerce

The European Accessibility Act is an EU directive adopted in April 2019. Member states had until June 28, 2022 to transpose it into national law, and the obligations apply from June 28, 2025, according to the European Commission’s EAA page. It harmonises accessibility requirements for a defined list of products and services, so that a business meeting the common rules can sell across the single market without 27 different technical standards.

The list is deliberately specific. On the product side it includes computers and operating systems, smartphones, e-readers, payment terminals, ATMs and ticketing or check-in machines. On the service side it includes electronic communications, access to audiovisual media services, elements of passenger transport, consumer banking, e-books and, crucially for this site’s readers, e-commerce services.

The definition of an e-commerce service

The directive defines e-commerce services as services provided at a distance, through websites and mobile device-based services, by electronic means and at the individual request of a consumer, with a view to concluding a consumer contract. That wording does a lot of work. It captures a branded Shopify store, a WooCommerce site, a native shopping app and a checkout embedded in a social storefront, as long as a consumer can buy through it.

It does not, on its face, capture a purely informational brochure site with no transaction path, or a business-to-business ordering portal where the customer is not a consumer. Sellers with mixed B2B and B2C channels should treat the consumer-facing flow as in scope, because that is the flow the definition targets.

What sits inside the scope of a store

In practice, regulators and auditors look at the whole purchase path rather than the homepage alone. That includes product discovery (search, filters, category pages), product detail pages, the cart, account creation and login, identification and security steps, payment, order confirmation and the communications that follow. The Annex I requirements for e-commerce specifically mention the accessibility of identification, security and payment functionality, which is where many otherwise tidy storefronts fall down.

The directive also asks e-commerce service providers to pass along information about the accessibility of the products they sell, where the responsible manufacturer or importer makes that information available. For a general merchandise retailer, this is mostly a catalog data question, and it connects directly to the attribute work covered in our guide to product data, catalogs and the digital shelf.

Part of the store	Typically in scope under the EAA	Common failure seen in audits
Search and category pages	Yes	Filters that cannot be operated by keyboard; results updates not announced to screen readers
Product detail pages	Yes	Images without text alternatives; size and color selectors built from unlabeled custom widgets
Cart and checkout	Yes	Error messages shown only in red; session timeouts with no warning or extension
Login, identity and security	Yes, named in Annex I	Image-only CAPTCHA with no alternative; one-time codes that expire too quickly
Payment step	Yes, named in Annex I	Third-party payment iframes that trap keyboard focus
Marketing blog or brand story pages	Usually treated as part of the service if linked from the purchase path	Video without captions; low-contrast text over images
B2B wholesale portal	Generally outside the e-commerce definition	Not applicable to the EAA, though procurement buyers may still ask for evidence

Who is in scope, including sellers based outside the EU

The single most common misunderstanding among cross-border sellers is the assumption that an EU directive only binds EU companies. The EAA applies to service providers that provide services to consumers in the Union. Where the seller is incorporated is not the test; whether it offers the service to EU consumers is.

That puts a large population of US, UK, Canadian and Asian direct-to-consumer brands in scope. If a store ships to Germany, prices in euros, offers a French-language storefront or runs EU-targeted ads, it is hard to argue the service is not offered to EU consumers. For teams still mapping which markets to open, our explainer on cross-border commerce in plain language covers the commercial side of that decision, and accessibility now belongs on the same checklist as VAT, returns and duties.

Signals that a store is targeting EU consumers

National authorities will apply their own reasoning, but the indicators commonly discussed by practitioners mirror those used in EU consumer law. They include delivery to EU addresses, EU currencies at checkout, EU language versions, EU country-code domains, EU-specific shipping or returns pages, and advertising directed at EU audiences. None of these is decisive alone; together they make the picture clear.

A store that merely can be reached from Europe, with no shipping, currency or marketing aimed there, is in a weaker position for an authority to pursue. Many sellers nonetheless treat accessibility as a global baseline, since the same work also reduces exposure under US and UK rules.

Marketplaces versus own-brand storefronts

Selling through Amazon, Zalando, Etsy or another marketplace shifts part of the picture. The marketplace operator is the provider of the e-commerce service its interface delivers, so the accessibility of the search, checkout and account flows sits primarily with the platform. A seller still controls listing content (images, alt text where the platform supports it, product descriptions and specification data), and that content is part of what a disabled shopper experiences.

Own-brand storefronts carry the full obligation. A brand that runs a headless storefront, a Shopify theme it customised heavily, or a native app is the service provider for that experience, even if it rents the underlying platform. Platform vendors may supply accessible default themes and checkout components, but customisations, third-party apps and embedded widgets are the store’s responsibility.

Seller profile	EAA position (general)	Other regimes that may also apply
US brand with its own store shipping to the EU	In scope for EU-facing service unless the micro-enterprise test is met	ADA Title III litigation risk in the US, per US Department of Justice guidance
UK brand selling into the EU after Brexit	In scope for EU-facing service; the EAA is not UK law	UK Equality Act 2010 duties to make reasonable adjustments
Canadian brand selling into the EU	In scope for EU-facing service	Provincial rules such as Ontario’s AODA for Ontario operations
Third-party seller on an EU marketplace only	Platform carries most interface duties; seller controls listing content	Marketplace’s own seller policies and content rules
EU-based micro-enterprise selling services	Exempt from the service requirements under Article 4(5)	National law may go further; check the transposition

The micro-enterprise exemption and its limits

The directive contains a carve-out that is often summarised as “small businesses are exempt.” That summary is misleading. The exemption covers microenterprises providing services, and the definition of a microenterprise is tight: fewer than 10 persons employed, and either an annual turnover or an annual balance sheet total not exceeding EUR 2 million.

Most profitable direct-to-consumer brands with a real cross-border footprint are above that line, especially once contractors and fulfilment staff are counted the way national rules require. A brand with 15 employees and EUR 1.5 million in revenue is not a microenterprise under this definition, because the headcount test fails.

What the exemption does not cover

Three limits matter in practice. First, the exemption applies to services, not products: a microenterprise that manufactures or imports an in-scope product, such as an e-reader, does not escape the product requirements, although it benefits from lighter documentation rules. Second, the exemption is personal to the business; it does not extend to the platforms, payment providers or apps that the business relies on.

Third, the exemption is a snapshot. A brand that hires its tenth employee or crosses the financial threshold leaves the safe harbour, and the obligations apply to the service from that point. Growth plans and accessibility plans should therefore be written together, rather than treating the exemption as a permanent status.

The separate “disproportionate burden” route

Businesses above the micro threshold have a different, narrower route. Article 14 of the directive allows an economic operator to avoid a specific requirement where compliance would fundamentally alter the basic nature of the service, or impose a disproportionate burden. The assessment follows criteria set out in Annex VI, must be documented, and is not a blanket opt-out.

According to the directive, a service provider relying on this route has to renew the assessment periodically (every five years, or sooner if the service changes or an authority asks), and providers other than microenterprises are expected to inform the relevant market surveillance authorities. Receiving outside funding to improve accessibility weakens the argument that the cost is disproportionate.

Technical requirements in practice, not in legal language

The directive itself is written in functional terms. Annex I asks that services be perceivable, operable, understandable and robust, the same four principles that structure the W3C’s Web Content Accessibility Guidelines. It does not list button colours or code patterns, which is why harmonised standards matter.

Until standards cited specifically under the EAA are published in the Official Journal of the EU, most auditors and authorities use EN 301 549 as the reference. That European standard incorporates WCAG 2.1 at level AA for web content. Several consultancies already test against WCAG 2.2, which adds criteria on focus visibility, target size and accessible authentication; building to 2.2 is a sensible way to avoid a second remediation round later, but the binding reference should be verified with the national authority or the Commission at the time of any audit.

What “perceivable” means on a product page

A shopper who cannot see the product photo needs a text alternative that describes what matters for the purchase: color, material, pattern, fit. A shopper who cannot hear needs captions on product videos. A shopper with low vision needs text with sufficient contrast against its background, and a layout that still works when zoomed to 200 percent.

These are not exotic requirements. They are also the items most often flagged by automated scanners, which makes them good first fixes for teams with limited capacity.

What “operable” means in a checkout

Every function needs to work with a keyboard alone, in a logical order, with a visible focus indicator. Time limits need a way to extend them. Nothing should flash in a way that can trigger seizures. Drag-and-drop interactions (common in bundle builders and configurators) need a simple alternative.

Checkout is where operable failures hurt most, because a single keyboard trap in a payment iframe blocks the whole purchase. The directive’s specific mention of payment and identification functions reflects that reality.

What “understandable” and “robust” mean

Understandable means form fields have visible labels, errors are described in text and explained in a way that helps the shopper fix them, and the language of the page is declared so screen readers pronounce it properly. On multilingual EU storefronts, the declared language must match the content, which is a frequent miss on machine-translated pages.

Robust means the code is built so assistive technologies can interpret it: correct roles, names and states on custom components, and no reliance on visual cues alone. Custom dropdowns, carousels and modal dialogs are the usual offenders.

The overlay question

Many sellers have been pitched accessibility overlays: a script that adds a toolbar and promises automated compliance. Disability advocacy groups and many accessibility practitioners have criticised these tools publicly, and an overlay does not change the underlying code that an authority or auditor will test. Treating an overlay as a substitute for remediation is widely regarded as a risk rather than a solution.

Approach	Typical cost profile	What it changes	Value as EAA evidence
Automated scan only	Low, often included in platform tools	Finds a share of issues; fixes nothing alone	Weak; covers only machine-detectable criteria
Overlay toolbar	Low to moderate subscription	Adds user settings on top of existing code	Weak; underlying code is unchanged
Theme or component remediation	Moderate, front-loaded	Fixes shared templates used across the store	Strong when documented and retested
Expert manual audit plus fixes	Moderate to high	Finds and fixes issues automation misses	Strong; produces a report authorities recognise
Testing with disabled users	Variable	Validates real task completion	Strong supporting evidence

Accessibility statements and documentation you must hold

The EAA treats information as a requirement in its own right. Annex V asks service providers to include information on how the service meets the accessibility requirements in their general terms and conditions or an equivalent document, and to make it publicly available in written and oral format, in a way that is itself accessible. Most sellers implement this as an accessibility statement linked from the footer and referenced in the terms.

That information has to be specific. A credible statement describes the service, the standard used for testing (for example, WCAG 2.1 AA through EN 301 549), the date of the last assessment, known limitations with planned fix dates, and a contact route for shoppers who hit a barrier. A statement that only says “we are committed to accessibility” does not meet the purpose of the annex.

The documentation file behind the statement

Behind the public statement, a well-run seller keeps an internal file that an authority could ask to see. Typical contents include the most recent audit report and its scope, a remediation log with dates, the results of retesting, any Article 14 disproportionate burden assessment, and records of complaints with their resolution. Keeping this file current is cheap compared with reconstructing it after a complaint arrives.

Sellers relying on the micro-enterprise exemption should keep evidence of headcount and financial figures for each year. Authorities can ask how a business concluded it was exempt, and “we assumed so” is a poor answer.

Language versions

An EU-facing statement written only in English may not be enough where the store operates in German, French or Spanish. National transpositions vary, but the general principle in EU consumer law is that information should be available in the language the trader uses to sell. Translating the statement alongside the storefront avoids an avoidable gap.

Enforcement, complaints and national authorities

The EAA is enforced nationally. Each member state designates market surveillance authorities for products and authorities responsible for checking services, sets up procedures for consumers to complain, and lays down penalties that the directive requires to be “effective, proportionate and dissuasive.” The directive also requires that consumers, and organisations with a legitimate interest such as disability associations, be able to take action under national law.

The practical consequence for a cross-border seller is fragmentation. Germany implemented the Act through its Accessibility Strengthening Act (Barrierefreiheitsstärkungsgesetz, or BFSG), and commentators report fines of up to EUR 100,000 for certain listed breaches under that law. Other member states have chosen different authorities and ceilings, and published summaries disagree with one another, so any specific figure should be checked against the national text or the authority’s own publications before it is relied on.

How enforcement has looked so far

As of late August 2026, reported enforcement has been largely complaint-driven and corrective in tone, according to practitioner and press accounts. The pattern most often described is a complaint, a request for information, a corrective order with a deadline, and penalties only where a business fails to act. Disability organisations have been active: in France, for example, associations sent formal notices to several large grocery retailers in 2025 about the accessibility of their sites and apps, and some of those disputes have reached the courts, according to press reports.

That pattern means visibility matters. Large, well-known consumer brands attract complaints first, but smaller sellers in categories with engaged disability communities (assistive products, health, fashion and groceries) have also been named in advocacy campaigns. A store with a clear contact route and a track record of fixing reported barriers is in a better position when a complaint arrives.

Reaching a seller outside the EU

A reasonable question from US and UK sellers is how an authority in Berlin or Paris would enforce against a company with no EU entity. Direct collection of a fine across borders is harder, but authorities have other levers. They can work through payment providers, marketplaces and logistics partners operating in the EU, and EU platforms increasingly push compliance obligations down to the sellers that use them.

For brands that plan to grow in Europe, the more relevant risk is commercial: marketplace delistings, retail partner due diligence and the cost of retrofitting accessibility after a complaint. These are the same frictions covered in our guide to global trade for retail and cross-border commerce, where compliance increasingly decides which markets a brand can scale in.

Enforcement element	Set at EU level	Set nationally
Which services are covered	Yes, in the directive	Member states may extend, not narrow
Functional requirements	Yes, Annex I	Applied through harmonised standards
Which authority checks services	No	Yes, designated in each transposition
Complaint channel for consumers	Required in principle	Procedure set nationally
Penalty amounts	Only the “effective, proportionate and dissuasive” test	Yes, ceilings vary widely by country
Transition periods	Yes, Article 32	Some states shortened them

Transition periods that are often misread

Article 32 of the directive allows service providers to keep using products that were lawfully in use before June 28, 2025 until June 28, 2030, and lets service contracts agreed before that date continue unchanged until they expire, subject to a five-year maximum. Some sellers have read this as a five-year grace period for their websites. It is not: the transition concerns products used to deliver a service and pre-existing contracts, not a general delay for storefront accessibility.

Sequencing the work for a small catalog team

A team of three or four people running a store with a few hundred products cannot fix everything at once, and does not need to. The goal is a credible, documented programme that removes the barriers that stop purchases first, then works outwards. The sequence below is a common pattern in practice; it describes how work is typically ordered, not a prescribed legal route.

Weeks 1–4: baseline and ownership

Start by running an automated scan across the main templates (homepage, category, product, cart, checkout, account) and pairing it with a short manual review of the checkout using only a keyboard and a screen reader. Name an owner for accessibility, even if it is a part-time role. Record the results with dates; this is the first entry in the documentation file.

At the same time, confirm whether the business meets the micro-enterprise test, and write the answer down with the figures used. If the answer is no, the rest of the plan applies in full.

Weeks 5–12: shared components and checkout

Fix the components that appear everywhere: header navigation, search, filters, buttons, form fields, modals and the product image gallery. Because themes reuse these, one fix can clear hundreds of page-level issues. Then work through checkout, including any third-party payment and identity widgets; where a vendor component fails, ask the vendor for its own conformance report and roadmap.

Platform choice matters here. Some hosted platforms ship accessible checkout flows that merchants cannot easily break, while heavily customised or headless builds put more of the burden on the merchant. Our comparison of how to choose the right e-commerce platform is a useful lens if a replatform is already under discussion.

Weeks 13–20: catalog content and media

With templates fixed, the remaining work is content. Write meaningful alt text for primary product images, caption product videos, check color contrast in banners and promotional tiles, and add accessibility attributes to product data where suppliers provide them. Batch this by category, starting with best sellers, so effort follows revenue.

This is also the point to publish the accessibility statement, translated into each storefront language, and to link it from the footer and the terms. Include a working contact route and a response target.

Ongoing: retest, log and maintain

Accessibility decays with every theme update, new app and seasonal campaign. Build a short check into the release process for template changes, rerun the automated scan monthly, and repeat a manual audit at least annually or after major redesigns. Keep the remediation log current.

For brands still choosing where to expand, accessibility readiness belongs in the market selection scorecard. Our piece on choosing a first cross-border market covers the commercial factors; the EAA adds a compliance factor that applies to every EU market at once, which can actually simplify the choice once the work is done.

Phase	Main tasks	Evidence produced
Weeks 1–4	Scan, keyboard and screen reader check of checkout, micro-enterprise test, owner named	Baseline report, exemption assessment
Weeks 5–12	Fix shared components, checkout, payment and identity flows; request vendor reports	Remediation log, vendor conformance documents
Weeks 13–20	Alt text, captions, contrast, product accessibility data, statement published	Accessibility statement in each language, content checklist
Ongoing	Release checks, monthly scans, annual manual audit, complaint handling	Retest results, complaint records

Accessibility work on an EU-facing store overlaps heavily with the wider accessibility duties that apply in the US, the UK and Canada. Teams that want the full cross-jurisdiction picture, including physical stores, procurement requests and a four-quarter budget, can continue with our guide to accessible storefronts, stores and the rules that now apply.

Important note on legal information

This article is general information about the European Accessibility Act and how it is commonly applied to online stores. It is not legal advice, and it does not take into account the facts of any particular business. The directive is implemented through national laws that differ in their authorities, procedures, transition periods and penalties, and those laws and their official guidance change over time. Figures and dates here reflect publicly available sources as of late August 2026; verify current rules with the European Commission, the text of Directive (EU) 2019/882 on EUR-Lex and the relevant national authority, and consult a qualified lawyer or accessibility compliance specialist in the countries where you sell before making decisions.

FAQ on the European Accessibility Act

Does the European Accessibility Act apply to a US online store?

It can. The directive applies to e-commerce services provided to consumers in the EU, according to the European Commission, regardless of where the seller is based. A US store that ships to EU addresses, prices in euros or markets to EU shoppers is generally considered to be offering its service there, unless it qualifies for the micro-enterprise exemption.

When did the EAA start applying to online shops?

The requirements have applied since June 28, 2025. Member states were required to transpose the directive into national law by June 28, 2022. Some transition arrangements under Article 32 run to 2030, but they relate to products used to deliver services and to pre-existing service contracts, not to a general delay for storefronts.

Who counts as a micro-enterprise under the EAA?

The directive defines a microenterprise as a business employing fewer than 10 persons with an annual turnover or annual balance sheet total not exceeding EUR 2 million. Microenterprises providing services are exempt from the service requirements. The exemption does not cover products, and it ends when a business crosses either threshold.

Which technical standard do authorities use to test a store?

Most auditors and authorities currently refer to EN 301 549, which incorporates WCAG 2.1 level AA for web content, while harmonised standards cited specifically under the EAA are being finalised. Many practitioners test against WCAG 2.2 to stay ahead. The applicable reference should be confirmed with the national authority or the Commission at the time of an audit.

Does selling only on Amazon or another marketplace remove the obligation?

Largely, for the interface itself. The marketplace operator provides the e-commerce service its search, account and checkout flows deliver. Sellers still control listing content, such as images, descriptions and product specifications, and marketplaces may set their own content rules that reflect accessibility expectations.

Is an accessibility overlay enough to comply?

Overlays are widely criticised by disability organisations and accessibility practitioners because they do not change the underlying code that auditors test. They are generally seen as weak evidence of conformance. Remediating templates and components, and documenting the work, is the approach most practitioners recommend.

What happens if a shopper complains about a store?

Procedures are set nationally. Reported practice so far is that an authority requests information, may issue a corrective order with a deadline, and moves to penalties where a business does not act. Disability organisations in several member states can also bring actions under national law, according to the directive’s enforcement provisions.

How large are the fines for EAA non-compliance?

Penalties are set by each member state and vary widely. In Germany, commentators report ceilings of up to EUR 100,000 for certain breaches under the BFSG; published figures for other states differ between sources. Check the national transposition law or the authority’s own publications for current amounts rather than relying on summaries.

What should an accessibility statement contain?

Under Annex V, service providers explain how the service meets the accessibility requirements, in their terms or an equivalent document. A credible statement typically names the standard tested against, the date of the last assessment, known limitations with planned fixes, and a contact route for shoppers, and it is published in the languages the store sells in.