Global eCommerce Accessibility Laws: EAA, ADA, and AODA

Digital accessibility is no longer optional for eCommerce businesses — it is a legal requirement in most major markets. An estimated 1.3 billion people globally live with some form of disability. In the US alone, people with disabilities represent a combined purchasing power of $490 billion annually. Beyond the business case, accessibility is increasingly a legal obligation enforced through litigation, regulatory action, and substantial penalties.

This guide covers the major global accessibility laws affecting eCommerce — the EU European Accessibility Act (EAA), the US Americans with Disabilities Act (ADA), Canada's Accessibility for Ontarians with Disabilities Act (AODA), and the UK Equality Act — along with the WCAG technical standards that underpin all of them, practical implementation requirements, and compliance roadmaps.

Key Takeaways

• The EU EAA requires eCommerce services to meet WCAG 2.1 AA by June 28, 2025 — enforcement is now active across EU member states
• US ADA Title III has been interpreted by courts to require website accessibility for businesses serving the public; over 4,600 federal ADA web accessibility lawsuits filed in 2023
• Canada's AODA requires WCAG 2.0 AA for websites of Ontario-based organisations with 50+ employees
• WCAG 2.2 (published September 2023) added nine new success criteria — the gold standard for accessibility compliance
• The EU Web Accessibility Directive (2016/2102) applies to public sector websites; the EAA extends obligations to private sector eCommerce
• Common eCommerce accessibility failures: missing alt text, inaccessible checkout forms, keyboard navigation gaps, poor colour contrast, and missing captions on video
• Accessibility overlays (single-line JavaScript solutions) do not achieve legal compliance and are increasingly cited as non-compliant by regulators and courts
• Automated testing catches only 30–40% of accessibility issues — manual testing with assistive technologies is required

---

The Global Accessibility Legal Landscape

EU European Accessibility Act (EAA)

The European Accessibility Act (Directive 2019/882) is the most significant development in global accessibility law for eCommerce. It requires a wide range of digital products and services to meet accessibility requirements by June 28, 2025. Member states transposed the directive into national law by June 28, 2022, with the compliance deadline for service providers on June 28, 2025.

EAA scope for eCommerce:

• Consumer products with digital components (computers, smartphones, payment terminals, ATMs, ticketing machines)
• Electronic communications services
• Access to audio-visual media services
• E-commerce services — the direct sale of products and services through websites, mobile applications, and other electronic means
• Banking services accessible to consumers
• E-books and dedicated software
• Passenger transport services

What "accessible eCommerce" means under EAA:

• Websites and mobile apps must be perceivable, operable, understandable, and robust (POUR principles — the WCAG framework)
• Products, services, and information must be accessible to persons with disabilities
• Payment and checkout processes must be accessible
• Customer support must be accessible through multiple channels

Enforcement: Each EU member state designates a market surveillance authority responsible for EAA enforcement. Penalties vary by member state but can include fines and mandatory remediation orders. Member states must ensure effective, proportionate, and dissuasive penalties.

Disproportionate burden exception: Service providers (not microenterprises defined as fewer than 10 employees and under €2 million turnover) can claim a disproportionate burden exemption if compliance would require excessive resources. However, the exemption requires documentation and is subject to regulatory review.

US Americans with Disabilities Act (ADA)

Title III of the ADA (42 U.S.C. § 12181 et seq.) prohibits discrimination by places of public accommodation on the basis of disability. Courts have consistently held that websites of businesses that serve the public qualify as places of public accommodation subject to ADA Title III.

Current legal landscape:

• No specific web accessibility regulation exists — ADA was enacted in 1990 before the modern internet
• DOJ published final rule on March 18, 2024 requiring state and local governments to meet WCAG 2.1 AA
• For private businesses, ADA Title III web accessibility obligations are enforced through litigation
• Over 4,600 federal ADA web accessibility lawsuits filed in 2023 — targeting eCommerce, hospitality, healthcare, financial services
• Serial plaintiffs and plaintiff law firms have developed systematic testing methodologies targeting WCAG failures

DOJ Guidance (2022, 2024): The Department of Justice has made clear that website accessibility is required under ADA Title III. While no final rule exists for private businesses equivalent to the 2024 government rule, the DOJ has filed amicus briefs supporting plaintiffs' positions that websites must be accessible.

