ADA website lawsuit playbook.

What's actually happening — the demand-letter pattern.

For several years, ADA Title III website filings have run in the thousands annually in the United States. The pattern is well documented in industry reports from law firms tracking the docket: a plaintiff's firm sends a pre-litigation demand letter alleging that a publicly-facing commercial website does not comply with the Americans with Disabilities Act, citing barriers tested by either a screen-reader user or an automated tool. The letter usually offers settlement and remediation in lieu of filing suit.

The targets have widened. Early matters concentrated on retail and hospitality. More recent rounds have pulled in healthcare practices, law firms, accountants, contractors, schools (especially private schools that take public funds), nonprofits, and small e-commerce shops. If your business is consumer-facing and your website has barriers a tester can document, you are inside the addressable population.

The first 7 days — the triage playbook.

This is what we run with clients in week one. It runs in parallel with the legal track, not in place of it.

Day 1 — Preserve and route.

• Do not edit the site.
• Do not respond to the plaintiff’s firm directly.
• Take a full Wayback / archive snapshot of every page named or referenced in the letter.
• Send the letter to your attorney. If you don’t have one, this is the first call you make today.

Day 2–3 — Run a real audit.

This is the parallel technical track. We run three layers:

• Automated — axe-core, Lighthouse, WAVE across every page in the site map. These find roughly a third to a half of real WCAG issues, which is why automated alone is not the floor.
• Manual functional — keyboard-only traversal of the primary tasks (book a tour, request a quote, complete a form, check out). This is where most barriers actually live.
• Assistive technology — VoiceOver and NVDA on the same primary tasks. If a screen reader can’t do the job, the site has a real problem.

The output is a per-success-criterion conformance report (WCAG 2.2 AA), with each finding tagged severity / page / criterion / proposed fix. That report is the artifact your attorney needs.

Day 4–5 — Build the remediation plan.

The plan has three buckets:

• Now — quick wins (alt text, form labels, heading hierarchy, focus order, color contrast tweaks). Days, not weeks.
• Soon — structural fixes (semantic re-templating, ARIA correction, dynamic-content announcements). Weeks.
• Ongoing — the monitoring and authoring practice that prevents regression. CMS guardrails, contributor training, recurring audits.

Day 6–7 — Author the documentation kit.

• An accessibility statement (real, dated, with a contact path).
• A WCAG 2.2 AA conformance report by criterion.
• A documented remediation timeline tied to the plan above.
• A point of contact your business commits to monitoring for accessibility feedback.

This kit is what your attorney brings to the negotiating table. It is the difference between “we’re working on it” and “here is the conformance report, the dated remediation plan, and the public statement.”

Why we don't use accessibility overlays.

Accessibility overlays are JavaScript widgets that load on top of an existing site and offer a toolbar (font size, contrast, screen-reader mode, etc.). The widely shared position from accessibility specialists, including the authors of major statements signed by hundreds of accessibility professionals, is that overlays do not bring non-conforming sites into WCAG conformance and may introduce new barriers for users who already rely on their own assistive technology.

Beyond the conformance question, public lawsuit data shows that businesses whose only accessibility measure was an overlay have been named in subsequent ADA matters anyway. The overlay vendors have themselves been the subject of public legal action, which is the underlying reason the term userway lawsuit trends in search.

Our position is operational, not ideological: a site that fails WCAG fails WCAG, regardless of the JavaScript loaded on top of it. The remediation has to happen in the markup, the patterns, and the authoring process. That’s what we do, and it’s what survives a response review.

What settlements typically look like.

Settlement amounts in individual ADA website matters are negotiated and usually confidential, so any range you read online is an aggregate from public reports and industry trackers, not a promise. Common patterns we see referenced in those reports:

• Low five figures plus attorneys’ fees for individual matters resolved early with a remediation plan.
• Mid five figures for matters that escalate before an early-resolution offer.
• Higher amounts for class-action or multi-claimant matters, or where statutory damages apply (some state laws stack on top of the federal claim).

The cheaper part is almost always the remediation itself. A focused engagement to bring a small-business site into WCAG 2.2 AA conformance typically costs less than the early-settlement floor. The math usually says: remediate first, settle from a position of conformance, monitor going forward.

The remediation framework — what real fixes look like.

WCAG 2.2 AA covers four principles (perceivable, operable, understandable, robust) and 50 success criteria at the AA level. The matters URCO sees in practice cluster around the same dozen issues. If your site has any of these, fix them first.

Perceivable

• Images missing meaningful alt text (or alt="" on informative images).
• Color contrast below 4.5:1 for body text or 3:1 for large text and UI components.
• Videos without captions and transcripts.
• PDF documents that aren’t tagged or are scans without OCR.

Operable

• Keyboard traps where focus enters a component and can’t leave (often modal dialogs).
• Buttons or links not reachable by keyboard (custom <div> controls without role or tabindex).
• Skip-to-content link missing or broken.
• Focus indicators removed by CSS (the “outline: none” problem).

Understandable

• Form fields without programmatic labels.
• Error messages that aren’t announced or are conveyed by color alone.
• Page <html lang> attribute missing or wrong.

Robust

• Custom widgets that don’t expose role / state / value to assistive tech.
• ARIA patterns implemented incorrectly (the most common: aria-hidden on focusable content).

We use the WAI-ARIA Authoring Practices (APG) as the canonical reference. URCO’s 100-point scorecard includes accessibility as one of seven categories.

How URCO can help.

Three on-ramps depending on where you are.

• You haven’t received a letter, want a baseline. Run the free URCO audit. Returns a 100-point breakdown across accessibility, technical SEO, mobile UX, conversion, tracking, content, and trust. About 60 seconds to start. Use the score as your baseline conformance evidence.
• You want a deep manual audit. Book a 5-day manual audit. Includes the per-success-criterion conformance report, the prioritized remediation plan, and the documentation kit described above.
• You have a letter or a deadline. Contact us directly. We can typically start within a week and have an initial conformance report and remediation plan in hand inside 7–10 days.

Related reading.

• Wix, Squarespace, Webflow — what their platforms can and can’t do for accessibility
• URCO Accessibility services
• URCO’s own accessibility statement (template you can adapt)
• WCAG vs ADA: what your website actually needs

ADA website lawsuit playbook — FAQ.