European Accessibility Act (EAA): What US and EU Businesses Must Know in 2026

Unlike the ADA Title II deadline (which targets US government entities), the EAA covers private sector products and services across multiple industries.

Products Covered:
• Computers and operating systems
• ATMs, payment terminals, and ticket machines
• Smartphones and tablets
• E-readers and related equipment
• Consumer banking hardware

Services Covered:
• E-commerce websites and platforms
• Banking and financial services
• Transportation ticketing and check-in
• Telecommunications and messaging
• Audiovisual media services
• E-books and dedicated reading software

Technical Standard: EN 301 549

The EAA references the harmonized European standard EN 301 549 for digital accessibility requirements. EN 301 549 incorporates WCAG 2.1 Level AA as its web content baseline — the same standard required under the US ADA Title II rule.

This means a website that meets WCAG 2.1 AA satisfies the core digital requirements of both laws.

Timeline:
• June 28, 2025: Enforcement begins for new products and services
• June 28, 2030: Deadline for existing services already on the market
• Archived content: Specific exceptions apply, but active services do not qualify

Microenterprise Exemption: Businesses with fewer than 10 employees AND annual turnover under €2 million are exempt from service requirements (but not product requirements). This exemption does not apply to businesses of any size outside the EU that serve the EU market.

Both the EAA and the ADA aim to make digital services accessible to people with disabilities. But they differ significantly in scope, enforcement, and legal structure.

Scope:
• ADA Title II: US state and local government entities (50,000+ population by April 2026)
• ADA Title III: US private businesses open to the public (no explicit WCAG mandate, but courts apply it)
• EAA: Private sector products and services across banking, e-commerce, transport, telecom, media, and hardware in all 27 EU member states

Technical Standard:
• ADA: WCAG 2.1 Level AA (explicitly required for Title II; de facto standard for Title III through court precedent)
• EAA: EN 301 549, which incorporates WCAG 2.1 Level AA and adds requirements for non-web products

Enforcement:
• ADA: Primarily through private lawsuits (8,667 filed in 2025) and DOJ investigations. Plaintiff-driven litigation model.
• EAA: Market surveillance authorities in each member state. Regulators proactively monitor compliance. Penalties set nationally.

Penalties:
• ADA: $75,000 first violation, $150,000 repeat (Title III). Title II: DOJ enforcement, federal funding at risk. Plus private settlement costs averaging $50,000-$125,000.
• EAA: Varies by member state. Penalties must be "effective, proportionate, and dissuasive." Can include fines, product sanctions, and suspension of local operations.

Extraterritorial Reach:
• ADA: Applies to US entities (though foreign companies operating in the US may be covered)
• EAA: Applies to any business placing covered products or services on the EU market, regardless of where headquartered

Key Takeaway: If you comply with WCAG 2.1 AA, you meet the core digital accessibility requirements of both laws. The difference is who enforces them and how.

If your US-based business has EU customers, you likely need to comply with both the ADA and the EAA. The EAA applies to any business that places covered services on the EU market — and having an e-commerce site accessible from Europe qualifies.

When the EAA Applies to You:
• You sell products or services to EU customers online
• You have an EU subsidiary or office
• Your SaaS product is used by EU organizations
• You provide banking, transport, or telecom services in the EU
• Your e-commerce platform ships to EU addresses

When It Likely Doesn't Apply:
• You only serve US customers with no EU presence
• Your website blocks EU traffic or does not offer EU shipping
• You are a microenterprise under the exemption threshold

Practical Impact for US Companies:

The good news is that WCAG 2.1 AA compliance covers both laws. If you are already working toward ADA compliance, you are simultaneously working toward EAA compliance for your digital services. The additional EAA requirements primarily affect physical products (ATMs, kiosks, hardware), not websites.

Procurement Implications: US government vendors who also serve EU public sector clients face triple compliance: ADA Title II (for US government customers), Section 508 (for US federal contracts), and EAA/EN 301 549 (for EU contracts). Again, WCAG 2.1 AA is the foundation for all three.

Action Steps for US Businesses: 1. Scan your website against WCAG 2.1 AA — this covers both ADA and EAA 2. Identify if any covered EAA services apply to your EU operations 3. Review EN 301 549 for non-web product requirements (if applicable) 4. Document your compliance efforts — both US and EU regulators value good faith