Settlement patterns: Most ADA web accessibility cases settle for $10,000–$100,000+ plus attorney's fees ($50,000–$200,000) and remediation commitment. Serial plaintiffs often target small and medium businesses. Class action risk exists for large eCommerce platforms with systematic accessibility failures.

California Unruh Civil Rights Act

California's Unruh Act (Civil Code § 51) prohibits discrimination by business establishments and incorporates ADA requirements. Provides statutory damages of $4,000 per violation (per visit by a person with a disability who encounters an accessibility barrier). California has higher accessibility litigation rates than any other state.

Canada: AODA and Federal PTAS

Ontario Accessibility for Ontarians with Disabilities Act (AODA): Applies to Ontario-based organisations with 50+ employees. Requires WCAG 2.0 Level AA for websites and web content. Deadlines: public sector by 2012; large private sector (50+ employees) by 2021.

Federal: Accessible Canada Act (ACA): Applies to federally regulated entities (federal government, banks, telecoms, airlines, broadcasters). Requires accessibility plans, progress reports, and feedback processes. The CRTC and other regulators issue sector-specific accessibility standards.

UK Equality Act 2010

Section 29 of the UK Equality Act requires service providers to make reasonable adjustments for disabled customers. The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 implement the EU Web Accessibility Directive for UK public sector websites (WCAG 2.1 AA standard). Private sector eCommerce faces obligations under the general Equality Act reasonable adjustment duty — courts have found WCAG compliance to be a relevant benchmark.

---

WCAG: The Technical Standard

The Web Content Accessibility Guidelines (WCAG) developed by the W3C Web Accessibility Initiative (WAI) are the technical reference for virtually all global accessibility laws and regulations. Understanding WCAG is essential for compliance.

WCAG Structure: POUR Principles

All WCAG success criteria fall under four principles:

Perceivable: Information and UI components must be presentable to users in ways they can perceive:

• Text alternatives for non-text content (images, icons, buttons)
• Captions and audio descriptions for video
• Adaptable content that can be presented in different ways
• Content distinguishable (contrast, audio control)

Operable: UI components and navigation must be operable:

• All functionality available from keyboard (no mouse required)
• Users have enough time to read and use content
• Content does not cause seizures or physical reactions
• Users can navigate and find content
• Input modalities beyond keyboard supported (touch, voice)

Understandable: Information and operation of UI must be understandable:

• Text readable and understandable
• Content appears and operates in predictable ways
• Users helped to avoid and correct mistakes

Robust: Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.

WCAG Conformance Levels

Level A: Minimum accessibility — basic barrier removal. Non-conformance at Level A means some users cannot access content at all.

Level AA: Standard legal requirement in most jurisdictions. Addresses the most common accessibility barriers. Required by EAA, ADA (case law and DOJ guidance), AODA.

Level AAA: Enhanced accessibility — not required by law for entire sites but elements may be required by some regulations.

WCAG 2.2 New Criteria (September 2023)

WCAG 2.2 added nine success criteria, several highly relevant to eCommerce:

• 2.4.11 Focus Not Obscured (Minimum) (AA): Keyboard focus indicator is not entirely hidden by sticky headers or cookie banners
• 2.4.12 Focus Not Obscured (Enhanced) (AAA): Focus indicator fully visible
• 2.4.13 Focus Appearance (AAA): Focus indicator has minimum contrast and size
• 2.5.7 Dragging Movements (AA): All drag-and-drop operations have single-pointer alternative
• 2.5.8 Target Size (Minimum) (AA): Touch targets minimum 24×24 CSS pixels
• 3.2.6 Consistent Help (A): Help mechanisms (chat, FAQ, contact info) appear in consistent location across pages
• 3.3.7 Redundant Entry (A): Information entered in multi-step process does not need re-entry
• 3.3.8 Accessible Authentication (Minimum) (AA): No cognitive function tests in authentication (CAPTCHAs must have accessible alternative)
• 3.3.9 Accessible Authentication (Enhanced) (AAA): No cognitive function tests at all

---

eCommerce-Specific Accessibility Requirements

Product Pages

