βΏ ADA WEBSITE COMPLIANCE
What It Is Β· Why It Matters Β· The Legal Landscape Β· What We Audit Β· What We Fix Β· How We Maintain It Β· How to Grant Us Access
Read This First:
ADA website compliance is not a design preference. It is not a feature upgrade. It is a legal requirement that is actively being enforced through litigation β and the businesses being targeted are not Fortune 500 companies. They are small and mid-size businesses exactly like yours. This document explains what the law requires, what your current exposure looks like, what we do to address it, and how we work together to protect your business. Read it completely before dismissing it.
PART 1: WHAT IS THE ADA AND WHY DOES IT APPLY TO YOUR WEBSITE?
The Americans with Disabilities Act β A Brief History
The Americans with Disabilities Act was signed into law in 1990 to ensure that people with disabilities have equal access to public life. Originally focused on physical accommodations like wheelchair ramps and Braille signage, the ADA's scope has expanded significantly in the digital age.
The Digital Extension of the ADA
Title III of the ADA prohibits discrimination in "places of public accommodation." Over the past decade, courts have consistently ruled that websites operated by businesses open to the public qualify as places of public accommodation.
The DOJ confirmed this position with official guidance in March 2022 and a landmark **Final Rule issued in March 2024**, applying **WCAG 2.1 Level AA** as the binding technical standard for state and local government websites. This sets the trajectory for all covered entities.
Who Is Affected by Inaccessible Websites?
- 26% of adults (approx. 61 million people) live with some form of disability.
- 7.6 million people have a visual disability affecting computer use.
- 19.9 million people have difficulty with physical hand/arm movements affecting keyboard use.
- 1 in 8 Americans aged 12+ has hearing loss in both ears.
Inaccessible websites actively exclude millions of potential clients from doing business with you.
PART 2: THE LEGAL LANDSCAPE β THE LAWSUIT REALITY
The Litigation Explosion
| Year | Federal Filings | Key Development |
|---|---|---|
| 2017 | ~800 | Litigation begins scaling |
| 2019 | ~2,256 | Robles v. Domino's β 9th Circuit ruling |
| 2021 | ~4,055 | Post-COVID digital acceleration |
| 2022 | ~3,255 | DOJ issues formal web accessibility guidance |
| 2024 | ~5,000+ | DOJ Title II Final Rule β WCAG 2.1 AA codified for government |
| 2025 (H1) | 2,014 | 37% increase over H1 2024 β on pace for 5,500+ |
Typical Financial Exposure
- Demand letter settlement: $5,000 β $20,000
- Average lawsuit settlement: $25,000 β $75,000
- Maximum civil penalty (1st violation): $75,000
High-Risk Industries
| Industry | Why High Risk |
|---|---|
| Healthcare / Medical / Dental | Critical access points for disabled users; high usage by patients with disabilities. |
| Fitness / Wellness | Class booking, membership purchases, facility info. |
| Restaurants | Menus, reservations, online ordering (#1 most sued industry in 2025). |
| Retail / E-commerce | Product browsing, purchasing, checkout. |
PART 3: THE TECHNICAL STANDARD β WCAG 2.2 AND WHAT IT REQUIRES
WCAG (Web Content Accessibility Guidelines) is the international standard. As of 2026, **WCAG 2.2 Level AA** is the target standard for compliance, replacing version 2.1.
The Four Core Principles (POUR)
- Perceivable: Info must be presentable to users in ways they can perceive (e.g., alt text for images, captions for video).
- Operable: Navigation must be operable (e.g., keyboard-only access, no keyboard traps).
- Understandable: Operation must be understandable (e.g., readable text, predictable navigation).
- Robust: Content must be robust enough to be interpreted by assistive technologies (e.g., proper HTML structure).
New Criteria in WCAG 2.2
| Criterion | Requirement |
|---|---|
| Focus Not Obscured | Focused elements cannot be hidden by sticky headers or popups. |
| Dragging Movements | Must have a single-pointer alternative (click/tap) for drag interactions. |
| Consistent Help | Help mechanisms (chat, contact) must appear in the same spot on every page. |
| Accessible Authentication | Logins cannot require cognitive puzzle solving; password managers must work. |
PART 4: THE MOST COMMON VIOLATIONS
According to the WebAIM Million report, **96.3% of home pages have detectable WCAG failures.**
- β Missing alt text on images (Invisible to screen readers)
- β Insufficient color contrast (Unreadable text)
- β Missing form input labels (Unusable forms)
- β Keyboard inaccessibility (Menus/modals requiring a mouse)
- β Missing "Skip to content" link
- β Videos without captions
PART 5: THE OVERLAY WIDGET PROBLEM β THE FALSE SOLUTION
Accessibility overlays (widgets like accessiBe, UserWay, AudioEye) are often marketed as "one-click compliance." **They do not work.**
Why Overlays Fail
- Technical Failure: They cannot fix underlying code issues like missing labels or improper structure.
- Interference: They often conflict with the screen readers users already have installed.
- Legal Failure: Courts have ruled overlays do not provide ADA compliance. The FTC fined accessiBe **$1 million in 2025** for false claims.
- Targeting: 456 lawsuits in H1 2025 specifically targeted sites with overlays installed.
We do not recommend or install overlays. We build real compliance through code remediation.
PART 6: WHAT WE DO β THE PROSCRIS ACCESSIBILITY PROCESS
Step 1: The Accessibility Audit
We combine Automated Scanning (axe DevTools, WAVE) with Manual Testing (Keyboard navigation, Screen Reader testing via JAWS/NVDA).
Step 2: Prioritized Remediation
- Priority 1 (Critical): Fix blockers (keyboard traps, broken forms).
- Priority 2 (Serious): Fix major barriers (color contrast, alt text).
- Priority 3 (Moderate): Enhance usability (focus indicators, ARIA labels).
Step 3: The Accessibility Statement
We write and publish a legal statement affirming your commitment to WCAG 2.2 AA standards, describing measures taken, and providing a contact mechanism for feedback.
Step 4: Maintenance & Documentation
Compliance is ongoing. We perform monthly scans, quarterly manual reviews, and maintain a Compliance Documentation File (Audit reports, remediation logs) as your legal defense record.
PART 8: GRANTING US ACCESS
We audit without login. For remediation, we require specific platform access:
- WordPress: Administrator role (via Users β Add New).
- Shopify: Staff account with Theme/Product permissions.
- Squarespace: Administrator (Invite Contributor).
- Webflow: Admin role (Invite Member).
- Wix: Co-Owner role (required for full code access).
We NEVER ask for personal Google logins, domain registrar access (unless DNS work needed), or financial data.
PART 11: THE ACCESSIBILITY STATEMENT
This statement must be linked in your footer. It confirms conformance status (WCAG 2.2 AA), assessment approach (external audit), and provides contact info for feedback.
PART 12: ONBOARDING CHECKLIST β DOCUMENT 5
- β Initial Automated & Manual Audit completed
- β Audit Report delivered & reviewed
- β Platform Access granted
- β Critical Remediation completed
- β Post-remediation verification scan
- β Accessibility Statement published
- β Compliance Documentation File created
- β Maintenance schedule confirmed
APPENDIX: KEY TERMS GLOSSARY
| Term | Definition |
|---|---|
| ADA | Americans with Disabilities Act. |
| WCAG 2.2 AA | Current technical standard for web accessibility. |
| Screen Reader | Software (JAWS, NVDA) that reads web content aloud. |
| Alt Text | Text description of images for screen readers. |
| Overlay | Ineffective third-party widget claiming automated compliance. |
| Demand Letter | Pre-litigation legal notice demanding settlement for violations. |
A Note from Proscris Agency:
ADA compliance is infrastructure. The audit tells you where you stand. The remediation fixes it. The documentation protects you. This is not overhead; it is asset protection and market expansion. The businesses that ignore this are not safe; they are simply not yet targeted.
Sources
- DOJ β Guidance on Web Accessibility and the ADA (March 2022)
- DOJ β Web Accessibility Final Rule Title II (March 2024)
- W3C β Web Content Accessibility Guidelines (WCAG) 2.2
- W3C β Understanding WCAG 2.2
- W3C β WAI-ARIA Authoring Practices
- W3C β WCAG 2.2 Summary of Changes from 2.1
- WebAIM β The WebAIM Million 2024 Annual Accessibility Report
- Ecomback β 2025 Mid-Year ADA Website Lawsuit Report
- UsableNet β ADA Web Lawsuit Trends 2026
- Accessible.org β 2026 ADA Website Compliance and AI
- AudioEye β ADA Compliance Fines and Penalties
- LFL Legal β FTC accessiBe $1M Fine
- Darrow Everett β ADA Website Accessibility Litigation 2025
- Fox Rothschild β ADA Website Lawsuit Trends 2025
- Level Access β WCAG 2.2 AA Summary and Checklist
- AllAccessible β WCAG 2.2 Complete Guide 2025
- ADA Compliance Pros β WCAG 2.2 Update
- Seyfarth Shaw β ADA Title III Litigation Report 2024
- NFB β Position Statement on Accessibility Overlays
- Overlay Fact Sheet
- Deque Systems β axe DevTools Documentation
- Robles v. Domino's Pizza LLC, 913 F.3d 898 (9th Cir. 2019)
- Return on Disability β Annual Report
- CDC β Disability and Health Data 2023
- Google β Web Accessibility Fundamentals
- CDGI β 2025 Web Accessibility Lawsuit Trends