ADA Website Accessibility Checklist — WCAG 2.1 AA (2026)

What is ADA website compliance?

The Americans with Disabilities Act (ADA) of 1990 prohibits discrimination against people with disabilities in places of public accommodation. Since the mid-2010s, US federal courts have consistently ruled that commercial websites are "places of public accommodation" under Title III. In 2024, the U.S. Department of Justice issued a final rule under Title II explicitly requiring state and local government websites to meet WCAG 2.1 Level AA, cementing this standard as the benchmark for accessibility compliance across both public and private sectors.

Any business with a public-facing website can face ADA accessibility lawsuits. The number of federal ADA website lawsuits has grown every year, exceeding 4,000 in 2023. Retail, hospitality, financial services, and healthcare are the most targeted industries, but no sector is exempt. Fines for first violations can reach $75,000, with subsequent violations up to $150,000. Beyond regulatory fines, class action litigation settlements regularly reach into the millions.

WCAG 2.1 vs WCAG 2.2 — what's the difference?

WCAG (Web Content Accessibility Guidelines) is published by the W3C's Web Accessibility Initiative (WAI). WCAG 2.1 (published June 2018) added 17 success criteria to WCAG 2.0, with particular focus on mobile accessibility and cognitive disabilities. It remains the current legal standard in most US, EU, and international jurisdictions. WCAG 2.2 (published October 2023) adds 9 new criteria, removing the 4.1.1 Parsing criterion and adding new criteria for focus appearance, dragging movements, and accessible authentication. WCAG 2.2 is backwards compatible — meeting WCAG 2.2 AA also means meeting WCAG 2.1 AA.

The four WCAG principles — Perceivable, Operable, Understandable, Robust (POUR) — provide a framework for understanding accessibility requirements. Each success criterion is assigned a level: A (minimum), AA (standard compliance target), or AAA (enhanced). ADA compliance is measured against Level AA across all four principles.

How to test for and fix accessibility issues

No single method catches all accessibility issues. Use a layered testing approach: automated tools (Google Lighthouse, axe DevTools, WAVE) identify approximately 30 to 40% of WCAG issues quickly and at no cost. Manual keyboard-only navigation testing catches interactive element issues that automated tools miss. Screen reader testing with NVDA (Windows, free), JAWS (Windows), or VoiceOver (macOS and iOS, built-in) verifies that users with visual impairments can navigate and understand your content.

This checklist covers all WCAG 2.1 AA success criteria plus the WCAG 2.2 additions, organised by the POUR principles. Each item links to the official W3C "Understanding" document. If you collect personal data from users, consider reviewing the GDPR checklist (EU users) or the CCPA checklist (California users).

What this checklist is for, and what it is not

This checklist is for US businesses operating public-facing websites that are subject to ADA Title III (private entities in places of public accommodation). WCAG 2.1 Level AA is the standard that US federal courts, the Department of Justice, and most structured settlement agreements use to define "accessible." The checklist covers all Level A and Level AA success criteria in WCAG 2.1, plus the 9 new criteria added in WCAG 2.2. It addresses what a development or design team can self-audit against in a structured review.

What it does not cover: jurisdiction-specific accessibility law outside the US (the European Accessibility Act, the UK Equality Act, and AODA in Ontario have overlapping but distinct requirements); mobile app accessibility beyond the WCAG criteria; or the technical implementation specifics for your particular framework or CMS. A website accessibility audit by a qualified auditor using manual testing and screen reader evaluation is the appropriate method for formal compliance documentation. Last verified May 2026 against WCAG 2.1 at w3.org.

Real-world ADA website enforcement cases

In January 2019, the Ninth Circuit Court of Appeals ruled in Robles v. Domino's Pizza that the ADA applies to commercial websites and mobile apps when they have a "sufficient nexus to a physical place of public accommodation." Domino's had argued that the ADA could not apply because its website was not a physical location. The court rejected this argument, and the Supreme Court declined to hear Domino's appeal in October 2019. Robles is the foundational precedent establishing that website accessibility is a legal obligation under Title III for businesses with physical locations.

