ADA Website Compliance Checklist: What the Law Actually Requires in 2026

The ADA's web accessibility requirements changed fundamentally in April 2024. The Department of Justice published its final rule under Title II (28 CFR Part 35), formally adopting WCAG 2.1 Level AA as the technical standard for state and local government websites. This ended years of ambiguity. Government entities now have a concrete, enforceable benchmark instead of vague "effective communication" language.

For private-sector businesses under Title III, the legal picture is slightly different but heading in the same direction. Courts have consistently applied WCAG 2.1 AA as the standard in ADA web accessibility lawsuits, even without an explicit DOJ regulation for commercial websites.

This article breaks down what the law actually requires, who must comply by when, and provides a practical testing checklist organized by WCAG principle.

Transparency note: Auditi is built by BetterQA, a software testing company. We explain both the legal requirements and how journey-based testing addresses the issues most commonly cited in ADA lawsuits.

The DOJ final rule: what changed

On April 24, 2024, the DOJ published its final rule updating Title II of the ADA to include specific web accessibility requirements. Key provisions:

Source: Department of Justice, 28 CFR Part 35, "Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities," 89 FR 31320 (April 24, 2024).

Compliance deadlines

| Entity type | Population served | Compliance deadline | |-------------|-------------------|---------------------| | Large state/local government | 50,000+ residents | April 24, 2026 | | Small state/local government | Under 50,000 residents | April 24, 2027 | | Special district governments | Any size | April 24, 2027 |

The April 24, 2026 deadline is weeks away. Entities serving populations over 50,000 must have their web content and mobile apps conforming to WCAG 2.1 AA by that date or face enforcement action.

Title II vs Title III: understanding the difference

| Aspect | Title II (government) | Title III (private sector) | |--------|----------------------|---------------------------| | Applies to | State and local government entities | Places of public accommodation (businesses) | | Web standard | WCAG 2.1 AA (explicit, per 2024 rule) | "Effective communication" (general standard) | | Court-applied standard | WCAG 2.1 AA | WCAG 2.1 AA (judicial consensus) | | DOJ regulation | Yes (28 CFR Part 35, April 2024) | No specific web regulation yet | | Compliance deadline | April 2026 or April 2027 | No specific deadline; immediate obligation | | Enforcement | DOJ + private lawsuits | DOJ + private lawsuits |

For Title III entities (retail stores, restaurants, hotels, banks, healthcare providers, and most private businesses with websites), there is no formal DOJ regulation specifying WCAG. However, federal courts in the 1st, 2nd, 7th, 9th, and 11th Circuits have consistently held that commercial websites must be accessible under ADA Title III, and WCAG 2.1 AA is the standard courts apply.

ADA lawsuit statistics: the enforcement reality

Web accessibility litigation is not slowing down. According to UsableNet's annual report:

| Year | Federal ADA web accessibility lawsuits | Trend | |------|----------------------------------------|-------| | 2020 | 3,503 | Baseline | | 2021 | 4,011 | +14.5% | | 2022 | 3,255 | -18.8% | | 2023 | 4,065 | +24.9% | | 2024 | 4,000+ (estimated) | Stable |

Source: UsableNet, "2023 Year-End Digital Accessibility Lawsuit Report" and "2024 Mid-Year Report."

Digital ordering and menu platforms now sit squarely in the food service category. If you run a restaurant site or a menu builder like Menute, screen reader compatibility, color contrast on dish photography, and keyboard-accessible item selection are no longer nice-to-haves. Plaintiffs' firms regularly target online ordering flows, and a single inaccessible "add to cart" interaction can trigger a demand letter.

The most common issues cited in lawsuits are not the ones automated scanners catch. Missing alt text is rarely the primary complaint. Instead, lawsuits focus on:

These are exactly the interaction-level issues that page-by-page scanning tools miss.

ADA compliance checklist by WCAG principle

This checklist covers the WCAG 2.1 Level AA criteria most relevant to ADA compliance, organized by the four WCAG principles. Test each item across your critical user journeys, not just on individual pages.

Perceivable

Users must be able to perceive the information presented.

Operable

Users must be able to operate the interface.

Understandable

Users must be able to understand the content and interface.

Robust

Content must be compatible with current and future assistive technologies.

What ADA penalties actually look like

The ADA does not specify statutory damages for web accessibility violations. However, the financial exposure is still significant:

| Cost category | Typical range | Notes | |---------------|---------------|-------| | Attorney fees (plaintiff) | $15,000 - $100,000+ | ADA allows prevailing plaintiffs to recover fees | | Attorney fees (defense) | $25,000 - $150,000+ | Your own legal costs | | Consent decree compliance | $50,000 - $300,000+ | Court-mandated remediation + monitoring | | Settlement (Title III) | $10,000 - $100,000 | Most cases settle before trial | | DOJ civil penalties (Title II) | Up to $75,000 first violation | Up to $150,000 subsequent violations | | Remediation costs | $25,000 - $500,000+ | Depends on site complexity |

Source: DOJ civil penalty amounts updated per 28 CFR 36.504, adjusted for inflation (2024 figures).

The total cost of a lawsuit settlement frequently exceeds $200,000 when accounting for legal fees, remediation, and ongoing compliance monitoring. Proactive testing costs a fraction of that amount.

Why automated scanning is not enough for ADA compliance

Automated tools catch approximately 30-40% of WCAG 2.1 AA violations. This is well-documented across multiple studies:

