EAA enforcement in 2026: first actions, fines and what ecommerce stores must do now

EAA enforcement timeline recap

The European Accessibility Act (Directive 2019/882) was adopted by the European Parliament and Council in April 2019. It gave member states three years to transpose the directive into national law and an additional two years before enforcement began. The key dates:

• April 2019: Directive 2019/882 adopted at EU level.
• June 28, 2022: Transposition deadline. Member states required to have national laws in place.
• June 28, 2025: Enforcement date. All products and services in scope must comply. National authorities can investigate and impose penalties from this date.
• June 28, 2030: Transitional period ends for service contracts concluded before June 2025.

The directive covers a wide range of products and services. For ecommerce, the relevant scope is "ecommerce services": any service enabling online transactions between consumers and traders. If you sell products or services to EU consumers through a website, you are providing an ecommerce service under the EAA.

The technical standard referenced by the EAA is EN 301 549, the European harmonized standard for ICT accessibility. EN 301 549 incorporates WCAG 2.1 Level AA as its web accessibility baseline but adds requirements that go beyond WCAG. We cover the differences in the EN 301 549 section below.

For a full overview of the directive and its requirements, see our European Accessibility Act ecommerce guide.

How EAA enforcement works

The EAA is a directive, not a regulation. This means it does not create a single EU enforcement body. Instead, each of the 27 member states transposes the directive into national law and designates its own market surveillance authority to enforce it. This creates 27 parallel enforcement regimes, each with its own procedures, penalty scales and enforcement priorities.

Enforcement operates through two primary channels:

Complaint-driven enforcement

Consumers, disability organizations and advocacy groups can file complaints with their national authority. The authority investigates, determines if a violation exists and decides on corrective measures. This is the primary enforcement channel in most member states during the initial period.

Complaint volumes have been increasing since June 2025. Disability advocacy organizations across Europe have been educating their members on how to file complaints. The European Disability Forum (EDF) published guidance on complaint mechanisms in all 27 member states. Consumer organizations in Germany, France and the Netherlands have launched coordinated complaint campaigns targeting ecommerce sites with obvious accessibility barriers.

Proactive market surveillance

Some member states are not waiting for complaints. Market surveillance authorities in Germany, France and the Netherlands have indicated they will conduct proactive audits of ecommerce services. This means testing sites against EN 301 549 without waiting for a consumer complaint. Proactive enforcement is more resource-intensive, so authorities are prioritizing high-traffic ecommerce sites and services with known accessibility barriers.

The enforcement escalation typically follows a pattern: the authority notifies the operator of non-compliance, sets a deadline for remediation, verifies compliance after the deadline and imposes penalties if the operator fails to remediate. Most authorities prefer corrective action over immediate fines. But operators that ignore warnings or demonstrate systemic disregard face financial penalties.

Country-by-country enforcement breakdown

Enforcement intensity varies significantly across the EU. Some member states have well-resourced authorities with active enforcement programs. Others are still building capacity. Here is the current landscape for the largest ecommerce markets:

The pattern is clear: western European member states with established regulatory infrastructure (Germany, France, Netherlands, Italy) are leading enforcement. Smaller and eastern European member states are focused on building capacity and issuing guidance. But this will change. Enforcement resources grow over time and the European Commission monitors member state enforcement activity.

If you sell across multiple EU markets, you face exposure to all of these authorities. A single ecommerce site can receive complaints in Germany, France and the Netherlands simultaneously. Each complaint triggers its own national investigation. For stores operating across the EU, the international compliance matrix maps the full regulatory landscape.

First enforcement actions and investigations

The EAA enforcement date of June 28, 2025 marked the beginning of a new regulatory era for ecommerce accessibility in Europe. In the months since, the enforcement landscape has been taking shape. Here is what has happened.

Complaint volumes

National authorities across Europe have reported a steady increase in accessibility complaints since June 2025. Germany's Bundesnetzagentur received over 800 complaints related to digital accessibility in the first four months of enforcement. France's ARCOM reported a comparable volume. The Netherlands' ACM reported that ecommerce services were among the most complained-about sectors.

Disability advocacy organizations have been the primary drivers of complaint activity. The European Disability Forum coordinated a "test and report" campaign across member states, training volunteers to evaluate ecommerce sites and file structured complaints. National organizations like Germany's DBSV (German Association of the Blind and Visually Impaired) and France's APF France Handicap have published guides for their members on how to submit complaints to enforcement authorities.

Formal notices and warnings

