Is your store in scope?
This article was drafted with AI assistance and reviewed by our team before publishing.
The European Accessibility Act (EAA) has applied since 28 June 2025, with enforcement handled by national authorities across all 27 EU member states. If you run an e-commerce store that accepts orders from EU customers — even if your business is based in the US, the UK, Canada, or anywhere else — you may be in scope. Many store operators haven't fully worked through whether this applies to them, and a common assumption is that non-European businesses are automatically excluded. That assumption isn't straightforward, and it's worth understanding exactly who the rules cover before drawing that conclusion. The harder challenge is that even stores that have done some accessibility work may still have gaps — not because their homepage is broken, but because of what happens at checkout. Accessibility conformance under the EAA is tied to the harmonised standard EN 301 549, which incorporates WCAG 2.1 AA. Those requirements include a "complete processes" rule that catches many stores off guard: a purchase flow is treated as a single process, and if one step in that process fails an accessibility check, the entire flow fails to conform. A well-designed storefront offers limited protection if the cart or payment page breaks conformance. This is the kind of problem that doesn't announce itself. There's no error message, no failed transaction, no customer complaint you can trace back to it. The risk accumulates quietly, until an enforcement action or a formal complaint makes it visible all at once.
The Deadline Has Passed — and National Authorities Are Checking
Directive (EU) 2019/882 required EU member states to transpose it into national law and begin applying it from 28 June 2025. That date has passed. Member states have designated enforcement bodies and non-compliant businesses may face fines, injunctions, or orders affecting their ability to operate in EU markets, depending on the member state and how national transposition has been implemented. Enforcement scope and priorities differ by country, so businesses should check the rules in each member state where they have meaningful consumer exposure. It's also important to note that national transposition varies. The Directive sets minimum requirements, but individual member states may have implemented it with additional specificity or different enforcement structures. There is no single pan-EU enforcement body — the practical implications of non-compliance depend on which national regulator acts and under which national law.
Who Is Actually in Scope — and Who Is Exempt
The Directive's scope covers e-commerce services provided to consumers in the Union. Article 2(2)(f) lists e-commerce among the services to which the Directive applies, and Article 3(4) defines "service provider" as any natural or legal person who provides a service on the Union market or makes offers to provide a service to consumers in the Union. The Directive does not expressly address providers established outside the EU, so how it applies to non-EU stores depends on national law and enforcement practice — businesses should check the position in each member state where they have meaningful consumer exposure. The Directive also includes a meaningful exemption for microenterprises. Under Article 4(5), microenterprises — defined in Article 3(23) as businesses with fewer than 10 employees and an annual turnover or balance sheet total not exceeding €2 million — are exempt from the accessibility requirements for services. As Recital 42 makes clear, an online store is an e-commerce service (a service provided at a distance through websites or apps with a view to concluding a consumer contract), and this is the case even when the store sells physical goods. The microenterprise exemption can therefore apply to small online stores. If your store falls below both thresholds, you should check whether you qualify under the national laws of the member states where you operate. If you are not a microenterprise, the scope question is more straightforward: if you are offering e-commerce services to consumers in the EU, the Directive applies to the digital touchpoints involved in those transactions.
Why Checkout Flows Are Where Compliance Often Breaks Down
Compliance checks already conducted by national authorities confirm what accessibility practitioners have long observed: checkout and transactional flows are consistently where accessibility problems concentrate. The Dutch Authority for Consumers and Markets (ACM) tested around 100 of the largest online stores in the Netherlands and found that on 61% of them it is impossible to place an order using assistive technology. The ACM stated that companies that do not improve risk enforcement action — making clear this is a widespread problem, not an edge case. The most common failure points aren't obscure technical details. Checkout accessibility reviews consistently surface the same recurring issues: form fields missing accessible labels, error messages that aren't announced to screen reader users, payment widgets — especially third-party embeds — that don't meet keyboard navigation requirements, and modal dialogs that trap focus in ways that make them unusable without a mouse. These aren't cosmetic issues. They can make the purchase process practically impossible for users who rely on assistive technology. The third-party widget problem deserves specific attention. Many stores outsource their payment UI to embedded processors and assume that because a reputable company built it, it must be accessible. That assumption frequently doesn't hold. Even when a payment processor's hosted page is accessible in isolation, the integration — how it is embedded, how errors are surfaced, how the transition between your checkout and their payment frame is handled — is often where conformance breaks down. How liability is allocated in that scenario will depend on your contractual arrangements and the applicable national law, and is a question worth raising with legal counsel.
What the Complete Processes Rule Actually Means for Your Store
The W3C WCAG 2.1 conformance requirements define a "complete process" as a sequence of steps that must all be completed to accomplish a task. The W3C's conformance documentation is explicit: if a web page is part of a series of web pages presenting a process, all pages in that process must conform at the declared level. Buying something is a complete process. This changes how you have to think about your audit strategy: you cannot check pages in isolation. You have to evaluate the entire purchase journey as a single unit. This means your audit needs to walk through every step a user takes from adding an item to the cart through receiving an order confirmation — testing each step for keyboard accessibility (can a user who cannot use a mouse complete every action?), screen reader compatibility (are all interactive elements properly labeled and announced?), color contrast (do error states and required field indicators meet minimum contrast ratios?), and timeout handling (if your checkout session expires, is the user warned and given time to respond?). It also means that fixing your homepage or your product pages without touching the checkout funnel leaves your conformance posture essentially unchanged. The complete processes rule means conformance is only as strong as its weakest step.
Practical Steps to Identify and Address Gaps
Start with a real audit of your checkout flow — not an automated scan of your homepage. Tools like Axe, WAVE, or Lighthouse can surface a portion of issues quickly and at no cost, but treat their output as a starting point, not a verdict. Automated tools are widely understood to catch only a subset of actual WCAG failures; manual testing by someone who uses assistive technology, or by a trained auditor who simulates those conditions, is necessary to surface the rest. Work through your checkout step by step. For each step, verify: every form field has a visible label that is also programmatically associated with the input (not just visually near it); error messages identify which field failed and explain how to fix it; all interactive elements are reachable and operable using only a keyboard; and any third-party payment widget behaves correctly when navigated without a mouse. Document your findings with specific WCAG 2.1 success criteria references — this documentation matters for demonstrating good-faith efforts if a question is ever raised about your compliance posture. Many national transpositions of the EAA also require service providers to publish an accessibility statement — a page that declares your conformance status, identifies known gaps, and provides contact information for users who encounter barriers. The specific requirements for this statement vary by member state, so check the applicable national law for markets where you have meaningful consumer exposure. Prioritize remediation in order of user impact and transaction criticality. Payment form accessibility comes before navigation menu improvements. Screen reader compatibility on the address entry step matters more than optimizing your product image alt text. Work from the checkout backward, not from the homepage forward. Finally, build a process for keeping conformance current. Third-party scripts update, A/B tests introduce new UI elements, and platform updates can silently break previously conformant components. A one-time audit is a starting point, not a solution. Periodic checks on your checkout flow, integrated into your standard release process, are what turn a point-in-time fix into a durable posture. Kova Design Studio designs and builds e-commerce storefronts and checkout flows, including with accessibility requirements in mind as part of the build process. --- *This article is for informational purposes only and does not constitute legal advice. Businesses should consult qualified legal counsel for their specific situation.*