The state of play
ADA web accessibility lawsuits surged 12% year-over-year in 2024, with over 4,500 federal complaints filed and significantly more state-level filings. California and New York lead the country in volume; Nevada is one of the fastest-growing jurisdictions. Plaintiff firms have built a cottage industry around finding non-compliant small business websites and filing demand letters.
What the law actually requires
The Americans with Disabilities Act (ADA) does not specify technical requirements for websites, but courts have consistently held that websites of "places of public accommodation" must be accessible to people with disabilities. The de facto standard is WCAG 2.1 Level AA, which covers four principle areas: perceivable, operable, understandable, and robust.
In practice this means: semantic HTML, proper heading hierarchy, alt text on all meaningful images, keyboard navigation throughout, color contrast meeting AA ratios, form labels and ARIA where needed, captions on video, and resizable text without breaking layout.
The typical lawsuit pattern
Plaintiff firms run automated scans of small business websites in target states. When a scan flags accessibility issues, they send a demand letter and (often) file a lawsuit simultaneously. Defendants face two costs: the settlement itself (typically $5-15k for an early settlement, more if it proceeds) and the remediation costs to fix the underlying problems.
What makes this particularly painful for small businesses: the plaintiff does not need to prove they were personally harmed in the same way they would for a physical-space ADA case. The mere existence of barriers on the website is often sufficient to ground a claim.
What most websites fail at
- Missing or generic alt text on images ("image1.jpg" instead of meaningful description)
- Color contrast below WCAG AA ratios (especially light text on light backgrounds)
- Form fields without labels or with placeholder-only labels
- Keyboard navigation broken (can’t Tab through pages or focus indicators invisible)
- Heading hierarchy skipped (H1 to H4 with no H2 or H3 between)
- Video and audio without captions or transcripts
- PDF documents that are image-only (not text-readable)
- No skip-to-content link for screen reader users
What to fix first
If you have an existing website with potential accessibility issues, prioritize:
- Add alt text to every meaningful image
- Verify color contrast meets WCAG AA ratios (4.5:1 for normal text, 3:1 for large text)
- Add labels to all form fields
- Ensure keyboard navigation works throughout
- Add a skip-to-content link
- Install a reputable accessibility widget for visitor control
- Publish an accessibility statement page
The statement page matters because plaintiff firms often check for it before filing — a published statement that you are conforming to WCAG 2.1 AA discourages the easiest filings.
How YelloPost AI handles this
We ship WCAG 2.1 AA structural conformance on every build, install the AdaWebPro widget for visitor control, generate the accessibility statement page, and run an automated audit at launch. We also offer ongoing compliance monitoring on Scale tier and as a $199/mo add-on for other tiers. See our Accessibility service for details.
Ready to apply this?
This is the playbook we run on every YelloPost AI build.