ADA website compliance

The Americans with Disabilities Act (ADA) requires "places of public accommodation" to be accessible. The Department of Justice has consistently taken the position that this includes the websites and apps of businesses open to the public, even though the ADA itself predates the modern web and does not name a specific technical standard for private businesses.

In 2024 the DOJ did set an explicit standard for one group: state and local government websites (Title II) must meet WCAG 2.1 Level AA, with deadlines phased in by entity size. For private businesses (Title III), courts have repeatedly pointed to the same WCAG guidelines as the practical benchmark.

When people say "ADA compliant website," they almost always mean WCAG 2.1 or 2.2, Level AA. That is the standard referenced in DOJ guidance, settlement agreements, and the large majority of legal complaints. Targeting WCAG 2.2 AA covers 2.1 AA as well, so it is the safe target to aim for.

The ADA is split into titles, and two of them matter for websites. Knowing which one covers you determines whether you have an explicit technical deadline or only case law to work from.

• Title II covers state and local government, including public universities, school districts and transit agencies. This is the one with a firm rule: the DOJ's 2024 regulation requires WCAG 2.1 Level AA, with compliance dates phased by entity size.
• Title III covers private businesses that are "places of public accommodation", which in practice means most retailers, restaurants, hotels, banks, healthcare providers and online services. Title III has no regulation naming a technical standard, which is precisely why the litigation exists: courts fill the gap, and they have consistently pointed at WCAG AA.

Nearly every web accessibility demand letter sent to a business is a Title III claim. The absence of an official standard is not a defence; it means the benchmark is set by settlements and rulings rather than by a rulebook you can point to.

Thousands of web accessibility lawsuits and demand letters are filed in the US every year, many under the ADA and state laws like California's Unruh Act and New York's human rights law. Most target the same handful of issues: low colour contrast, missing image alt text, unlabeled form fields, and keyboard traps. The honest takeaway is not "panic," it is that these are common, findable, and fixable, and that demonstrating ongoing effort matters.

Run the free scan above on any page. It loads the page in a real browser and runs axe-core against WCAG 2.2 A and AA, then outlines every failing element by severity and maps it to the success criterion. Automated testing reliably catches the machine-checkable issues, which are the bulk of what gets cited in complaints. It cannot judge everything, so it flags what still needs a human and never claims you are "compliant."

Accessibility overlay widgets that promise instant ADA compliance from one line of JavaScript do not fix your underlying code, and they have themselves become a frequent target of lawsuits. Use a scanner to find real issues, fix them in your markup and content, and re-check. There is no shortcut button.