Equivalent access to goods and services
Disabled users must be able to achieve the same outcome as non-disabled users — browse, compare, purchase, book, pay, communicate — without needing assistance or a separate interface.
ADA Compliance
United States · Federal
What is the ADA?
The Americans with Disabilities Act of 1990 is the foundational US civil-rights law prohibiting discrimination against people with disabilities — and US courts have consistently held that it applies to websites and mobile apps.
Enacted
26 July 1990
Enforced by
US DOJ + private action
Technical target
WCAG 2.1 AA
Penalty range
$75k – $150k+ per violation
The Americans with Disabilities Act (ADA) is a federal civil-rights statute signed into law by President George H.W. Bush on 26 July 1990. It prohibits discrimination on the basis of disability in five contexts (“titles”): employment (Title I), state and local government (Title II), public accommodations (Title III), telecommunications (Title IV) and miscellaneous provisions (Title V).
For digital accessibility, two titles matter most. Title II covers state and local government agencies, courts, public universities and transit authorities. Title III covers private businesses “open to the public” — retail, restaurants, hotels, banks, healthcare, entertainment, professional services.
The statute itself predates the web, but since National Federation of the Blind v. Target (2006), and every appellate decision since, US courts have treated business websites as places of public accommodation. The DOJ reaffirmed this position in its 2022 web-accessibility guidance and its 2024 Title II final rule, which formally adopts WCAG 2.1 Level AA for all state and local governments.
Scope
Who must comply?
The ADA applies to any organisation with an American user base — including foreign companies selling into the United States. The test is whether your site or app is used by people in the US, not where you’re headquartered.
Title II applies to: every US state, local and territorial government entity, including public K-12 schools, public universities and community colleges, state courts, public libraries, public transit agencies and any services contracted by these bodies. From April 2026 (large entities) and April 2027 (small entities), these must meet WCAG 2.1 Level AA for all web content and mobile apps.
Title III applies to: private businesses operating as places of public accommodation — 12 categories including retail, food service, lodging, entertainment, healthcare providers, legal and financial services, education providers, social service centres, gyms and places of recreation.
There is no revenue or employee threshold for Title III. A sole-trader e-commerce site with three customers faces the same legal exposure as Amazon. Courts have rejected the argument that small size or good intent is a defence; what matters is whether disabled customers can equivalently use your service.
ADA lawsuits against international companies with US traffic are common — jurisdiction is established by serving US users, not by company domicile.
Key requirements
What the ADA actually requires
Title II now points to WCAG 2.1 AA directly. Title III does not specify a technical standard, but the DOJ, EEOC and every federal appellate court treat WCAG 2.1 AA as the operative benchmark.
WCAG 2.1 Level AA conformance
50 success criteria across Perceivable, Operable, Understandable and Robust. Title II mandates this explicitly from 2026. Title III cases default to it as the reasonable-accommodation standard.
Accessible PDFs and documents
Any PDF or document served through a public-accommodation website must be tagged, navigable by screen reader and keyboard-operable. Image-only PDFs and unreadable forms are common triggers for ADA complaints.
Keyboard-only operation
Every interactive element — menus, carousels, modals, forms, checkout flows — must be fully usable with only a keyboard. No mouse-only drag-and-drop, no hover-only reveals.
Screen-reader compatibility
Images need alt text, form fields need labels, structure needs headings, dynamic updates need ARIA live regions. JAWS, NVDA and VoiceOver are the de-facto testing trio in ADA case law.
Captions, transcripts, audio descriptions
Pre-recorded video needs synchronised captions and, for content where visuals carry meaning not in the audio, audio description. Live video needs real-time captions.
Contrast, text size, reflow
Minimum 4.5:1 contrast for body text, 3:1 for large text and UI components. Content must reflow at 400 % zoom without horizontal scrolling.
Forms and error handling
Labels programmatically associated with inputs, error messages identified in text (not colour alone), suggested corrections, confirmation steps for legal and financial commitments.
Accessibility statement
Not strictly mandated by statute, but universally recommended. State the standard you’re targeting, known limitations, contact method and how to request an accessible alternative. Used as evidence of good-faith effort.
Third-party content and widgets
Courts have explicitly ruled that outsourcing doesn’t outsource liability. Chat widgets, embedded videos, payment iframes and analytics overlays on your site are your responsibility to make accessible.
Penalties & enforcement
What non-compliance costs
The ADA is enforced through both federal action (DOJ) and private lawsuits. Private lawsuits dominate: in 2024, over 4,600 Title III website lawsuits were filed in federal court alone — not counting state-court filings.
$75,000
First DOJ violation
Maximum civil penalty for a first ADA violation under Title III enforcement by the Department of Justice (28 CFR 36.504).
$150,000
Subsequent violations
Maximum per-violation penalty for subsequent violations. DOJ can also seek injunctive relief and attorneys’ fees on top.
$50k+
Typical private settlement
Plaintiffs cannot collect damages under Title III, but can recover attorneys’ fees. Typical settlements range from $25,000 to $100,000+ plus remediation costs.
Notable cases: NFB v. Target ($6M settlement, 2008). Gil v. Winn-Dixie (11th Cir., mixed precedent). Robles v. Domino’s (9th Cir. 2019, cert. denied by Supreme Court — website of a physical business is subject to ADA). NFB v. Scribd (Title III applies to online-only businesses).
State-level overlays: California’s Unruh Civil Rights Act treats ADA violations as minimum-$4,000-per-plaintiff statutory damages. New York has similar state human-rights law. ADA defendants in these states face compounded liability.
Deadlines
Key ADA digital-accessibility deadlines
For Title II (public sector), the DOJ’s 2024 final rule sets two hard deadlines. For Title III (private sector), there is no “deadline” — the obligation has been in effect since 1990.
26 July 1990
ADA signed into law
Title III obligation for private-sector “places of public accommodation” takes effect. Digital accessibility obligation has existed continuously since this date in the eyes of the DOJ and US courts.
February 2008
NFB v. Target $6M settlement
First major ADA web-accessibility settlement. Established that commercial websites connected to physical stores are subject to Title III.
March 2022
DOJ web-accessibility guidance
Department of Justice formally publishes guidance stating that Title III covers websites of public-accommodation businesses, with WCAG cited as the accepted standard.
April 2024
Title II final rule published
DOJ publishes 28 CFR Part 35: WCAG 2.1 Level AA becomes the explicit technical standard for all state and local government web content and mobile apps.
24 April 2026
Title II compliance deadline — large entities
State and local governments serving populations of 50,000 or more must meet WCAG 2.1 AA for all web content and mobile apps.
26 April 2027
Title II compliance deadline — small entities
All remaining state, local and special-district government entities must meet WCAG 2.1 AA. No further extensions expected.
How to comply
Your ADA compliance checklist
Courts assess ADA compliance as a process, not a pass/fail. Demonstrating a documented, ongoing programme is itself a defence against lawsuits.
Run an automated audit of your entire site
Scan every page and user flow with a WCAG 2.1/2.2 checker. Prioritise issues by impact and frequency. Automated tools catch 30–50 % of WCAG failures — a solid baseline.
Conduct manual testing for the remaining 50–70 %
Screen-reader testing (JAWS, NVDA, VoiceOver), keyboard-only navigation, zoom to 400 %, text-spacing tests, colour-contrast verification of non-scanned elements.
Remediate high-impact issues first
Login, checkout, main navigation, forms. A partially accessible home page buys nothing if users can’t complete the core task.
Audit and remediate PDFs and documents
Every PDF served on your site is subject to the same standard. Tag structure, reading order, alt text, table headers, language, bookmarks.
Publish an accessibility statement
State target standard (WCAG 2.1 AA), date of last audit, known limitations, a named contact and how to request an accessible alternative. Used as good-faith evidence in litigation.
Integrate accessibility into the design system
Fixing the symptom on one page creates 100 new issues on the next feature. Bake it into components, templates and CI checks.
Re-audit on every major release
A site that passed audit in Q1 and shipped five feature releases by Q4 is almost certainly non-compliant by year-end. Continuous monitoring beats annual audits.
Next step
Find out which ADA issues your site has
Run a free WCAG 2.1/2.2 audit of any public URL. You’ll get the exact criteria that fail, the screen-reader output, the DDA/ADA mapping and a remediation fix for each issue.