ADA Title III for websites: what U.S. businesses actually need to know

A practical, no-jargon guide to how the Americans with Disabilities Act applies to websites in 2026 — what the DOJ has signaled, what plaintiff firms are filing, and how to reduce your exposure.

The Americans with Disabilities Act (ADA) is U.S. civil-rights law that prohibits discrimination on the basis of disability. Title III applies to “places of public accommodation” — and since 2017, federal courts have consistently held that this includes commercial websites and apps, even when the business has no physical storefront.

That means: if you sell to U.S. consumers, your website is almost certainly subject to Title III, and an inaccessible website is a potential lawsuit.

The lawsuit landscape (and why it's a problem for businesses)

Industry trackers (UsableNet, Seyfarth Shaw, ADA Title III Federal Lawsuits Annual Report) have recorded between 3,000 and 4,500 ADA Title III website accessibility lawsuits per year for several years running. Most are filed by a small number of plaintiff firms; many target small and mid-sized businesses because the economics favor settlement over defense.

Typical demand-letter pattern:

1. A plaintiff firm runs an automated scanner (often a free one) against your homepage.
2. They cite a list of WCAG violations in a complaint, often with a specific allegation that the plaintiff was denied equal access on a specific date.
3. They offer to settle for a four-to-five-figure sum plus a remediation commitment, without the cost of trial.
4. Many businesses settle because the litigation cost would exceed the settlement.

This isn't a critique of plaintiffs (the law exists for a reason and many plaintiffs have legitimate accessibility needs). It's an accurate description of the operational reality businesses face.

What “compliance” means in the absence of formal regulation

The DOJ has not issued a Title III website regulation. There is no codified technical standard that, if you meet it, conclusively proves compliance. Courts have instead developed a working consensus:

• Most settlements and consent decrees reference WCAG 2.1 Level AA as the technical benchmark. With the publication of WCAG 2.2 in October 2023, expect newer agreements to reference 2.2 AA.
• Federal Title II (state and local government) issued a binding rule in April 2024 requiring 2.1 AA. While Title II doesn't apply to private businesses, it sets the regulatory expectation in court.
• The DOJ has explicitly said WCAG conformance is a means of compliance, not the only means — but it is by far the most defensible.

Practical risk-reduction steps

Plaintiff firms target sites that are easy to scan and easy to find issues on. You don't need to be perfectly conformant; you need to be visibly trying.

1. Run automated scans regularly

Automated tools catch 30-40% of WCAG issues — the well-defined programmatic ones. Those are also the issues plaintiff firms cite most often, because they're what their automated scanners detect. Removing this category of finding is the single highest ROI accessibility investment.

2. Publish an accessibility statement

A page (typically /accessibility) describing your conformance commitment, the standard you target (WCAG 2.2 AA), known limitations, and a contact for accessibility issues. This isn't a get-out-of-jail-free card, but it signals good faith and gives users a path to flag issues before suing.

3. Establish a remediation workflow

When an accessibility issue is reported, you need a documented response: who owns it, target fix timeline, communication with the reporter. Demonstrating an active remediation process is one of the strongest defenses if you do receive a demand letter.

4. Manual testing for the highest-risk flows

Account creation, checkout, and contact forms are the flows most likely to generate “denied equal access” allegations because they're functional bottlenecks. Test these with a screen reader and keyboard-only at least quarterly.

5. Train your engineering team

Most accessibility issues are introduced by developers who never learned the practices, not by malicious actors. A 2-hour training that covers semantic HTML, ARIA basics, and how to use a screen reader prevents 80% of the new issues you would otherwise ship.

Where Plumb fits

Plumb handles step 1 — automated scanning — at a price that fits an SMB budget ($49/month covers most small business sites) and produces reports suitable for engineering follow-through. Steps 2 through 5 are work your team does; we don't replace your accessibility consultant or your legal counsel. We make the technical part fast, repeatable, and inexpensive enough that running a scan before every release becomes routine.

This article is not legal advice. ADA Title III liability depends on facts, jurisdiction, and the specific allegations in any complaint. Consult a qualified attorney for legal questions specific to your business.