What is the European Accessibility Act and does it apply to my business?

The European Accessibility Act deadline was June 28, 2025. It applies to e-commerce businesses selling in the EU with more than 10 employees or over €2M annual revenue. Non-compliance risks fines up to €100,000 in some member states plus potential market access restrictions.

What is the European Accessibility Act?

The EAA is EU legislation (Directive 2019/882) that sets accessibility requirements for products and services, including e-commerce. It aims to harmonize accessibility rules across EU member states and ensure people with disabilities can fully participate in digital commerce.

The directive covers websites, mobile apps, and all digital touchpoints involved in selling products or services online. The compliance standard it references is EN 301 549, which in turn references WCAG 2.1 Level AA as the technical baseline.

Does the EAA apply to my business?

The EAA applies if you:

• Sell products or services to consumers in the EU
• Have more than 10 employees, OR
• Have annual turnover exceeding €2 million

Microenterprises (fewer than 10 employees AND under €2M turnover) are exempt from the e-commerce provisions, though accessibility remains a commercial best practice regardless of legal obligation.

Important: If you’re based outside the EU but sell to EU customers, the EAA still applies to you. The law follows the consumer, not the business location.

Key deadline: June 2025 (already passed)

The compliance deadline was June 28, 2025. Enforcement began after this date, with EU member states implementing their own penalty structures. If you’re reading this in 2026 and your e-commerce site isn’t compliant, enforcement risk is active.

What compliance requires

E-commerce websites must meet EN 301 549 / WCAG 2.1 Level AA requirements across four principles:

Perceivable

• Text alternatives for all non-text content (alt text for images)
• Captions and transcripts for video and audio content
• Sufficient color contrast (4.5:1 for normal text, 3:1 for large text)
• Content readable and functional when zoomed to 200%
• Content doesn’t depend on color alone to convey meaning

Operable

• Full keyboard accessibility — every function must work without a mouse
• No keyboard traps
• Skip navigation links to bypass repeated header content
• Sufficient time to complete tasks (session timeout warnings)
• No content that flashes more than 3 times per second

Understandable

• Clear, consistent navigation across pages
• Form labels and error messages that explain what’s needed
• Predictable page behavior — pages don’t change context without warning

Robust

• Valid, semantic HTML
• Compatible with assistive technologies (screen readers, switch access, etc.)
• ARIA labels for custom interface components

Penalties for non-compliance

Each EU member state sets its own enforcement and penalties. Current known penalty structures:

• Germany: Administrative fines up to €100,000 per violation
• France: Fines up to €50,000 per violation, public naming on a blacklist
• Netherlands: Administrative fines and potential market restrictions
• Ireland: Enforcement pending final transposition legislation

Beyond financial penalties, non-compliant businesses face reputational risk, potential litigation from disabled users under national discrimination law, and — for businesses dependent on EU public sector contracts — potential disqualification.

The accessibility statement requirement

The EAA requires businesses to publish an accessibility statement on their website. This document must:

• State the level of accessibility conformance achieved
• List known accessibility issues and planned remediation timeline
• Provide contact information for accessibility-related complaints
• Reference enforcement mechanisms available to users

Publishing an honest accessibility statement showing ongoing improvement is better than claiming full compliance you haven’t achieved. Misrepresenting compliance creates additional legal exposure.

Steps to achieve EAA compliance in 2026

If you haven’t started yet, this is the practical path:

1. Audit your current state — Use automated tools (axe, WAVE) to identify issues across your key pages: homepage, product pages, category pages, checkout. Then supplement with manual keyboard and screen reader testing.

2. Prioritize the critical path — Focus on checkout accessibility, product page keyboard operability, and navigation first. These affect conversion and are most likely to be the basis of complaints.

3. Fix high-impact issues — Alt text, keyboard navigation, color contrast, form labels. A developer sprint of 5-10 days addresses the majority of common issues.

4. Test with real users — Validate fixes with people who use assistive technologies. Automated tools catch only 30-40% of real accessibility issues.

5. Publish your accessibility statement — Document what you’ve fixed, what’s still being worked on, and how users can report issues.

6. Establish ongoing processes — Accessibility must be maintained. Add it to your QA checklist, design review process, and developer acceptance criteria for all future work.

The business case beyond compliance

15-20% of the EU population has some form of disability. Making your store accessible opens your market to these customers and typically lifts conversion rates for all users by 10-20%, as the UX improvements are universally beneficial.

A UX audit includes accessibility evaluation against WCAG 2.1 AA as standard, with a prioritized remediation plan that addresses EAA requirements while delivering measurable conversion improvements.

For a complete breakdown, read European Accessibility Act Ecommerce Compliance: Complete Guide for Online Retailers.