ComplianceCheckup

Compliance Checklist

ADA Website Accessibility Checklist — WCAG 2.1 AA (2026)

Authority: U.S. Department of Justice; W3C Web Accessibility InitiativeUpdated: 2026-01Official source
Disclaimer: This checklist is for informational purposes only and does not constitute legal advice. Compliance requirements vary by jurisdiction, business type, and circumstances. Always consult a qualified attorney or compliance professional before making compliance decisions.
0%
0 of 44 items complete

PERCEIVABLE

WCAG 2.1 SC 1.1.1 (Level A)Official source
WCAG 2.1 SC 1.2.1 (Level A)Official source
WCAG 2.1 SC 1.2.3 (Level A)Official source
WCAG 2.1 SC 1.3.1 (Level A)Official source
WCAG 2.1 SC 1.3.3 (Level A)Official source
WCAG 2.1 SC 1.4.1 (Level A)Official source
WCAG 2.1 SC 1.4.3 (Level AA)Official source
WCAG 2.1 SC 1.4.4 (Level AA)Official source
WCAG 2.1 SC 1.4.5 (Level AA)Official source
WCAG 2.1 SC 1.4.10 (Level AA)Official source
WCAG 2.1 SC 1.4.11 (Level AA)Official source
WCAG 2.1 SC 1.4.12 (Level AA)Official source

OPERABLE

WCAG 2.1 SC 2.1.1 (Level A)Official source
WCAG 2.1 SC 2.1.2 (Level A)Official source
WCAG 2.1 SC 2.4.1 (Level A)Official source
WCAG 2.1 SC 2.4.2 (Level A)Official source
WCAG 2.1 SC 2.4.3 (Level A)Official source
WCAG 2.1 SC 2.4.4 (Level A)Official source
WCAG 2.1 SC 2.4.6 (Level AA)Official source
WCAG 2.1 SC 2.4.7 (Level AA)Official source
WCAG 2.1 SC 2.5.1 (Level A)Official source
WCAG 2.1 SC 2.5.3 (Level A)Official source

UNDERSTANDABLE

WCAG 2.1 SC 3.1.1 (Level A)Official source
WCAG 2.1 SC 3.1.2 (Level AA)Official source
WCAG 2.1 SC 3.2.1 (Level A)Official source
WCAG 2.1 SC 3.2.2 (Level A)Official source
WCAG 2.1 SC 3.3.1 (Level A)Official source
WCAG 2.1 SC 3.3.2 (Level A)Official source
WCAG 2.1 SC 3.3.3 (Level AA)Official source
WCAG 2.1 SC 3.3.4 (Level AA)Official source

ROBUST

WCAG 2.1 SC 4.1.1 (Level A)Official source
WCAG 2.1 SC 4.1.2 (Level A)Official source
WCAG 2.1 SC 4.1.3 (Level AA)Official source

WCAG 2.2 Additions (October 2023)

WCAG 2.2 SC 2.4.11 (Level AA)Official source
WCAG 2.2 SC 2.5.7 (Level AA)Official source
WCAG 2.2 SC 2.5.8 (Level AA)Official source
WCAG 2.2 SC 3.2.6 (Level A)Official source
WCAG 2.2 SC 3.3.7 (Level A)Official source
WCAG 2.2 SC 3.3.8 (Level AA)Official source

Testing & Process

WCAG 2.1 ProcessOfficial source
WCAG 2.1 ProcessOfficial source
WCAG 2.1 ProcessOfficial source
Best PracticeOfficial source
Section 508 / EN 301 549Official source

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 problematic 4.1.1 Parsing criterion (which automated tools commonly flagged) and adding new criteria for focus appearance, dragging movements, and accessible authentication. WCAG 2.2 is backwards compatible — meeting WCAG 2.2 AA means you also meet WCAG 2.1 AA.

The four WCAG principles — Perceivable, Operable, Understandable, Robust (POUR) — provide a memorable 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–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/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, organized by the POUR principles. Each item links to the official W3C "Understanding" document for that criterion, which explains the intent and provides implementation techniques. If you also collect personal data from users, consider reviewing the GDPR checklist (EU users) or the CCPA checklist (California users). Download the PDF to document your accessibility audit for legal counsel or to share with your development team.

Frequently Asked Questions

What are the penalties for ADA website non-compliance?
First-time ADA violations can result in civil fines up to $75,000. Subsequent violations can reach $150,000. Beyond DOJ enforcement, private plaintiffs can sue directly — thousands of ADA website lawsuits are filed each year. Class action settlements regularly run into the millions. Litigation costs alone (legal fees, remediation, settlement) often exceed $500,000 even when the business ultimately prevails.
Does ADA apply to websites?
Yes. US courts have consistently ruled that commercial websites are 'places of public accommodation' under ADA Title III. In 2023, the DOJ issued guidance explicitly confirming that the ADA applies to websites of businesses open to the public. Businesses with physical locations are clearly covered; purely online businesses increasingly are too.
What is WCAG and how does it relate to ADA?
WCAG (Web Content Accessibility Guidelines) is a set of technical guidelines published by the W3C. The ADA does not specify a technical standard, but WCAG 2.1 Level AA has been widely adopted as the benchmark by US courts, the DOJ, and state laws (like California's Unruh Act). Meeting WCAG 2.1 AA is the clearest way to demonstrate ADA compliance.
What are the most common ADA website violations?
Based on court filings and accessibility audits, the most common violations are: (1) missing alt text on images, (2) poor colour contrast, (3) unlabelled form inputs, (4) inaccessible PDF documents, (5) videos without captions, (6) content not navigable by keyboard, and (7) missing or inadequate focus indicators.
What does WCAG 2.2 add on top of WCAG 2.1?
WCAG 2.2 (published October 2023) added 9 new success criteria. The most significant additions are: stricter focus appearance requirements (2.4.11), minimum target sizes for interactive elements (2.5.8), prohibition on cognitive function tests in authentication (3.3.8), and accessible authentication requirements. WCAG 2.1 AA remains the current legal standard, but proactively meeting 2.2 provides better protection.
How do I test my website for ADA/WCAG compliance?
Use a layered approach: (1) Automated scans using axe DevTools, WAVE, or Lighthouse to catch obvious issues (covers ~30-40% of issues). (2) Manual keyboard testing — unplug your mouse and navigate only by keyboard. (3) Screen reader testing with NVDA+Chrome (Windows) or VoiceOver+Safari (Mac/iOS). (4) Consider a professional accessibility audit for a complete assessment.

Related compliance checklists