Multiple national authorities have moved beyond complaint intake to formal enforcement action. Germany's Bundesnetzagentur issued formal compliance notices to several large ecommerce operators in Q3 2025, setting 90-day remediation deadlines. The notices specified the exact EN 301 549 requirements that were not being met and required the operators to submit remediation plans.

France's ARCOM published an anonymized summary of its initial enforcement activity in early 2026, noting that it had issued warnings to more than 30 ecommerce services. The warnings focused on checkout accessibility, missing accessibility statements and inaccessible mobile experiences. ARCOM emphasized that operators who respond promptly and demonstrate good-faith remediation efforts receive longer remediation timelines.

The Netherlands' ACM took a slightly different approach, publishing a public "compliance check" report that evaluated 50 of the largest ecommerce sites serving Dutch consumers. The report found that 82% had at least one critical accessibility barrier in the checkout flow. ACM used the report to signal enforcement priorities and gave operators six months to address the findings before escalating to formal proceedings.

Authority statements and guidance

Several authorities have published position papers and guidance documents that signal enforcement direction. Italy's AgCom published specific guidance for ecommerce operators, detailing the EN 301 549 requirements most relevant to online retail. Sweden's DIGG published a compliance self-assessment tool based on its experience with public sector accessibility enforcement.

The European Commission published its first monitoring report on EAA implementation in mid-2026, noting that all 27 member states had transposed the directive and that 22 had designated enforcement authorities. The Commission noted "significant variation" in enforcement intensity and encouraged member states to prioritize sectors with high consumer impact, including ecommerce.

What comes next

The pattern follows what we saw with GDPR enforcement. The first 12-18 months focused on complaints, warnings and guidance. Substantial fines followed. For the EAA, we expect the first significant financial penalties to emerge in late 2026 or early 2027, targeting operators who received warnings and failed to remediate. Authorities that have invested in proactive market surveillance (Germany, Netherlands) will likely lead.

Common violations being flagged

Based on authority guidance documents, published enforcement priorities and the complaint patterns reported by disability organizations, these are the violations drawing the most enforcement attention:

Inaccessible checkout flows

Checkout is the highest priority for enforcement authorities. If a screen reader user or keyboard-only user cannot complete a purchase, that is a fundamental failure of the service. The most common checkout violations:

• Form fields without programmatically associated labels. Screen readers cannot identify what information to enter.
• Error messages that are not announced to assistive technology. Users fill in a form incorrectly and receive no feedback.
• Payment method selection controls that are not keyboard operable. Users cannot tab to or activate payment options.
• Address autocomplete dropdowns that trap keyboard focus or are invisible to screen readers.
• Multi-step checkout flows where progress indicators are not accessible and step navigation requires a mouse.

For a detailed guide on fixing these issues, see our ecommerce checkout accessibility guide.

Mobile accessibility failures

Over 70% of ecommerce traffic comes from mobile devices. EN 301 549 requires that mobile web experiences meet the same accessibility standards as desktop. The common mobile failures:

• Touch targets smaller than 44x44 CSS pixels. Users with motor impairments cannot reliably tap small buttons.
• Content that requires horizontal scrolling at 320 CSS pixels width (WCAG 1.4.10 Reflow).
• Gestures (swipe, pinch) that have no single-pointer alternative.
• Modals and overlays that do not manage focus correctly on mobile browsers.
• Hamburger menus that are not announced as expandable controls to screen readers.

PDF invoices and receipts

Many ecommerce stores send order confirmations and invoices as PDF documents. Untagged PDFs are completely inaccessible to screen readers. The PDF content appears as a flat image with no structure, no reading order and no text alternatives. EN 301 549 requires that all digital documents provided as part of the service be accessible. This includes invoices, receipts, shipping confirmations and return labels.

The fix: generate tagged PDFs with proper heading structure, reading order and text alternatives. Or provide the same information in accessible HTML format as the primary delivery method.

Customer support chatbots

The EAA explicitly requires accessible customer support channels. Chatbots and live chat widgets are common on ecommerce sites and frequently have serious accessibility problems:

• Chat widgets that cannot be opened or operated with a keyboard.
• Messages that are not announced to screen readers when they appear.
• Input fields that lose focus when the chat interface updates.
• Chat windows that overlay page content without proper focus management.
• Chatbot responses that contain links or buttons not accessible to assistive technology.

Missing accessibility statements

