To be ADA compliant, a website must be usable by people with disabilities — which in practice means conforming to WCAG 2.2 Level AA, the standard that courts, settlement agreements, and federal regulators reference. The core requirements: text alternatives for images, full keyboard operability, sufficient color contrast, labeled form fields, captioned video, and a page structure screen readers can navigate. This ADA website compliance checklist walks through each of those requirements in plain English, so you know exactly what to check and how to verify it.
One thing to clear up first: there is no formal federal regulation spelling out a web standard for private businesses under ADA Title III. But the Department of Justice has long held that business websites are covered, most courts agree, and WCAG is the de facto benchmark nearly every settlement points to. The legal ambiguity has not slowed the lawsuits — quite the opposite.
Why does ADA website compliance matter in 2026?
Because the litigation machine keeps accelerating. More than 5,000 digital-accessibility lawsuits were filed in 2025 — up roughly 20% over 2024 — and most cases settle for between $10,000 and $75,000, plus a binding commitment to remediate anyway. Settling never removes the fix-the-site work; it just stacks legal fees on top of it. Our breakdown of ADA website lawsuit trends for 2026 covers who is filing and which industries they target.
The exposure is wide because the failures are everywhere. WebAIM's 2025 analysis of the top one million homepages found detectable WCAG failures on 94.8% of them — mostly low-contrast text, missing alt text, missing form labels, and empty links or buttons. And the audience affected is not a rounding error: over 1 in 4 U.S. adults live with a disability, per the CDC.
The 2026 ADA website compliance checklist
The benchmark to work against is WCAG 2.2 Level AA — a W3C Recommendation since October 5, 2023, and the level courts, the DOJ's government-website rule, and the EU all reference. If your last audit cited version 2.1, review what changed in WCAG 2.2: nine new success criteria, several of which are easy to fail. Work through the checklist in order.
- Every image has appropriate alt text. Meaningful images get a short, accurate description; purely decorative images get an empty alt attribute so screen readers skip them. Missing alt text is one of the most common failures on the web.
- Text and controls meet contrast minimums. 4.5:1 for normal text, 3:1 for large text (18pt and up, or 14pt bold), and 3:1 for UI components such as buttons, icons, and form-field borders. Low-contrast text is the single most common detectable failure in WebAIM's data.
- The entire site works with a keyboard alone. Every menu, form, modal, and carousel must be reachable and operable with Tab, Enter, and arrow keys — no mouse required. A keyboard trap, where focus enters a component and cannot leave, is an automatic failure.
- Keyboard focus is always visible. Users need to see where they are on the page. WCAG 2.2 added Focus Appearance (2.4.11) precisely because so many sites suppress the focus outline for aesthetic reasons.
- Forms have real labels and clear error messages. Every field needs a programmatic label a screen reader can announce, and errors must say what went wrong and how to fix it. Missing form labels are a top-four failure — and forms are where your leads and sales happen.
- Links and buttons have descriptive names. "Learn more" repeated ten times, or an icon-only button with no accessible name, tells a screen-reader user nothing. Link text should make sense read on its own.
- Headings follow a logical order. One main heading per page, section headings beneath it, sub-points under those. Screen-reader users navigate by heading structure the way sighted users skim.
- Video has captions. Prerecorded video requires captions at Level A; live content requires them at Level AA; and prerecorded video also needs audio description at AA. Auto-captions only count if they are accurate.
- Interactions meet WCAG 2.2's newest bars. Interactive targets need a minimum size of 24x24 CSS pixels (2.5.8), any drag-only interaction needs a single-tap alternative (2.5.7), and logins cannot depend on memorizing or transcribing codes (Accessible Authentication, 3.3.8).
- You publish an accessibility statement with a feedback channel. A statement does not make a site accessible, but it documents the standard you target, your progress, and how users can report barriers — useful to real visitors and relevant in a legal dispute. See our guide to writing a website accessibility statement.
Do accessibility overlays get you off the hook?
No — and 2026 is a bad year to bet otherwise. In January 2025 the FTC announced a $1 million action against accessiBe over claims that its overlay widget could make any website WCAG-compliant; the final order bars unsubstantiated compliance claims. UsableNet's litigation reports repeatedly find hundreds of companies sued each year that already had a widget or overlay installed. The National Federation of the Blind calls overlay products "not only ineffective but harmful."
One distinction worth drawing carefully: a user-facing preference widget — contrast and text-size controls on a site that is already accessible at the code level, making no compliance claims — is a legitimate convenience. Our own site runs one. The problem is the surface-layer "compliance" overlay: a third-party script sold as making a broken site compliant. It cannot, and the lawsuit data shows plaintiffs are not deterred by it. The full comparison is in accessibility widget vs. overlay: what's the difference.
How do you verify your website actually conforms?
In two layers, because no single method covers everything. Automated scanners can detect only about a third of WCAG success criteria — they are excellent at catching contrast failures, missing alt text, and unlabeled fields at scale, but they cannot judge whether alt text is accurate, whether keyboard order makes sense, or whether a screen-reader user can complete checkout. A clean automated scan means zero detectable violations; it does not mean full conformance.
The second layer is expert human testing: keyboard-only passes, screen-reader walkthroughs of your key user journeys, and manual review of the criteria machines cannot evaluate. If you want a concrete starting point, request a free accessibility audit and we will show you exactly where your site stands against WCAG 2.2 AA — automated findings and the human-judgment gaps a scanner misses.
Then keep testing. Every deploy, template change, and new marketing page can introduce regressions, which is why ongoing monitoring belongs on the checklist rather than a one-time cleanup.
Frequently asked questions
Is WCAG 2.2 legally required for private business websites?
Not by an explicit federal regulation — Title III of the ADA has never had one for websites. The DOJ's formal web rule applies to state and local governments and adopts WCAG 2.1 AA, with compliance deadlines extended in April 2026 to April 26, 2027 for larger entities and April 26, 2028 for smaller ones. For private businesses, WCAG Level AA is the benchmark courts and settlement agreements reference, and auditing against the current version — 2.2 — is the practical way to meet every standard in play.
Can a small business be sued over its website?
Yes. ADA Title III applies to places of public accommodation regardless of company size, and serial plaintiffs routinely target small e-commerce sites precisely because they are unlikely to fight a lengthy case. In California, the Unruh Act adds minimum statutory damages of $4,000 per violation plus attorney's fees, which is why demand letters there are so common. A settlement in the typical $10,000–$75,000 range hits a small business far harder than an enterprise.
How often should a website be tested for accessibility?
Treat accessibility as a state you maintain, not a certificate you earn once. Automated monitoring should run continuously or on every release, because new content and code changes reintroduce failures — a page that passed last quarter can fail today. Pair that with periodic human re-testing of your key journeys, and a full expert audit after any redesign, re-platform, or major feature launch.
Ready to see how your site scores against this checklist? Get a free WCAG 2.2 audit from ADA Fail — we will identify the exact failures on your site, rank them by legal exposure, and show you what code-level remediation actually involves. No overlay, no upsell theater, just the list of what to fix.