Blog

Global Accessibility Regulation Timeline: EAA, ADA, AODA Compliance Dates

TestParty
TestParty
March 19, 2025

Digital accessibility regulations are expanding worldwide. Organizations operating across borders face a complex landscape of requirements, deadlines, and enforcement mechanisms. Understanding this global regulatory environment helps organizations build compliance programs that satisfy multiple jurisdictions efficiently.

This guide provides a comprehensive timeline of accessibility regulations globally, focusing on key compliance dates and requirements for organizations operating internationally.


Regulatory Landscape Overview

Convergence on WCAG

Despite regulatory differences, global accessibility requirements increasingly converge on the Web Content Accessibility Guidelines (WCAG) as the technical standard:

  • WCAG 2.0 Level AA: Baseline for most current regulations
  • WCAG 2.1 Level AA: Referenced by newer regulations
  • WCAG 2.2 Level AA: Emerging as the recommended target

This convergence simplifies compliance—achieving WCAG 2.2 Level AA generally satisfies requirements across jurisdictions.

Enforcement Mechanisms

Regulations differ in enforcement:

Private Litigation (US Model): Individuals can sue organizations directly. Creates litigation risk but inconsistent enforcement.

Regulatory Enforcement (EU Model): Government agencies monitor and enforce. More systematic but potentially slower.

Complaint-Based (Hybrid): Government investigates complaints. Balances private rights with regulatory oversight.


United States

Americans with Disabilities Act (ADA)

Effective: 1990 (web application evolved through case law)

Scope:

  • Title III: Public accommodations (private businesses)
  • Title II: State and local government

Technical Standard: No formal technical standard specified in statute, but courts consistently reference WCAG. DOJ guidance confirms WCAG 2.1 Level AA as appropriate standard.

Enforcement: Private litigation under Title III; DOJ enforcement and private action under Title II.

Current Status:

  • Active litigation environment with thousands of annual website lawsuits
  • 2024 DOJ rule codifies WCAG 2.1 AA for state/local government web content
  • Private sector remains under case-law-driven enforcement

Key Dates:

  • Ongoing: ADA applies to websites now; no future effective date
  • April 2026: DOJ Title II rule compliance deadline for larger government entities
  • April 2027: DOJ Title II rule compliance deadline for smaller government entities

For detailed litigation trends, see our ADA Lawsuit Statistics.

Section 508 (Rehabilitation Act)

Effective: 1998 (refreshed 2017)

Scope:

  • Federal agencies
  • Federal contractors (for delivered products/services)
  • Organizations receiving federal funding

Technical Standard: WCAG 2.0 Level A and AA (via ICT Standards refresh)

Enforcement: Administrative complaints, procurement requirements, potential contract issues.

Key Dates:

  • Current: Section 508 applies now
  • Ongoing: Procurement requirements include accessibility

For implementation guidance, see our Section 508 Checklist.

State Laws

California (Unruh Act): Applies civil rights protections to websites; $4,000+ minimum statutory damages incentivize state court filings.

New York: New York Human Rights Law provides additional accessibility protections.

Other States: Various states have or are developing accessibility requirements.


European Union

European Accessibility Act (EAA)

Effective: June 28, 2025

Scope: Private sector products and services including:

  • E-commerce websites and apps
  • Banking services
  • Electronic communications
  • Transport services
  • E-books and e-readers
  • Audiovisual media services

Technical Standard: EN 301 549 (which incorporates WCAG 2.1 Level AA for web content)

Enforcement: Member state implementation varies; includes market surveillance, complaints, and penalties.

Key Dates:

  • June 28, 2025: Compliance deadline for new products/services
  • June 28, 2030: Extended transition for existing products/services (with limitations)

Geographic Scope: 27 EU member states. Organizations selling to EU customers must comply regardless of headquarters location.

Exemptions: Microenterprises (fewer than 10 employees and less than €2 million turnover) partially exempt for services.

Web Accessibility Directive (WAD)

Effective: September 2018 (deadlines varied by content type)