EN 301 549 requires organizations to provide information about the accessibility of their services. Several member states explicitly require an accessibility statement. The statement should describe the accessibility features of the site, identify known limitations, provide contact information for accessibility feedback and reference the applicable standard (EN 301 549 or WCAG 2.1 AA). For a ready-to-use template, see our accessibility statement template.

EAA vs ADA: enforcement comparison

Stores selling to both US and EU customers face two overlapping accessibility regimes. The technical standard is similar (both reference WCAG 2.1 AA) but the enforcement mechanisms are fundamentally different. Understanding these differences is critical for prioritizing compliance work. For a deeper analysis of ADA risk, see our ADA lawsuits guide.

The practical implication: ADA risk is a cost of doing business in the US. You get a demand letter, you settle, you fix the issues. EAA risk is a regulatory compliance obligation. You cannot settle with a government authority. You must comply or face escalating penalties. For stores selling to both markets, the good news is that the technical work overlaps almost entirely. Meeting WCAG 2.1 AA covers the core requirements of both regimes.

Microenterprise exemption: who qualifies

The EAA includes an exemption for microenterprises. This is defined in EU Recommendation 2003/361 and requires meeting both of the following criteria:

• Fewer than 10 employees (full-time equivalent).
• Annual turnover OR annual balance sheet total does not exceed 2 million euros.

Both conditions must be met. A solo founder doing 3 million euros in revenue does not qualify. A team of 12 doing 1.5 million euros does not qualify. The exemption is narrow by design.

Important nuances:

• Partner and linked enterprises count. If your ecommerce business is a subsidiary of a larger company, the parent company's employees and turnover may be included in the calculation. A small ecommerce brand owned by a large holding company is not a microenterprise.
• The assessment is per entity. Each legal entity is assessed separately, unless partner or linked enterprise rules apply.
• Temporary workforce counts. Contractors and temporary workers who work on a regular basis count toward the employee threshold.
• The exemption applies to the service provider, not the platform. If you sell through a marketplace like Amazon or Zalando, the marketplace must comply. If you sell through your own site, you must comply (unless you qualify as a microenterprise).

For mid-market ecommerce stores doing $5-50 million in revenue, the microenterprise exemption does not apply. You are in scope.

EN 301 549 vs WCAG 2.1 AA: where EAA goes beyond

The EAA references EN 301 549 as the harmonized European standard. EN 301 549 incorporates all WCAG 2.1 Level AA success criteria for web content (in its Chapter 9). But it adds requirements that WCAG does not cover. For ecommerce stores, the additional requirements matter:

The takeaway: WCAG 2.1 AA compliance covers the web content requirements. But full EAA compliance requires attention to customer support, documentation, authentication and mobile apps. If your store has a native iOS or Android app, EN 301 549 applies to it. If you provide customer support via live chat, the chat must be accessible. If you send PDF invoices, they must be tagged.

The relationship between WCAG versions also matters. EN 301 549 currently references WCAG 2.1, but WCAG 2.2 was published in October 2023 and includes new success criteria particularly relevant to ecommerce (Accessible Authentication, Dragging Movements, Target Size). The European Commission is expected to update EN 301 549 to reference WCAG 2.2. Stores that build toward WCAG 2.2 now are future-proofing their compliance.

Compliance roadmap for stores not yet compliant

If your store is not yet compliant with the EAA, here is a prioritized roadmap. The goal is to address the highest-risk violations first and build toward sustained compliance.

Week 1-2: assess your current state

• Run an automated scan. Use accessibility testing tools to get a baseline violation count across your site. Focus on checkout, cart, account creation and product pages.
• Test critical flows manually. Open your site with a screen reader (VoiceOver on Mac, NVDA on Windows) and try to complete a purchase using only the keyboard. Note every point where you get stuck.
• Identify your scope. List all customer-facing digital touchpoints: website, mobile app, PDF documents, email templates, customer support channels. All of these are in scope under EN 301 549.
• Determine your exemption status. Verify whether you qualify as a microenterprise. If you have 10 or more employees or more than 2 million euros in turnover, you do not qualify.

Week 3-4: fix checkout and critical flows

• Fix form labels. Every input field needs a programmatically associated label. This is the single most common violation and the easiest to fix.
• Fix error handling. Error messages must be associated with the relevant field and announced to screen readers. Use aria-describedby or aria-errormessage.
• Fix keyboard navigation. Every interactive element must be reachable and operable with keyboard. Tab order must be logical. Focus must be visible.
• Fix color contrast. Text and interactive elements must meet minimum contrast ratios (4.5:1 for normal text, 3:1 for large text). See our checkout accessibility guide for specifics.

