What is the ADA, and does it apply to websites?
The Americans with Disabilities Act (1990) is the US civil rights law prohibiting discrimination on the basis of disability. Title III requires "places of public accommodation" to provide equal access to goods and services - and for years the open question was whether a website counts. That question is functionally closed: the Department of Justice has repeatedly stated the ADA applies to web content, thousands of lawsuits and settlements have proceeded on that basis, and no business has a reliable defense built on "the internet does not count".
Two parts of the law matter for the web:
- Title II - state and local government. Now under an explicit DOJ rule: WCAG 2.1 Level AA, with compliance dates of 26 April 2027 (larger entities) and 26 April 2028 (smaller ones).
- Title III - private businesses open to the public: shops, banks, restaurants, clinics, hotels, and their websites. No named technical standard - which is exactly why WCAG AA became the de facto one.
What makes a website ADA compliant? WCAG.
Because the ADA text predates the web, compliance is measured through WCAG - the standard courts cite in settlements, the DOJ references in rules and agreements, and every serious demand letter names. In practice, "ADA compliant website" means:
- Conformance with WCAG 2.1 Level AA (building to 2.2 AA covers it and the next regulatory update) - all 50 Level A and AA success criteria on your real pages;
- Including your documents: statements, forms and menus served as PDFs are part of the service - see WCAG for PDFs;
- With evidence: a dated audit and remediation trail, because in a dispute the question is never "do you feel accessible" but "show us the testing".
A word on risk: over 5,000 web accessibility lawsuits were filed in the US in 2025, and more than a quarter of the sued sites had an accessibility widget installed. Tools help - they do not, by themselves, constitute WCAG compliance.
The 5-step path to an ADA-compliant website
- Understand your exposure. Which title applies to you, which state law adds to it (California's Unruh Act attaches damages per visit), and which of your properties and documents are in scope.
- Audit against WCAG. An automated scan (free checker per page, crawler for the site) finds the machine-detectable third; certified auditors cover the rest, criterion by criterion.
- Remediate: code first, then the visitor layer. Fix templates and components at the source, guided by the per-criterion fix instructions in the criteria library; add an accessibility widget so visitors get assistive functions on every page.
- Test with people and document. Keyboard-only and screen reader passes on your critical flows, and the result written down - an audit report or VPAT - plus a public accessibility statement.
- Monitor continuously. Sites change weekly and compliance decays silently; monitoring plus periodic re-audit keeps the evidence current.
The 15-point ADA compliance checklist
Work through these and you have covered the failures behind the vast majority of ADA web claims:
- Every image has meaningful alt text; decorative images are marked decorative (1.1.1)
- Body text meets 4.5:1 contrast; controls and icons meet 3:1 (1.4.3, 1.4.11)
- The whole site works with a keyboard alone - no traps, visible focus (2.1.1, 2.4.7)
- Headings are real and hierarchical; landmarks structure every page (1.3.1)
- Every form field has a visible, programmatic label; errors say what to fix (3.3.2, 3.3.1)
- Links describe their destination - no bare "click here" (2.4.4)
- Videos have captions; audio has transcripts (1.2.2)
- Nothing conveys meaning by color alone (1.4.1)
- The page reflows at 320px / 400% zoom without horizontal scrolling (1.4.10)
- Carousels and animations can be paused; nothing flashes (2.2.2, 2.3.1)
- Every page has a language attribute and a unique descriptive title (3.1.1, 2.4.2)
- Custom components expose name, role and state; updates are announced (4.1.2, 4.1.3)
- Your PDFs are tagged, titled and readable - test them like pages (WCAG applies to documents)
- An accessibility statement is published, with a working contact route for barriers
- Testing and fixes are documented and dated - your evidence if a letter ever arrives
Automated vs manual ADA compliance
The honest division of labor:
| Automated (AI) | Manual (certified experts) | |
|---|---|---|
| Finds | Contrast, alt text, labels, ARIA errors, structure - at scale, continuously | Reading order logic, alt-text quality, keyboard flows, screen reader experience |
| Fixes | A large share of the common, machine-recognizable patterns | Complex components, forms, tables, documents, judgement calls |
| Alone it is | Fast but incomplete - and courts know it | Complete but slow and point-in-time |
| Together | The hybrid model: automation for scale and monitoring, experts for depth and evidence |
What non-compliance actually costs
The typical event is not a government fine - it is a private lawsuit or demand letter: settlement, plaintiff's legal fees, your legal fees, remediation under deadline, and sometimes repeat suits from serial plaintiffs (the same inaccessible site can be sued more than once). State laws stack on top - California's Unruh Act attaches statutory damages per violation. Against that, a planned compliance program is not just safer; it is cheaper, because remediation under your own schedule costs a fraction of remediation under a settlement's.
Frequently asked questions
What is ADA compliance for a website?
Meeting the Americans with Disabilities Act's requirement of equal access on your website - in practice, conforming to WCAG Level AA and being able to evidence it with testing and documentation.
Is ADA website compliance mandatory?
Yes, in effect. The DOJ holds that the ADA applies to web content, courts have allowed thousands of suits on that basis, and Title II entities now face an explicit WCAG 2.1 AA rule with 2027/2028 deadlines.
What is the technical standard for ADA compliance?
WCAG Level AA. Title II names WCAG 2.1 AA explicitly; for private businesses courts and settlements use WCAG AA as the benchmark. Building to WCAG 2.2 AA covers both today and next.
How do I check if my website is ADA compliant?
Run a free automated scan for the machine-detectable failures, then a manual audit - keyboard, screen reader, criterion by criterion. The combination, documented, is what compliance verification means.
Does ADA compliance software exist?
Software handles detection, monitoring and a large share of automatable fixes. Full compliance also needs human remediation and testing - which is why the effective model is hybrid: AI plus certified experts.
Does the ADA apply to PDFs on my site?
Yes. Documents that are part of your services - forms, statements, menus - are covered, and are among the most commonly cited failures. They are tested against WCAG and PDF/UA.
What happens if my website is not ADA compliant?
The realistic risk is private litigation: demand letters, settlements, fees and court-supervised remediation - repeated, in some cases, by serial plaintiffs. State laws like California's Unruh Act add statutory damages.
- US Department of Justice, Guidance on Web Accessibility and the ADA - ada.gov
- US Department of Justice, ADA Title II web and mobile accessibility rule - ada.gov
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2 - w3.org
- UsableNet, Annual digital accessibility lawsuit reports - usablenet.com
Last updated . Reviewed by the EqualWeb accessibility team.
Get ADA compliant - and stay that way
Audit, remediation, monitoring and legal-grade documentation by certified IAAP/CPWA experts, with AI doing the heavy lifting. Free accessibility checks included.