Scope:

  • Public sector bodies in EU member states
  • Public sector websites and mobile applications

Technical Standard: EN 301 549 (WCAG 2.1 Level AA for web content)

Key Dates:

  • September 23, 2019: New websites compliant
  • September 23, 2020: All websites compliant
  • June 23, 2021: Mobile applications compliant

Current Status: In effect; monitoring and enforcement ongoing.


United Kingdom

Equality Act 2010

Effective: 2010

Scope: Organizations providing goods, services, or facilities to the public.

Technical Standard: No specific standard mandated; WCAG widely referenced as best practice.

Enforcement: Equality and Human Rights Commission; discrimination claims through employment tribunals and courts.

Public Sector Bodies Accessibility Regulations

Effective: September 2018 (UK implementation of EU WAD; retained post-Brexit)

Scope: Public sector bodies including government, education, healthcare.

Technical Standard: WCAG 2.1 Level AA

Key Dates:

  • Current: Requirements in effect for public sector

Canada

Accessible Canada Act (ACA)

Effective: July 2019

Scope:

  • Federal government
  • Federally regulated organizations (banks, telecommunications, transportation)

Technical Standard: WCAG 2.1 referenced in guidance; specific technical standards still developing.

Enforcement: Accessibility Commissioner, Canadian Human Rights Commission.

Key Dates:

  • Current: Framework established, standards developing
  • 2040: Government target for barrier-free Canada

Accessibility for Ontarians with Disabilities Act (AODA)

Effective: 2005 (web requirements phased in)

Scope:

  • Ontario private sector (50+ employees)
  • Ontario public sector

Technical Standard: WCAG 2.0 Level AA

Key Dates:

  • January 1, 2021: All public websites WCAG 2.0 AA compliant
  • Current: Enforcement and compliance ongoing

Other Provincial Laws

Manitoba: Accessibility for Manitobans Act Nova Scotia: Nova Scotia Accessibility Act British Columbia: Accessible British Columbia Act


Australia

Disability Discrimination Act (DDA)

Effective: 1992

Scope: Organizations providing goods, services, or facilities.

Technical Standard: WCAG 2.0 referenced in guidance; WCAG 2.1 increasingly expected.

Enforcement: Australian Human Rights Commission complaints; Federal Court proceedings.

Notable Cases: Early landmark cases established web accessibility requirements under Australian law.


Other Key Jurisdictions

Japan

Act on the Elimination of Discrimination Against Persons with Disabilities JIS X 8341-3 (based on WCAG) Government websites required; private sector encouraged.

Israel

Equal Rights for Persons with Disabilities Law Mandatory web accessibility requirements for various organization types.

South Korea

Act on Promotion of Information and Communications Network Utilization Web accessibility requirements with WCAG alignment.

Brazil

Lei Brasileira de InclusĂŁo (LBI) Accessibility requirements for websites of government and public interest.

India

Rights of Persons with Disabilities Act Government websites required; private sector evolving.


Compliance Timeline Summary

Immediate Requirements (Now)

| Jurisdiction  | Regulation  | Scope          | Standard     |
|---------------|-------------|----------------|--------------|
| United States | ADA         | Private sector | WCAG 2.1 AA  |
| United States | Section 508 | Federal        | WCAG 2.0 AA  |
| EU            | WAD         | Public sector  | WCAG 2.1 AA  |
| UK            | PSBAR       | Public sector  | WCAG 2.1 AA  |
| Canada        | AODA        | Ontario        | WCAG 2.0 AA  |
| Australia     | DDA         | All sectors    | WCAG 2.0+ AA |

2025 Deadlines

| Date          | Regulation | Requirement                      |
|---------------|------------|----------------------------------|
| June 28, 2025 | EU EAA     | Private sector products/services |

2026-2027 Deadlines

| Date       | Regulation      | Requirement                    |
|------------|-----------------|--------------------------------|
| April 2026 | US DOJ Title II | Larger state/local government  |
| April 2027 | US DOJ Title II | Smaller state/local government |

