In 2024, U.S. federal courts saw more than 4,000 ADA Title III website-accessibility lawsuits — UsableNet's annual report counted 4,536 filings against 2,452 unique defendants. Plaintiffs continue to target small and mid-size online businesses alongside enterprise. This checklist tells you what to put in place before a demand letter arrives.

Why 2026 looks different

• April 2024 DOJ Title II rule: the Department of Justice finalized a rule requiring state and local government web content to meet WCAG 2.1 Level AA. Title II is for public entities, but it sets a public conformance bar plaintiffs cite when arguing about Title III (private businesses).
• European Accessibility Act (EAA) enforcement began 28 June 2025. Many U.S. businesses with EU customers (e-commerce, SaaS, banking) are now in scope under EU law in parallel with ADA at home. See the EU Commission resources for sector applicability.
• Courts continue to look unfavorably on “accessibility overlay” widgets as a sole remediation. Several 2023–2024 decisions allowed cases to proceed despite an overlay being installed.

The 2026 checklist

1. Pick a target standard and write it down

WCAG 2.1 Level AA is the de facto bar referenced by the DOJ. WCAG 2.2 (October 2023) adds 9 success criteria you should adopt; conforming to 2.2 AA implies 2.1 AA. Publish your chosen standard in your accessibility statement so plaintiffs and courts know what you're aiming at.

2. Publish an accessibility statement

A statement should include: target standard (e.g. “WCAG 2.2 AA”), conformance level (full / partial), date of last audit, contact method (email + phone), and a remediation timeline. Link it from your footer on every page. Templates and guidance: W3C WAI.

3. Run a dated baseline audit

Use an automated scanner (axe-core, WAVE, AccessProof) plus at least one manual screen reader pass. Export the result with a timestamp and store it. Today's baseline is tomorrow's evidence that you started.

If you don't have a baseline yet, AccessProof's free scanner produces a dated PDF in under 90 seconds.

4. Fix the critical and serious issues first

Plaintiff firms cite a relatively small set of patterns repeatedly:

• Missing alt text on informative images (WCAG 1.1.1).
• Form fields without labels (WCAG 1.3.1, 3.3.2).
• Color contrast failures (WCAG 1.4.3).
• Keyboard inaccessible controls (WCAG 2.1.1).
• Missing or duplicate page titles (WCAG 2.4.2).
• Empty or unclear link text (“click here”) (WCAG 2.4.4).

These are the ones automated tooling catches and plaintiffs screenshot. Address them first, regardless of WCAG level.

5. Document remediation with dates

Commit messages, ticket IDs, before/after screenshots, dated PDF reports — every fix should leave a paper trail. Courts and counsel are persuaded by continuous, dated activity far more than by “we did an audit once.”

6. Schedule recurring scans

Monthly minimum, weekly preferred. The 2018 Robles v. Domino's outcome and most subsequent settlements reinforce the same expectation: regressions are inevitable, and the standard is whether you detect and fix them quickly. AccessProof runs scans automatically on a schedule and archives every PDF — starter plans begin at weekly cadence.

7. Train at least one developer to use a screen reader

30 minutes per release using NVDA (Windows / Firefox) or VoiceOver (Mac / Safari) catches issues no automated tool can — reading order, live region announcements, custom widget patterns. Free, no certifications required.

8. Have counsel on speed dial

Pre-identify counsel familiar with ADA Title III litigation in your state. If a demand letter arrives, do not negotiate directly. Forward to counsel within 24 hours.

9. Avoid overlay widgets as a sole remedy

An overlay can be one layer of defense in depth, but courts now scrutinize them. The Overlay Fact Sheet (signed by 800+ accessibility professionals) catalogs the limitations. Don't rely on an overlay as your only remediation.

10. Review your third-party widgets

Chat widgets, video players, payment iframes, signup forms — third-party code accounts for a significant share of failures on e-commerce and SaaS sites. Audit each integration and request accessibility statements from vendors. Cite them in your own statement (“Component X is provided by vendor Y; their conformance status: Z”).

What a court-ready audit trail looks like

If you receive a demand letter and have all of these on file, you start the conversation from a defensible position:

• An accessibility statement on every page, dated within the last 12 months.
• A series of dated PDF audit reports (monthly or weekly cadence).
• A public remediation log or changelog showing fixes shipped.
• A documented incident response process for accessibility complaints.

The difference between a $20,000 settlement and a $5,000 settlement is often the strength of this documentation alone.

Common mistakes

• One-time audit, no follow-up. A single audit ages fast; the site changes, the standards evolve, regressions creep in.
• Removing the offending page. Looks like evidence destruction. Fix it instead.
• Overlay-only remediation. Documented in court rulings as insufficient.
• Treating accessibility as a project, not a process. The expectation is ongoing conformance.