The U.S. Department of Justice reached a settlement with Rite Aid Corporation in 2023 after finding that Rite Aid's pharmacy scheduling website was inaccessible to users with visual impairments. Rite Aid agreed to implement WCAG 2.1 AA compliance and pay civil penalties. The settlement explicitly named WCAG 2.1 AA as the required standard, and is one of several DOJ settlements in 2022 to 2024 doing so. The case demonstrates that accessibility obligations apply to interactive forms and scheduling tools, not only static content.

Over 4,000 ADA Title III website lawsuits were filed in US federal courts in 2023. Approximately 95% of defendants settle rather than proceed to trial. Typical settlements include injunctive relief (WCAG 2.1 AA compliance within a defined timeline), attorneys' fees (commonly $20,000 to $50,000), and in some cases statutory damages. Retail, hospitality, food service, and healthcare are the most targeted sectors, but any business with a public website can be targeted. The existence of an accessibility audit on file demonstrating good-faith remediation efforts is a relevant factor in settlement negotiations.

Common ADA website accessibility mistakes

Installing an accessibility overlay widget and assuming compliance. "Accessibility overlay" tools marketed as automatic fixes are not an adequate substitute for genuine WCAG compliance. The National Federation of the Blind, the American Council of the Blind, and numerous courts have found that overlay tools do not reliably remediate underlying code deficiencies. Multiple plaintiffs have specifically named overlay tools in ADA lawsuits. A widget does not fix keyboard navigation failures, screen reader incompatibility, or colour contrast issues in the source HTML.

Treating alt text as a checkbox rather than a contextual description. WCAG 1.1.1 (Level A) requires all non-text content to have a text alternative. Many websites add alt attributes but fill them with file names, developer comments, or generic phrases. Meaningful alt text describes the function or content of an image in context. Decorative images should have empty alt attributes (alt="") so screen readers skip them. Images of text should reproduce the text. CMS auto-generation often propagates poor alt text patterns across hundreds of pages.

Keyboard traps in modal dialogs and custom widgets. WCAG 2.1.2 (Level A) requires that keyboard users can move focus out of any component using standard keys. Modals, date pickers, carousels, and custom dropdown menus frequently trap keyboard focus, preventing users who cannot use a mouse from closing the modal or continuing navigation. This is among the most commonly identified issues in automated accessibility scans and in ADA demand letters.

What changed in ADA website compliance: 2024 to 2026

The U.S. Department of Justice published a final rule under Title II of the ADA in April 2024 (89 Fed. Reg. 31320), explicitly requiring web and mobile app accessibility for state and local government entities. The rule adopts WCAG 2.1 AA as the technical standard. Compliance deadlines vary by entity size: large entities (population 50,000 or more) must comply by April 2026; smaller entities by April 2027. While the rule applies to Title II (government), it cements WCAG 2.1 AA as the DOJ's preferred standard and strongly signals enforcement direction under Title III (private sector) as well.

W3C published WCAG 2.2 in October 2023, adding 9 new success criteria and removing SC 4.1.1 (Parsing). New criteria at Level AA include Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), Target Size Minimum (2.5.8), Consistent Help (3.2.6), and Accessible Authentication (Minimum) (3.3.8). WCAG 2.2 is backwards compatible with 2.1. Many US court settlements and DOJ guidance reference WCAG 2.1 AA specifically; transitioning to 2.2 AA is advisable for forward compatibility.

The European Accessibility Act (Directive 2019/882) required EU member states to apply product and service accessibility requirements from June 28, 2025. This applies to websites and apps offering services in the EU, including businesses based outside the EU. EN 301 549 is the harmonised European accessibility standard, which references WCAG 2.1 AA. If your website operates in the EU, both ADA (for US users) and the EAA (for EU users) may apply. Last reviewed May 2026 by the Zeta Solutions editorial team.