2030 Extended Transitions

| Date          | Regulation | Requirement                |
|---------------|------------|----------------------------|
| June 28, 2030 | EU EAA     | Existing products/services |

Q&A: Global Accessibility Compliance

Q: If we're compliant in the US, are we compliant in Europe?

A: Mostly, but not automatically. Both reference WCAG, but at different versions. US litigation typically references WCAG 2.1; EU EAA references EN 301 549 (incorporating WCAG 2.1). Achieving WCAG 2.2 Level AA covers both adequately. However, EAA has specific requirements beyond web content (products, services) that ADA litigation doesn't typically address.

Q: Does the European Accessibility Act apply to non-EU companies?

A: Yes, if you offer products or services to EU customers. The EAA applies based on market access, not company headquarters. E-commerce sites selling to EU customers must comply regardless of where the company is based.

Q: Which WCAG version should we target for global compliance?

A: Target WCAG 2.2 Level AA. This exceeds current regulatory minimums (most reference WCAG 2.0 or 2.1) and provides buffer for regulatory evolution. It's backward compatible—meeting 2.2 means meeting 2.1 and 2.0. See our WCAG 2.2 vs 2.1 Comparison.

Q: How should we prioritize if we operate in multiple jurisdictions?

A: Focus on WCAG 2.2 Level AA as the unified target—this satisfies most jurisdictional requirements. Then address any jurisdiction-specific documentation requirements (accessibility statements, conformance reports). Consider litigation risk when prioritizing—US private litigation creates more immediate pressure than many other enforcement mechanisms.


Building a Multi-Jurisdictional Program

Unified Technical Standard

Adopt WCAG 2.2 Level AA as organizational standard:

  • Meets or exceeds all major regulatory requirements
  • Simplifies compliance across jurisdictions
  • Future-proofs against regulatory evolution
  • Single standard for development teams

Documentation by Jurisdiction

Different regions require different documentation:

US:

  • Accessibility statement (recommended)
  • VPAT/ACR for B2B/government sales
  • Litigation response documentation

EU:

  • Accessibility statement (required)
  • Conformity assessment documentation
  • EN 301 549 mapping

Other Regions:

  • Jurisdiction-specific statements as required
  • Local language accessibility information

Monitoring for Regulatory Change

Track:

  • New legislation proposals
  • Regulatory guidance updates
  • Enforcement trends
  • Standard version updates

Update:

  • Internal standards as regulations evolve
  • Documentation for new requirements
  • Training on regulatory changes

Compliance Strategy

For US-Only Organizations

  1. Address ADA litigation risk through WCAG 2.2 AA compliance
  2. Prepare for Title II rule if government entity or contractor
  3. Maintain Section 508 compliance if federal involvement
  4. Monitor state-level developments

For Organizations Expanding to EU

  1. Assess EAA applicability based on products/services offered
  2. Achieve WCAG 2.2 AA (covers both US and EU)
  3. Prepare EU-required documentation
  4. Consider EN 301 549 requirements beyond web content
  5. Plan for June 2025 deadline

For Global Organizations

  1. Establish WCAG 2.2 AA as global standard
  2. Map jurisdiction-specific requirements
  3. Create localized accessibility statements
  4. Build compliance monitoring across regions
  5. Develop response procedures by jurisdiction

Taking Action

Global accessibility regulations are expanding and converging. Organizations should:

  1. Assess current compliance against WCAG 2.2 Level AA
  2. Identify applicable regulations based on operations and markets
  3. Create unified compliance program satisfying multiple jurisdictions
  4. Prepare required documentation for each region
  5. Monitor regulatory evolution and adjust programs accordingly

Schedule a TestParty demo and get a 14-day compliance implementation plan.


Stay informed

Accessibility insights delivered
straight to your inbox.

Contact Us

Automate the software work for accessibility compliance, end-to-end.

Empowering businesses with seamless digital accessibility solutions—simple, inclusive, effective.

Book a Demo