EU: EAA in force since June 2025

EAA Website Accessibility Requirements

The European Accessibility Act sets specific accessibility requirements for websites and digital services. This guide breaks down what your website must do to comply, with practical steps and free scanning tools.

No signup required. Results in under 60 seconds.

WCAG 2.1 AAAI Fix SuggestionsFree, No Signup

EAA Website Requirements Overview

The European Accessibility Act (Directive 2019/882) requires that covered digital services be accessible to persons with disabilities. For websites, the requirements are defined through EN 301 549, which mandates conformance with WCAG 2.1 Level AA.

The EAA website requirements apply to specific service categories:

  • E-commerce: Product listings, shopping carts, checkout flows, order tracking, and customer accounts must all be accessible
  • Consumer banking: Account management, transfers, bill payments, loan applications, and financial information displays
  • Transport services: Route planning, ticket purchasing, seat selection, real-time departure information, and travel disruption alerts
  • Telecom services: Account management, plan selection, usage dashboards, and customer support interfaces
  • E-books: Reader interfaces, navigation, bookmarking, annotation, and content rendering

These requirements are active now — enforcement began June 28, 2025 across all EU member states.

Specific WCAG 2.1 AA Criteria Required by the EAA

WCAG 2.1 AA includes 50 success criteria organized under four principles. Here are the most commonly failed criteria that CompliScan detects:

  • 1.1.1 Non-text Content: Every image, icon, and visual element must have a text alternative that serves the same purpose
  • 1.3.1 Info and Relationships: Page structure (headings, lists, tables, forms) must be programmatically determinable, not just visually implied
  • 1.4.3 Contrast (Minimum): Text must have at least 4.5:1 contrast against its background (3:1 for large text at 18pt+ or 14pt+ bold)
  • 2.1.1 Keyboard: All functionality must be operable through a keyboard interface without requiring specific timings
  • 2.4.4 Link Purpose: The purpose of each link must be determinable from the link text alone or from its context
  • 3.3.2 Labels or Instructions: Form inputs must have labels or instructions so users know what information is expected
  • 4.1.2 Name, Role, Value: All UI components must expose their name, role, and state to assistive technologies

CompliScan scans for all 50 WCAG 2.1 AA criteria that can be tested automatically, with AI-generated fix suggestions for each violation found.

EAA vs ADA: How European Requirements Differ

If you are familiar with the Americans with Disabilities Act (ADA), understanding the EAA differences helps you adapt your compliance approach:

  • Explicit standard: The EAA explicitly references WCAG 2.1 AA through EN 301 549. The ADA does not specify a technical standard, though DOJ guidance and court rulings increasingly point to WCAG 2.1 AA
  • Defined scope: The EAA lists specific sectors that must comply (e-commerce, banking, transport, telecom, e-books). The ADA applies broadly to places of public accommodation, which courts have interpreted to include websites
  • Regulatory enforcement: The EAA is enforced by national market surveillance authorities through inspections and orders. The ADA is primarily enforced through private lawsuits and DOJ actions
  • Microenterprise exemption: The EAA exempts microenterprises providing services. The ADA has no size-based exemption
  • Product requirements: The EAA also covers physical products (self-service terminals, hardware). The ADA covers physical premises but web accessibility is handled separately

Businesses operating in both the US and EU markets should target WCAG 2.1 AA compliance to satisfy both frameworks simultaneously.

Meeting EAA Website Requirements With CompliScan

CompliScan helps you systematically address EAA website requirements through automated scanning and AI-assisted remediation:

  • Step 1 — Baseline scan: Run a free CompliScan scan to establish your current compliance level. The scan identifies violations and maps them to specific WCAG 2.1 AA success criteria
  • Step 2 — Prioritize fixes: Focus on critical and serious violations first. CompliScan ranks issues by severity and impact on user experience
  • Step 3 — Apply AI fixes: Use CompliScan's AI-generated code suggestions to fix violations. Each suggestion includes the specific HTML, CSS, or ARIA changes needed
  • Step 4 — Monitor continuously: Set up weekly or daily scans (Shield $49/mo or Shield Pro $149/mo) to catch new violations as your website content changes

For organizations managing multiple websites, the Agency plan ($299/mo) covers up to 50 sites — ideal for businesses with multiple EU-facing digital properties or agencies handling client compliance. PDF reports from Shield Pro and Agency plans serve as documentation for regulatory inquiries.

Frequently Asked Questions

What websites must comply with the EAA?

Websites providing e-commerce, consumer banking, transport services, telecommunications, and e-book services in the EU must comply. This applies to any business serving EU customers, regardless of where the business is headquartered. Microenterprises providing services (under 10 employees, under EUR 2 million turnover) are exempt.

What is the difference between EAA and Web Accessibility Directive?

The EU Web Accessibility Directive (2016/2102) applies to public sector websites and mobile apps. The European Accessibility Act (2019/882) extends accessibility requirements to private sector products and services in specific categories. The two directives are complementary — public sector bodies must comply with both, while private sector businesses in covered sectors must comply with the EAA.

Does the EAA require an accessibility statement?

The EAA itself does not mandate an accessibility statement in the same way the Web Accessibility Directive does for public sector sites. However, some EU member states have included accessibility statement requirements in their national transposition laws. Additionally, publishing an accessibility statement is considered a best practice that demonstrates your commitment to compliance.

What happens if my website is not EAA compliant?

National market surveillance authorities can order non-compliant services to be made accessible, restrict or withdraw them from the market, and impose financial penalties. The specific penalties vary by member state but must be effective, proportionate, and dissuasive. Non-compliance also creates legal risk from consumer complaints and potential litigation.

Can I use the same compliance approach for ADA and EAA?

Yes. Since both frameworks align on WCAG 2.1 AA as the target standard, a single compliance program can address both the ADA and EAA. CompliScan scans against WCAG 2.1 AA criteria, making results applicable to both US and EU compliance requirements. The key difference is enforcement: ADA through litigation, EAA through regulatory authorities.

Check Your Website Now

Enter your URL below and get a free accessibility report with AI-powered fix suggestions in under 60 seconds.

No signup required. Results in under 60 seconds.

EAA Website Requirements — Compliance Guide | CompliScan | CompliScan AI