ADA website compliance audit (USA): a 2026 SMB guide

The Americans with Disabilities Act of 1990 has become, over the last decade, the single largest source of website-related litigation against SMBs in the United States. 4,000+ federal lawsuits were filed in 2024 alone, and the plaintiff bar has shifted decisively from large enterprises to SMBs whose insurance and settlement posture is more predictable. An ADA website compliance audit is how you find out where you stand before someone files.

How the ADA actually applies to websites

The ADA itself does not mention websites — it predates the modern web. Title III requires “places of public accommodation” to be accessible to people with disabilities. The litigation question for thirty years has been whether a website is a “place.”

The current state of the law:

• DOJ position: websites of public accommodations are covered. Reaffirmed in 2022 guidance and consistent in enforcement actions.
• 1st, 2nd, 3rd, 4th, 7th, 9th, 11th Circuits: websites of physical public accommodations are covered. Some circuits require a “nexus” to a physical location (you have a brick-and-mortar store); others apply Title III to online-only businesses too.
• 5th, 6th Circuits: more restrictive. Coverage typically requires a physical-location nexus.
• State laws: California’s Unruh Civil Rights Act, New York State and City human-rights laws, and similar laws in Florida and Massachusetts often provide an independent basis for suit, including against online-only businesses, with lower thresholds than the federal ADA.

The technical bar

The ADA does not specify a technical standard, but DOJ guidance, court rulings, and settlement agreements consistently reference WCAG 2.1 Level AA (sometimes 2.0). The April 2024 DOJ rule for state and local governments (ADA Title II) mandates WCAG 2.1 AA explicitly; while it does not bind Title III, courts and plaintiffs routinely apply it as the de facto standard.

For SMB compliance work, the practical consequence is that the same WCAG 2.1 AA audit that satisfies the EAA, the UK Equality Act, and AODA also satisfies ADA Title III. One technical audit, multiple jurisdictions.

What plaintiffs actually target

Plaintiff complaints follow a recognisable pattern. The boilerplate alleges a series of specific WCAG failures observed during a screen-reader test, typically:

• Images without alt text or with empty alt on meaningful images
• Links and buttons with no accessible name (icon-only buttons are a major target)
• Form fields without labels
• Insufficient colour contrast
• Keyboard traps in modals or carousels
• Improper heading structure
• Inaccessible PDFs linked from the site
• Video without captions

These are exactly the issues an automated scan catches. A site that passes a cleanaxe-core scan has dramatically reduced exposure even if it has not completed a full manual audit.

The accessibility-overlay trap (US-specific)

US SMBs are the primary market for accessibility overlay vendors — accessiBe, AudioEye, UserWay. The pitch is that a single line of JavaScript creates ADA compliance and immunity from suit. The reality:

• FTC enforcement against accessiBe in January 2025: USD 1 million settlement for misleading marketing about overlay-based compliance.
• Plaintiff targeting: plaintiff firms have publicly stated they specifically target overlay-using sites because the failure pattern is so predictable. The Web Accessibility Initiative and the National Federation of the Blind have both issued statements warning against overlays.
• Class actions against AudioEye and UserWay in 2024–2025 making similar claims.

Removing an overlay reduces lawsuit exposure. Adding one increases it.

The realistic SMB defence plan

Five steps, in order, that close most of the gap.

1. Run a baseline WCAG 2.1 AA audit. Scanned audit captures 30–40% of issues automatically; the high-severity ones cluster in this band. Fix them first.
2. Manual screen-reader test of your top 10 pages. Home, product pages, cart, checkout, account, contact. Two-hour exercise with NVDA or VoiceOver.
3. Publish an accessibility statement. Specify the standard you target (WCAG 2.1 AA), the date of last review, known limitations, and a feedback channel. The plaintiff bar prefers easy targets; a credible statement and a real feedback mechanism shift the calculus.
4. Set up continuous monitoring. A WCAG-clean site stays clean only until the next deploy. Most regressions ship six weeks after the audit.
5. Document everything. If a complaint or lawsuit comes in, the audit-and-remediation log is your defence. Settlements depend heavily on whether the defendant can show good-faith effort.

Cost ranges

From SMBs we work with:

• Defence of a single ADA web lawsuit: USD 5,000–25,000 settlement, plus 2–6 weeks of remediation work. Repeat suits common after first settlement.
• One-time consultant audit: USD 5,000–15,000 depending on site size.
• Continuous scanning + ad-hoc consulting: USD 100–500 per month for tooling plus periodic professional review.

The ROI of pre-emptive auditing over reactive settlement is usually clear after the first lawsuit avoided.

How Veracly approaches ADA

One scan reports against ADA Title III, the EAA, the UK Equality Act, AODA, and general WCAG 2.1 AA. Each violation cites the relevant WCAG criterion, the legal framework it implicates, and the developer fix. The output includes a draft accessibility statement and a remediation log suitable for litigation defence. Run a free scan.

See also: WCAG 2.1 AA accessibility audit explained · EAA compliance for SMBs: what changes June 2025 · What is a website compliance audit?