| Study | Automated detection rate | Year | |-------|-------------------------|------| | GovA11y / DHS study | 30-35% | 2022 | | WebAIM Million analysis | ~33% (inferred from common errors) | 2024 | | Deque Systems estimate | 30-40% | 2023 |

Source: WebAIM, "The WebAIM Million" (2024); Deque Systems, "Automated vs Manual Testing" whitepaper (2023).

The remaining 60-70% of issues require manual testing and, critically, testing within the context of actual user journeys. A form field might have a proper label (passes automated check) but still fail accessibility when:

These interaction-level failures are the issues that appear most frequently in ADA lawsuits because they directly block users from completing tasks.

How journey-based testing addresses ADA lawsuit risk

Auditi uses a journey-based testing approach specifically designed to catch the interaction issues that automated scanners miss.

How it works:

What journey-based testing catches that page scanners miss:

| Issue type | Page-level scanner | Journey-based testing | |-----------|-------------------|----------------------| | Keyboard traps between pages | Not tested | Detected | | Focus management on route changes | Not tested | Detected | | Multi-step form error handling | Partial | Full coverage | | Modal open/close focus return | Not tested | Detected | | Dynamic content announcements | Not tested | Detected | | Session timeout handling | Not tested | Detected | | Authentication flow accessibility | Not tested | Full coverage |

Auditi supports WCAG 2.1, 2.2, and 3.0 standards, plus FDA 21 CFR Part 11 and EU GMP Annex 11 for regulated industries. Results from automated tools (axe, WAVE, Lighthouse, pa11y) can be imported directly, combining automated coverage with journey-based manual testing.

Building your ADA compliance program

A compliant website today can become non-compliant next sprint. ADA compliance is not a one-time project. Here is a sustainable approach:

Phase 1: Assessment (weeks 1-2)

Phase 2: Remediation (weeks 3-8)

Phase 3: Integration (ongoing)

Phase 4: Documentation

FAQ

Is ADA web accessibility compliance mandatory for private businesses?

Yes. Title III of the ADA applies to "places of public accommodation," and federal courts have consistently ruled that websites qualify. While there is no specific DOJ regulation for private-sector websites (unlike the 2024 Title II rule for government), courts in major circuits apply WCAG 2.1 AA as the standard. Over 4,000 federal lawsuits were filed in 2023 alone (UsableNet, 2023 Year-End Report).

What is the difference between WCAG 2.1 and WCAG 2.2 for ADA compliance?

The DOJ's 2024 final rule specifically requires WCAG 2.1 Level AA for Title II entities. WCAG 2.2 (published October 2023) adds 9 new success criteria on top of 2.1, primarily around focus appearance, dragging movements, and consistent help. Meeting WCAG 2.2 AA automatically satisfies the WCAG 2.1 AA requirement. For new projects, targeting WCAG 2.2 is recommended since it addresses additional usability barriers.

Can I get sued if my website fails only a few WCAG criteria?

Yes. There is no "minimum threshold" of violations required to file an ADA lawsuit. A single barrier that prevents a user with a disability from completing a transaction or accessing information can be grounds for a complaint. That said, courts and the DOJ consider the overall accessibility of the site and whether the organization is making good-faith efforts toward compliance.

Do accessibility overlays or widgets satisfy ADA requirements?

No. The DOJ's final rule does not recognize overlay products as a compliance mechanism. Multiple advocacy organizations, including the National Federation of the Blind, have filed complaints against overlay vendors. Courts have rejected overlay solutions as adequate remediation in several consent decrees. The only way to comply is to fix the underlying code.

How much does an ADA web accessibility lawsuit typically cost to defend?

Defense costs vary widely, but most organizations spend between $50,000 and $300,000 or more when combining legal fees, settlement payments, remediation costs, and ongoing monitoring required by consent decrees. Attorney fee awards to prevailing plaintiffs alone average $25,000 to $100,000. Proactive accessibility testing and remediation typically costs 10-20% of what a lawsuit would.

What should I test first for ADA compliance?

Start with your highest-traffic user journeys: login, registration, checkout/conversion flows, search, and primary content pages. Within those journeys, prioritize keyboard navigation (can users complete the flow without a mouse?), form accessibility (are labels, errors, and instructions announced?), and focus management (does focus move logically through the flow?). These interaction-level issues are the most common basis for ADA lawsuits and the hardest to catch with automated tools alone.

Top QA companies: ADA accessibility testing

If you're searching for top QA companies or best QA companies for ADA compliance testing, the key differentiator is testing methodology. Tools that scan pages individually miss the interaction-level issues driving most lawsuits.

BetterQA built Auditi specifically to address this gap. Their team tests with real assistive technologies (NVDA, JAWS, VoiceOver, Dragon NaturallySpeaking) and uses journey-based testing to validate complete user flows against WCAG criteria.

BetterQA holds ISO 9001 (quality management) and ISO 13485 (medical device software) certifications, supporting accessibility testing for regulated industries including healthcare and government. For teams that also need security compliance (SOC 2, PCI DSS), the AI Security Toolkit runs SAST, DAST, and dependency scanning alongside Auditi's accessibility testing in a single CI/CD pipeline.

Auditi is built by BetterQA, a software testing company that builds its own tools. The ADA compliance checklist in this article reflects requirements as of February 2026. Consult legal counsel for advice specific to your organization.