The Legal Landscape of Accessibility
Accessibility Is a Legal Requirement
Accessibility is not just a moral imperative or a nice-to-have feature. It is a legal requirement in every major market. QA engineers who understand the legal landscape can frame accessibility testing as risk mitigation, not just quality improvement.
Global Regulations (2026)
| Jurisdiction | Law | Scope | Penalties | Deadline |
|---|---|---|---|---|
| United States | ADA Title III | All "places of public accommodation" (interpreted to include websites) | Lawsuits, settlements ($10K-$500K typical) | Ongoing |
| European Union | European Accessibility Act (EAA) | Products and services sold in the EU, including e-commerce, banking, media | Fines, market access denial | June 28, 2025 (now in effect) |
| European Union | EN 301 549 | Public sector websites and mobile apps | Procurement exclusion | In effect |
| Canada | AODA / ACA | Ontario + federal organizations | Fines up to $100K/day | In effect |
| UK | Equality Act 2010 | All service providers | Discrimination claims | Ongoing |
| Australia | Disability Discrimination Act | All service providers | Human Rights Commission complaints | Ongoing |
| Japan | JISX 8341-3 | Government and large enterprise | Compliance audits | In effect |
| Israel | Equal Rights for Persons with Disabilities | Websites and mobile apps | Fines, lawsuits | In effect |
The ADA Litigation Explosion
Web accessibility lawsuits in the United States have grown dramatically:
- 2016: ~262 lawsuits filed
- 2019: ~2,256 lawsuits filed
- 2022: ~3,255 lawsuits filed
- 2024: ~4,000+ lawsuits filed
- 2026: Trend continues upward, with increasing focus on mobile apps
Most Common Targets
| Industry | % of ADA Web Lawsuits | Why Targeted |
|---|---|---|
| E-commerce / Retail | ~35% | Online shopping barriers |
| Food service / Restaurants | ~15% | Menu, ordering, delivery |
| Banking / Financial | ~12% | Account management barriers |
| Entertainment / Media | ~10% | Content accessibility |
| Healthcare | ~8% | Patient portal barriers |
| Travel / Hospitality | ~7% | Booking system barriers |
Most Common Violations Cited
- Missing alt text on images
- Missing form labels
- Insufficient color contrast
- Inaccessible navigation
- Videos without captions
- Keyboard-inaccessible functionality
- Missing page language declaration
- Empty links and buttons
The European Accessibility Act (EAA)
The EAA is the most significant accessibility regulation since the ADA. It requires accessibility compliance for products and services sold in the EU, including:
- E-commerce websites and mobile apps
- Banking and financial services
- Audiovisual media services
- E-books and e-readers
- Transportation services (booking, check-in)
- Telecommunication services
Key Requirements
The EAA references EN 301 549, which in turn references WCAG 2.1 AA. This means:
- All web content must conform to WCAG 2.1 Level AA
- Mobile applications must follow similar accessibility principles
- Self-service terminals (ATMs, check-in kiosks) must be accessible
- Companies must publish accessibility statements
- Enforcement is at the EU member state level
Impact on Non-EU Companies
If you sell to EU customers, the EAA applies to you regardless of where your company is based. This has caused a wave of accessibility investment from US and Asian companies that sell into the EU market.
How to Frame Accessibility in Business Conversations
For Engineering Leadership
"Accessibility testing is cheaper to implement proactively than to remediate reactively. Running axe-core on every PR costs us nothing in CI time and prevents violations that could result in lawsuits costing $10K-$500K each."
For Product Leadership
"The EAA is now in effect. If our product is sold in the EU without WCAG 2.1 AA compliance, we risk market access denial. Our competitors are already investing in accessibility."
For Legal/Compliance
"We have automated WCAG 2.1 AA scanning in our CI pipeline that catches 30-40% of violations automatically. Here is the latest report showing our compliance posture. I recommend quarterly manual audits to cover the remaining 60% that automation cannot detect."
Building a Compliance Program
| Phase | Timeline | Activities |
|---|---|---|
| Audit | Month 1 | Automated scan of all pages, manual expert audit of critical flows |
| Remediate | Months 2-4 | Fix critical and serious violations, prioritized by user impact |
| Automate | Month 3 | Add axe-core to CI pipeline, fail builds on critical violations |
| Monitor | Ongoing | Weekly automated scans, quarterly manual audits, annual user testing |
| Document | Ongoing | Publish accessibility statement, maintain VPAT/ACR documentation |
Accessibility Statement Template
## Accessibility Statement
[Company Name] is committed to ensuring digital accessibility for people with
disabilities. We are continually improving the user experience for everyone
and applying the relevant accessibility standards.
### Conformance Status
This website conforms to WCAG 2.1 Level AA. We assess our conformance through
automated testing on every release and quarterly manual audits.
### Feedback
If you encounter an accessibility barrier, please contact us at
accessibility@company.com. We aim to respond within 2 business days.
### Compatibility
This website is designed to be compatible with:
- Current versions of JAWS, NVDA, and VoiceOver screen readers
- Current versions of Chrome, Firefox, Safari, and Edge
- Text-only browsers and screen magnification software
Last updated: [Date]
Accessibility Overlay Widgets: A Legal Trap
Many companies purchase "accessibility overlay" widgets (e.g., AccessiBe, UserWay) thinking they solve compliance. Courts and accessibility experts disagree:
- Overlays do not achieve WCAG conformance. They apply surface-level fixes (font resizing, contrast adjustments) without addressing underlying structural issues.
- Multiple lawsuits have been filed against companies using overlays. Courts have ruled that the presence of an overlay does not constitute a good-faith accessibility effort.
- The National Federation of the Blind has publicly opposed overlays, calling them "not only ineffective but harmful to accessibility."
- Overlays can interfere with actual assistive technology. Screen readers may conflict with overlay scripts, making the experience worse, not better.
The only reliable path to compliance is fixing the underlying code: semantic HTML, proper ARIA roles, keyboard accessibility, and sufficient color contrast.
Understanding the legal landscape transforms accessibility from a "nice thing to do" into a business-critical compliance requirement. Frame it that way, and budgets and priorities follow.