• All product images require meaningful alt text describing what they show
• Product zoom functionality must be keyboard accessible
• Size charts and comparison tables must have proper table headers
• Video product demonstrations require captions and audio descriptions
• Colour swatches cannot be the only way to differentiate product variants — text labels required

Navigation and Search

• Site navigation must be fully keyboard accessible
• Skip navigation links to bypass repetitive menus
• Search functionality accessible by keyboard
• Autocomplete suggestions announced to screen readers
• Filter and sort controls fully accessible

Shopping Cart and Checkout

• Form labels explicitly associated with inputs (not just placeholder text)
• Error messages descriptive and associated with the relevant field
• All form controls keyboard accessible
• CAPTCHA must have an accessible alternative (audio CAPTCHA, logic question)
• Payment form inputs labelled correctly for autofill (autocomplete attributes)
• Session timeout warnings announced to screen readers with option to extend
• Order confirmation accessible to screen readers

Product Reviews and User-Generated Content

• Star ratings have text equivalents announced by screen readers
• Review forms accessible
• User-uploaded images in reviews need alt text provisions

---

Common eCommerce Accessibility Failures

The following issues account for the majority of ADA web accessibility lawsuits and EAA enforcement findings:

---

Testing for Accessibility

Automated Testing

Automated tools catch approximately 30–40% of WCAG success criteria violations. Use them as a first filter, not as a complete solution.

Recommended automated tools:

• axe DevTools (Deque Systems) — browser extension and CI/CD integration
• WAVE (WebAIM) — browser extension, visual overlay of accessibility issues
• Lighthouse (Google) — built into Chrome DevTools, accessibility audit
• IBM Equal Access Checker — automated WCAG checking

CI/CD integration: Integrate automated accessibility testing into your deployment pipeline. axe-core and pa11y can be run in automated test suites, failing builds when new accessibility violations are introduced.

Manual Testing

Manual testing is required to catch the issues automated tools miss (approximately 60–70% of real-world failures):

Keyboard navigation testing: Navigate your entire checkout flow using only Tab, Shift+Tab, Enter, Space, and arrow keys. No step should require a mouse.

Screen reader testing:

• NVDA + Firefox (Windows, free): Most common combination in accessibility lawsuits
• JAWS + Chrome (Windows, commercial): Enterprise standard
• VoiceOver + Safari (macOS/iOS, built-in): Required for iOS testing
• TalkBack + Chrome (Android, built-in): Required for Android testing

Colour contrast testing: Use a colour contrast analyser tool to verify all text meets 4.5:1 (normal text) or 3:1 (large text, UI components) ratios.

Zoom testing: Zoom to 400% and verify content remains usable without horizontal scrolling on a 1280px viewport (WCAG 1.4.10 Reflow).

Cognitive accessibility testing: Review content for plain language, clear instructions, and error recovery. Test with users with cognitive disabilities where possible.

---

Accessibility Overlays: Why They Do Not Work

Accessibility overlays — JavaScript libraries that claim to make websites accessible through a single code snippet — are ineffective and potentially increase legal exposure. Key problems:

1. They do not fix underlying code: Overlays attempt to patch inaccessible HTML after page load. Screen readers interpret the underlying HTML first; overlay modifications often fail to reach assistive technologies correctly.

2. Screen reader conflicts: Overlays frequently conflict with native assistive technologies, making pages less accessible for screen reader users.

3. Courts and regulators reject them: Multiple ADA lawsuits have proceeded (and been won by plaintiffs) even where defendants used accessibility overlays. The National Federation of the Blind and other disability organisations have formally opposed overlays.

4. Overlay providers' own claims: The limitations described above are why overlay providers include disclaimers stating that their products are intended to supplement, not replace, manual accessibility work.

The only reliable path to compliance is fixing the underlying code to meet WCAG 2.1/2.2 AA standards.

---

eCommerce Accessibility Compliance Checklist