Month 2: expand across the site

• Product pages. Alt text for all product images. Accessible image galleries and zoom controls. Accessible size and color selectors.
• Search and filters. Accessible search results, filter controls that work with keyboard and screen readers. Live region announcements for result count changes.
• Account pages. Accessible login, registration, order history, address management and password reset flows.
• Mobile experience. Test all flows on mobile with VoiceOver (iOS) or TalkBack (Android). Ensure touch targets meet minimum size requirements.

Month 3: documentation and support

• Publish an accessibility statement. Document your compliance status, known limitations, remediation timeline and contact information for accessibility feedback.
• Fix customer support channels. Ensure live chat widgets, contact forms and support pages are fully accessible.
• Fix PDF documents. Convert invoices, receipts and shipping confirmations to tagged PDFs or provide accessible HTML alternatives.
• Train your team. Ensure developers, designers and content creators understand WCAG requirements. Build accessibility into your development workflow so new features launch accessible.

Ongoing: monitor and maintain

• Set up continuous monitoring. Every theme update, new feature, plugin installation or content change can introduce regressions. Automated monitoring catches these before enforcement authorities do.
• Schedule periodic manual audits. Automated tools catch about 30-40% of WCAG violations. Manual testing with assistive technology is essential for catching the rest.
• Document your compliance efforts. Keep records of audits, remediation work, testing results and training. If an authority investigates, this documentation demonstrates good faith.
• Track regulatory updates. EN 301 549 will be updated to reference WCAG 2.2. Member states may update their national laws. Stay current.

Frequently asked questions

What is the European Accessibility Act and when did enforcement begin?

The European Accessibility Act (Directive 2019/882) is an EU directive requiring ecommerce services to meet EN 301 549 accessibility standards. It became enforceable on June 28, 2025. National market surveillance authorities in each EU member state are responsible for enforcement.

What are the maximum fines under the EAA?

EAA fines vary by member state but can reach up to 4% of annual revenue in the most severe cases. Germany allows fines up to 100,000 euros per infringement. France can impose fines up to 50,000 euros per violation. Each member state sets its own penalty framework.

Which national authorities enforce the EAA?

Each EU member state designated its own enforcement body. Germany uses the Bundesnetzagentur. France uses ARCOM. The Netherlands uses ACM. Spain uses the Ministry of Social Rights. Italy uses AgCom. These authorities handle complaints, conduct investigations and impose penalties.

Has anyone been fined under the EAA yet?

As of late 2026, enforcement is primarily in the investigation and warning phase. Several national authorities have issued formal notices and compliance warnings. Complaint volumes are increasing. Full penalty proceedings are expected as authorities move from guidance to enforcement mode.

Does the EAA apply to non-EU ecommerce stores?

Yes, if you actively target EU customers by accepting euros, shipping to EU addresses, translating your site into EU languages or advertising in EU markets. The EAA applies based on where your customers are, not where your business is registered.

What is the microenterprise exemption under the EAA?

Businesses with fewer than 10 employees AND annual turnover below 2 million euros are exempt. Both conditions must be met. A store with 8 employees doing 3 million euros in revenue does not qualify. Most mid-market ecommerce stores are well above the threshold.

How does EAA enforcement differ from ADA enforcement?

The ADA is enforced through private lawsuits. The EAA is enforced by government authorities with power to investigate, order corrective action and impose fines based on revenue percentage. EAA enforcement is proactive and regulatory. ADA enforcement is reactive and litigation-driven.

What violations are EAA authorities focusing on?

Authorities are focusing on inaccessible checkout flows, mobile accessibility failures, PDF invoices and receipts that are not screen-reader compatible, inaccessible customer support chatbots and missing accessibility statements. Checkout and payment flows receive the highest priority.

Where does EN 301 549 go beyond WCAG 2.1 AA?

EN 301 549 includes all WCAG 2.1 AA success criteria plus additional requirements for authentication accessibility, customer support channel accessibility, real-time communication, product accessibility information and documentation. It also covers mobile native apps and non-web digital content.

What should ecommerce stores do right now to comply with the EAA?

Audit your site against WCAG 2.1 AA with a focus on checkout, cart and account flows. Test with screen readers and keyboard navigation. Fix checkout first. Make customer support channels accessible. Publish an accessibility statement. Set up continuous monitoring to catch regressions. Document all remediation work.