Almost every website accessibility lawsuit starts with a problem you could have found on your own in an afternoon.
That is the uncomfortable truth behind the demand letters landing in Tampa mailboxes. Florida is one of the most active states for these claims, and we take these calls regularly, often from business owners holding a letter they didn’t see coming. The barriers named in those letters are rarely exotic. Missing image descriptions. A checkout that traps keyboard users. Gray text on a white background. Fixable things, found late.
Plain talk about what’s going on, what a demand letter actually contains, and what to do about it.
Why are accessibility lawsuits surging?
Plaintiffs’ firms argue, and many courts have accepted, that business websites are places of public accommodation under the ADA, and there is no official certification that declares a private-sector site compliant. That combination lets those firms test sites at scale and send letters over the same recurring barriers, again and again.
The de facto technical standard is WCAG, the Web Content Accessibility Guidelines. If you want the full picture of how the ADA and WCAG fit together, we wrote a separate explainer on ADA website compliance and WCAG. The short version: WCAG defines testable success criteria, and both courts and settlement agreements keep pointing to it as the benchmark.
Here’s the part that gets lost in the legal noise: those criteria describe real barriers for real customers, letters or no letters. A meaningful share of adults live with some form of disability, whether visual, motor, auditory, or cognitive. An inaccessible site is quietly turning them away long before any lawyer gets involved.
What triggers an accessibility lawsuit?
Most claims trace back to a handful of recurring failures: images without text alternatives, forms that screen readers can’t navigate, buttons and menus that don’t work by keyboard, text contrast below WCAG minimums, and video without captions. Plaintiffs’ firms find these with automated scanners, which means a public site can be evaluated as a target without anyone ever contacting you.
A few patterns raise the odds of getting picked:
- You transact online. Restaurants with online ordering, retail stores with checkout, medical practices with appointment booking. When a barrier blocks a purchase or a reservation, the claim writes itself.
- Your site fails the obvious automated checks. Scanners catch missing alt text, unlabeled form fields, and contrast failures instantly. Sites that fail loudly on a scan invite a closer manual look.
- You’re in a heavily filed industry. Hospitality, e-commerce, healthcare, and real estate come up constantly in Florida filings. Tampa’s restaurant and service-business economy sits squarely in that zone.
None of this means a clean automated scan makes you safe. Plenty of barriers only show up in manual testing with a keyboard and a screen reader. But the reverse is reliable: a site that fails the automated basics is discoverable by anyone who cares to look, and some people are paid to look.
What is actually in a demand letter?
A typical web accessibility demand letter identifies a plaintiff who claims they tried to use your site and couldn’t, alleges a violation of ADA Title III (and sometimes Florida state law), lists specific barriers, and demands remediation plus attorney’s fees. The structure is consistent enough that once you’ve read a few, you can map any new one in minutes.
The usual anatomy, section by section:
- The plaintiff and the visit. A named individual with a disability states they visited your site on a rough date and were unable to complete something: read a menu, book an appointment, buy a product.
- The legal theory. The letter frames your website as a place of public accommodation under the ADA, often citing case law and sometimes stacking a state-law claim on top.
- The barrier list. A rundown of specific failures, frequently pulled from an automated scan and phrased in WCAG language. This list is the technical core of the letter and the part an engineer can actually verify.
- The demand. Remediate the site to a named WCAG level, enter a settlement agreement, and pay the plaintiff’s attorney’s fees. The ADA itself doesn’t award damages to plaintiffs in these cases, so fees and settlement terms carry the economic weight.
- The deadline. A response window, after which the letter threatens a filed lawsuit.
Two things matter when you’re holding one. First, the barrier list is checkable. Some items are usually accurate, some are outdated, and some are boilerplate that doesn’t match your site at all. Documenting which is which gives your attorney something concrete to work with. Second, speed of documented remediation tends to shape how these resolve. A defendant who can show a scoped audit and fixes in progress is negotiating from a different position than one who ignored the letter for a month.
What should you do if you receive one?
Two moves, in parallel: talk to your attorney about the legal side, and start documented remediation of the actual barriers. We do the second part: a rapid audit that scopes the genuine issues, a prioritized fix plan your counsel can reference, and hands-on remediation of the highest-risk items fast. We fix websites; we don’t give legal advice. The pairing of lawyer plus engineers is the point.
One warning from the trenches: accessibility overlay widgets, the one-line-of-JavaScript “compliance” products, have not stopped businesses from receiving letters, and some complaints now cite the overlays themselves as barriers. Real remediation happens in your site’s actual code and content. There is no shortcut that survives a manual screen reader test.
Whatever you do, don’t quietly rebuild the site and hope the problem disappears. Undocumented changes made after a letter arrives can complicate the legal side. Coordinate the engineering work with counsel from day one.
How do you avoid a letter in the first place?
An audit is cheap compared to a letter. A scoped accessibility review finds the same barriers a plaintiff’s firm would find, except you get the list privately, with time to fix things on your own schedule and budget.
Building accessibly from the start costs almost nothing extra, because it’s mostly competent engineering: semantic markup, keyboard support, honest contrast, described images, captioned video. Every site we ship through our web design and development work is built to WCAG because it’s the same thing as building it well. Retrofitting an old site takes more effort, but the priority order is well understood: fix the flows where customers transact first, then work outward.
Details on our accessibility and remediation service are on the service page, including priority scheduling for businesses in active disputes.
Common questions about demand letters
Does an accessibility overlay widget protect me from lawsuits? No. Businesses running overlays continue to receive demand letters, and some complaints name the overlay itself as a barrier. Remediation in your site’s real code and content is the only approach that holds up to manual testing.
Is there an official ADA certification for websites? No. There is no government seal or certificate for private-sector sites. WCAG conformance, verified by audit and maintained over time, is the closest thing to a defensible standard, and it’s what settlement agreements typically require.
I got a letter but my site was built recently. Can it still have violations? Yes. A recent build date says nothing about accessibility. Plenty of new sites ship with missing alt text, unlabeled forms, and contrast failures. Verify the letter’s barrier list against the actual site before assuming either side is right.
How long does remediation take? It depends on the size of the site and the depth of the problems. High-risk barriers in checkout, booking, and contact flows can often move fast; a full-site pass to WCAG conformance takes longer and runs in prioritized phases. A scoped audit gives you a real timeline instead of a guess.