Since June 28, 2025, your organization must comply with the EAA as transposed into your member state's national law. Enforcement is active, and regulators are watching.

What You Need to Do:

Step 1: Determine if You're Covered The EAA applies to businesses providing covered products or services in the EU market. If you operate an e-commerce platform, provide banking services, sell transportation tickets online, offer telecommunications, or publish e-books, you are covered.

Step 2: Check Your Current Compliance Run a WCAG 2.1 AA compliance check on your website and web applications. This is the core technical requirement under EN 301 549. A free accessibility scan will identify violations and tell you exactly what needs fixing.

Step 3: Prioritize Remediation Focus on the most impactful violations first:
• Missing alternative text on images
• Insufficient color contrast
• Keyboard navigation failures
• Missing form labels
• Inaccessible PDF documents

These five categories account for the majority of accessibility barriers.

Step 4: Document Everything EU regulators prioritize remediation over punishment, but you need evidence of your compliance efforts. Keep dated scan reports, remediation tracking records, and accessibility policies.

Step 5: Monitor Ongoing Compliance Accessibility is not a one-time fix. Content updates, new features, and third-party integrations can introduce new violations. Establish quarterly accessibility scans as standard practice.

Member State Variations: Each EU member state has transposed the EAA into national law with its own penalty framework and enforcement authority. Check your national legislation for specific requirements and penalties. The technical standard (EN 301 549 / WCAG 2.1 AA) is consistent across all member states.

WCAG 2.1 Level AA is the technical accessibility standard that underpins virtually every major accessibility law worldwide:

• US ADA Title II (April 2026 deadline): Explicitly requires WCAG 2.1 AA
• European Accessibility Act: References EN 301 549, which incorporates WCAG 2.1 AA
• EU Web Accessibility Directive (WAD): Requires WCAG 2.1 AA for EU government websites
• Canada AODA: Aligns with WCAG 2.0 AA (updating to 2.1)
• UK Equality Act: References WCAG 2.1 AA for public sector
• Section 508 (US Federal): Revised to incorporate WCAG 2.0 AA

This convergence means that achieving WCAG 2.1 AA compliance positions your organization for compliance across multiple jurisdictions simultaneously.

What WCAG 2.1 AA Covers:
• 78 success criteria across 4 principles (Perceivable, Operable, Understandable, Robust)
• Visual accessibility (alt text, contrast, resizability)
• Keyboard and input accessibility
• Audio and video accessibility (captions, descriptions)
• Form and navigation accessibility
• Mobile accessibility (added in 2.1 vs 2.0)

What About WCAG 3.0? The W3C published a new WCAG 3.0 Working Draft in March 2026 with 174 requirements. But WCAG 3.0 is years from becoming a legal standard. Both the ADA and EAA require WCAG 2.1 AA today. Focus your compliance efforts there.

→ Learn more: WCAG 2.2 vs 2.1: What's Changed

Whether you need ADA compliance, EAA compliance, or both, the path starts the same way.

Step 1: Run a Free Accessibility Scan Scan your website against WCAG 2.1 Level AA. Our scanner checks for the most common accessibility violations and shows exactly what needs fixing. It works for any website worldwide — whether you're a US government entity, a European e-commerce business, or a multinational serving both markets.

Step 2: Review Your Violations The scan report categorizes issues by severity and WCAG success criteria. Focus on critical violations first: missing alt text, contrast failures, keyboard traps, and unlabeled forms.

Step 3: Fix and Document For each violation you fix:
• Record the date of the fix
• Note which WCAG criterion was addressed
• Save before/after evidence
• Track progress in a remediation spreadsheet

Step 4: Get Compliance Documentation Both US and EU enforcement frameworks value documented good faith effort. A compliance certificate provides formal, dated evidence of your accessibility status and remediation efforts.

Step 5: Establish Ongoing Monitoring Accessibility compliance is not a one-time achievement. Run quarterly scans, track new violations, and maintain your documentation. New content, code changes, and third-party updates can reintroduce accessibility barriers.

For Organizations Facing Both ADA and EAA: The technical work is identical. One WCAG 2.1 AA scan covers both jurisdictions. The difference is in documentation: maintain records appropriate for both US legal proceedings (if applicable) and EU market surveillance authorities.