Where AccessProof fits

AccessProof runs axe-core 4.9+ against your site on a schedule, scores it against WCAG 2.2, and produces a dated PDF after every scan. The PDFs are designed to be exportable as part of a remediation log. Compared to overlay widgets, we don't inject JavaScript into your site — we measure it. See our comparison vs. accessiBe for the detail.

A short timeline of how we got here

Understanding the trajectory helps explain why 2026 looks different from 2018:

• 1990: ADA signed into law. Title III applies to “places of public accommodation”; the question of whether websites count was unresolved.
• 2018: Robles v. Domino's Pizza — the Ninth Circuit held that the ADA applies to Domino's website because it had a nexus to a physical place. SCOTUS declined to review.
• 2019–2023: Federal filings of Title III website cases stabilized around 2,000–4,000 per year per UsableNet's annual reports. New York and California remain dominant venues.
• 2024: DOJ finalizes its Title II web rule for state and local government. Title III rulemaking remains pending, but the Title II rule defines “technical standard” as WCAG 2.1 AA, signaling DOJ's view.
• June 2025: European Accessibility Act enforcement begins. U.S. businesses serving EU consumers in covered sectors are now in scope.

The macro trend is consistent: courts and regulators expect WCAG conformance, plaintiffs file at scale, and overlay-only remediation is increasingly disfavored.

Sector-specific notes

• E-commerce: highest volume of lawsuits. The product page → cart → checkout flow is the path plaintiffs test most. Audit that flow weekly.
• SaaS: dashboards and onboarding flows are commonly cited. Trial signup pages get tested before paying-customer flows.
• Hospitality / travel: room-selection widgets, date pickers, and PDF menus are frequent flagged elements.
• Healthcare: patient portals are subject to both ADA and HHS Section 504/1557 standards. Multi-standard compliance is essential.
• Government contractors: Section 508 compliance is its own statute; the technical standard is WCAG 2.0 AA per the 2017 refresh.

Cost of doing nothing vs. cost of compliance

Typical settlement amounts for ADA web Title III cases reported in trade press range from a few thousand to mid-five-figures, plus mandatory remediation. Annual programmatic compliance — automated scans, a part-time accessibility engineer or service, periodic manual audits — generally costs less than a single contested case. The ROI argument writes itself; the question is operational discipline.

What plaintiffs actually look for

Demand letters and complaints we've seen cite a remarkably consistent set of evidence:

• Screenshots of the homepage and product/service pages with annotations showing missing alt text or contrast failures.
• Automated scanner output (often WAVE or axe DevTools) included as appendix.
• Specific quotes from your accessibility statement (or absence thereof) used against you.
• Comparison against your competitor's site if they have better conformance.
• Records of past complaints unanswered or unresolved.

This shapes the defense strategy: if the same scanner the plaintiff used produces a clean (or rapidly-improving) report on your dated audits, you neutralize the strongest evidence early.

Vendor and procurement considerations

If you sell to enterprise or government, your accessibility posture is a procurement input:

• VPAT (Voluntary Product Accessibility Template) using ITI's template — increasingly required by procurement.
• ACR (Accessibility Conformance Report) — the executive summary that wraps a VPAT.
• Section 508 conformance for U.S. federal contracts (WCAG 2.0 AA per the 2017 refresh).
• EN 301 549 for European procurement (incorporates WCAG 2.1 AA + non-web criteria).

If you don't have a VPAT, you'll lose deals before you ever hear about a lawsuit. A current VPAT typically requires a documented audit, which is the same artifact your remediation log needs anyway.

Documentation cadence

The defensible operational rhythm:

• Weekly: automated scan of critical flows (homepage, signup, checkout, account).
• Monthly: review the scan deltas, file tickets, close the previous month's.
• Quarterly: manual screen-reader walkthrough of the same critical flows.
• Annually: third-party audit (paid). Refresh VPAT.
• Continuously: open contact channel for accessibility complaints, monitored by a named owner.

The cadence doesn't need to be heavy. It needs to be documented and actually executed.

The simplest first step

If you have nothing in place today, start here:

• Run a free baseline scan. AccessProof free scanner gives you a dated PDF in 90 seconds.
• Publish an accessibility statement (W3C templates are free). Add it to your footer.
• Triage the top 10 critical/serious findings with your dev team.
• Schedule a recurring scan — weekly minimum. Starter plans at AccessProof cover this.

That sequence — baseline + statement + remediation + recurring scan — is the difference between “we tried” and “we have evidence we tried.”

This article is general guidance, not legal advice. Always consult counsel for your specific situation.

---

Originally published on access-proof.com.