What ADA website lawsuits look like from the inside
Our studio provides expert witness analysis in federal web accessibility cases. That seat teaches you how sites actually end up in court — and what genuinely keeps them out.
July 14, 2026
2 minutes
The complaint is rarely a surprise
When an accessibility lawsuit lands, the barriers named in the complaint are almost never exotic. They are the first things any screen-reader user hits in the first five minutes: buttons with no accessible name, images that carry meaning but no alt text, forms that cannot be completed with a keyboard, menus and modals that trap focus or never receive it.
That is the uncomfortable part, and also the hopeful part. The failures that create legal exposure are the same failures a basic audit finds. Organizations rarely get sued over an obscure WCAG criterion; they get sued because nobody ever tried to use the site the way a blind customer has to.
What an expert actually examines
Expert analysis in these cases is not a scan tool printout. It means using the site the way the plaintiff does: with a screen reader, with a keyboard alone, with the page structure the browser actually exposes rather than the one the design implies. Automated checkers catch a fraction of what matters; the rest is judgment about whether a real person can complete real tasks.
History matters too. Whether the organization audited the site, when barriers were reported, and what happened next all become part of the record. A documented remediation effort reads very differently in court than years of silence.
A widget is not a shield
Accessibility overlays and toolbars can add genuine conveniences — contrast toggles, text sizing, reading aids. What they cannot do is repair the underlying code. Accessible names, roles, focus order, and document structure live in the markup, and that is exactly where expert analysis looks. If the code underneath is broken, a widget on top of it changes nothing about what a screen reader encounters or what a complaint will allege.
Our position is the same one we build to: use a widget for the conveniences if you like, but conformance has to be structural. There is no bolt-on substitute for semantic, tested code.
What actually protects you
The organizations that stay out of court do unglamorous things consistently. They build with semantic structure from the start instead of retrofitting. They test with actual assistive technology — VoiceOver, TalkBack, NVDA — not just automated tools. They document the work: audits, VPATs, remediation logs. And they treat accessibility as part of the definition of done, not a launch-week scramble.
We have delivered more than 200 accessibility audits and VPATs, and the pattern holds every time: fixing accessibility at the design stage costs a fraction of fixing it under a demand letter. The cheapest time to take this seriously is before anyone makes you.