• WCAG 2.2 Level AA audit completed (automated + manual)
• All product images have meaningful alt text
• All form inputs have explicit, associated labels
• Entire checkout flow navigable by keyboard
• No keyboard traps in any modal or dialog
• All video content has captions (auto-generated captions verified for accuracy)
• Colour contrast meets 4.5:1 for text, 3:1 for UI components
• CAPTCHA has accessible alternative (audio, logic question)
• Session timeout provides accessible warning with extension option
• Cookie consent banner keyboard accessible
• Skip navigation link implemented
• Responsive design maintains accessibility at 400% zoom
• Mobile touch targets meet minimum 24×24px (WCAG 2.5.8)
• Focus visible and not obscured by sticky elements (WCAG 2.4.11)
• Screen reader testing completed with NVDA + Firefox
• EAA compliance assessment completed for EU market
• Accessibility statement published on website
• Accessibility remediation plan and timeline documented

---

Frequently Asked Questions

When did the EU European Accessibility Act take effect for eCommerce?

The EU EAA compliance deadline for eCommerce services was June 28, 2025. Services that were in operation before that date had until June 28, 2030 to comply (with conditions). New services and significant updates to existing services must comply immediately. Member states designated their market surveillance authorities in 2025 and enforcement actions are expected to increase throughout 2026. Microenterprises (fewer than 10 employees, under €2 million turnover) have a disproportionate burden exception, but must still work toward accessibility.

Is my US eCommerce website required to be ADA accessible?

Courts have consistently held that websites of businesses open to the public are places of public accommodation subject to ADA Title III. While there is no final DOJ regulation specifying technical requirements for private sector websites, WCAG 2.1 AA is universally referenced as the appropriate standard. With over 4,600 ADA web accessibility lawsuits filed in 2023, the litigation risk is real regardless of your state. Proactive WCAG 2.1 AA compliance is the only reliable litigation defense.

What is the minimum colour contrast ratio required by WCAG?

WCAG 2.1/2.2 Level AA requires: (1) Normal text (below 18pt, or below 14pt bold): minimum 4.5:1 contrast ratio against background; (2) Large text (18pt+ or 14pt+ bold): minimum 3:1 contrast ratio; (3) Non-text UI components and graphical objects: minimum 3:1 contrast ratio against adjacent colours. Level AAA requires 7:1 for normal text and 4.5:1 for large text. Use a tool like the WebAIM Contrast Checker or browser DevTools accessibility auditor to verify.

Do we need to make our mobile app accessible too?

Yes. The EAA explicitly covers mobile applications. ADA case law is extending to mobile apps. WCAG 2.1 applies to mobile web content. For native iOS and Android apps, platform-specific accessibility guidelines apply: Apple Human Interface Guidelines (accessibility) and Android Accessibility. The core principles (perceivable, operable, understandable, robust) apply equally to mobile. Screen reader testing on VoiceOver (iOS) and TalkBack (Android) is essential.

How long does it take to make an eCommerce site WCAG 2.1 AA compliant?

Timeline depends heavily on the current state of the site. A Shopify store using a modern, well-maintained theme may need minor adjustments over 2–4 weeks. A large custom eCommerce platform with legacy HTML and third-party integrations may require 3–6 months of development work. Start with a comprehensive WCAG audit to understand your baseline, then prioritise barriers that affect the most users (keyboard accessibility, alt text, form labels, checkout flow) before addressing lower-frequency issues. Integrate accessibility into your development workflow to prevent regression.

Does an accessibility statement help with legal compliance?

An accessibility statement demonstrates good faith effort and transparency — it documents your compliance status, known issues, remediation timeline, and contact information for accessibility feedback. The EAA requires providers to publish an accessibility statement. Under ADA, courts consider evidence of good faith effort in determining damages. An accessibility statement alone is not a legal defence, but it is a best practice that signals commitment to accessibility and provides users with a mechanism to report barriers.

---

Next Steps

eCommerce accessibility is both a legal obligation and a business opportunity. Accessible websites reach a broader audience, perform better in SEO (many accessibility principles align with search engine requirements), and provide a better experience for all users — including those using mobile devices in challenging conditions.

ECOSIRE's Shopify implementation team builds accessibility-first eCommerce experiences that meet WCAG 2.1 AA standards from the ground up. Whether you are launching a new store or remediating an existing one, our team can help you achieve and maintain compliance.

Get started: ECOSIRE Shopify Services

Disclaimer: This guide is for informational purposes only and does not constitute legal advice. Accessibility law requirements vary by jurisdiction and are subject to change through legislation and court decisions. Consult qualified legal counsel for advice specific to your organisation.