Your Law Firm Can Get Sued Over Its Own Website (The Widget Won't Save You)

Your law firm can get sued over its own website, and the statute names you by occupation. 42 U.S.C. § 12181(7)(F) puts “office of an accountant or lawyer” inside the definition of a public accommodation, in the same subsection as a laundromat and a gas station. You are not in a gray zone about whether the ADA reaches your practice. The only argued question has been whether your website counts as part of it, and the plaintiffs’ bar stopped waiting for that answer a long time ago.

I am not a lawyer and none of this is legal advice. I am the person who opens the template and rewrites the markup after somebody else’s demand letter lands on your desk. That is the seat I am writing from.

Why your law firm can get sued over its own website

The defense most principals reach for first is that they meet clients in person, so the site is just a brochure. That argument generally loses, because the site is the gateway to the service. It is where the intake form lives, where the consultation gets booked, and where the fee structure is explained.

Here is the part that should interest a Florida firm specifically. In April 2021 the Eleventh Circuit held in Gil v. Winn-Dixie that websites are not places of public accommodation, rejecting the “nexus” standard the Third and Ninth Circuits use. Firms in Boca Raton read that and relaxed. Then in December 2021 the court vacated its own opinion as moot, because the injunction had expired. The favorable precedent evaporated. What is left in this circuit is open ground, which is exactly the condition serial filers like.

The numbers, as of the 2025 year-end reports

Seyfarth Shaw’s Title III tracker counted 3,117 federal website accessibility lawsuits in 2025, a 27% jump from 2,452 in 2024 and the highest total since 2022. Those filings were 36% of every ADA Title III case in federal court that year.

UsableNet counts state court too. Its 2025 year-end report puts the national total at 5,114 across federal and state venues, with 1,919 of those filed in New York and California state courts. It also found 1,427 suits filed against defendants who had already been sued once, which is 45% of federal filings.

Neither number captures demand letters. Those resolve quietly, in the four and five figures, and nobody publishes them.

Now the supply side. WebAIM tested the top million home pages in February 2026 and found 95.9% had detectable WCAG 2 failures, up from 94.8% the year before, averaging 56.1 distinct errors per page. Low contrast text appeared on 83.9% of pages. Missing alternative text on 53.1%. Missing form labels on 51%. That last one is your intake form.

There is no deadline. That is the point.

You may have been told that accessibility becomes mandatory in April 2027. Whoever told you that is reading the wrong rule, and I want to kill this one carefully because it is the most common piece of bad information circulating in legal marketing right now.

April 2027 is a Title II date. It applies to state and local government entities serving populations of 50,000 or more, and it only exists because the DOJ published an interim final rule on April 20, 2026 pushing the original April 24, 2026 date back by a year. Smaller entities and special districts moved to April 26, 2028. The DOJ’s stated reasons included resource constraints and the limits of generative AI as a remediation tool, which is a federal agency saying out loud that the automated fix does not work yet.

Your private firm is a Title III entity. Title III has no technical regulation and no compliance date. The obligation has been live since 1992. WCAG 2.1 Level AA is the de facto standard courts and demand letters apply, not because a rule says so, but because it is the only yardstick everyone recognizes.

So there is no future date when this starts. There is only the date somebody decides to file.

April 2027 still matters to you in two narrow ways. If your firm touches government work, expect accessibility riders in procurement. And when opposing counsel needs a standard to measure your site against, that rule is the one sitting on the table.

The widget you installed is not a defense

Somebody sold your firm a script tag. One line in the footer, a little icon in the corner, a promise of automatic WCAG conformance for a monthly fee. I have removed these from law firm sites and I will remove them from yours.

On January 3, 2025 the FTC ordered accessiBe to pay $1 million over claims that its accessWidget product could automatically make any website conform to WCAG 2.1 AA. The Commission alleged the widget actually created barriers for users with disabilities on the sites running it, and that the company dressed up paid reviews as independent endorsements. The final order came through in April 2025 and bars those representations absent evidence.

That is the regulator. Here is the litigation record: UsableNet found that 28% of 2025 digital accessibility lawsuits targeted sites that already had an overlay installed, up from 25% in 2024. The widget is not deterring anyone. A plaintiff’s tester can fingerprint a known overlay from the page source in seconds, and a site running one advertises two useful facts at once: somebody here knows they have a problem, and somebody here paid for the cheap answer.

The widget sits on top of the DOM and guesses. It cannot know that the empty link in your attorney bio grid goes to the DUI page. It cannot name your unlabeled form field. It cannot fix keyboard focus order in a custom dropdown, because that order is a consequence of how the component was built. You do not remediate a foundation by painting the walls.

What a real remediation actually touches

This is engineering work on the site itself, and on most firm sites it is a matter of days, not a rebuild. The order below is the order I work in, because each pass makes the next one cheaper.

1. Run an automated scan and accept that it finds maybe a third of it. axe DevTools or Lighthouse in Chrome, free, ten minutes. This catches the six WebAIM categories, which is real ground. It will not catch a heading that lies about the content under it.
2. Fix contrast at the token level, not the page level. Pull your brand colors, compute the ratios, and correct the palette values once. WCAG AA wants 4.5:1 for body text and 3:1 for large text. If you fix contrast page by page you will be doing it forever.
3. Give every image a decision. An informative image gets alt text that carries the same information. A decorative divider gets alt="" so a screen reader skips it. Your attorney headshots get names. “Image of lawyer” is a failure with extra steps.
4. Label every form control. A visible <label> tied to the input by for and id. Not a placeholder. Not an aria-label bolted on to cover a missing one. Your case evaluation form is the single highest-stakes element on the site under both the ADA and your conversion rate.
5. Unplug the mouse and navigate the whole site with Tab. Every interactive element must be reachable, must show a visible focus ring, and must activate with Enter or Space. Practice-area filters and mobile menus break here constantly.
6. Fix the heading hierarchy and name every empty link or button. One h1, then headings that describe structure instead of styling it. An icon-only phone button needs an accessible name. While you are in the template, set <html lang="en">. It is one attribute and 13.5% of the web still gets it wrong.

Then write down what you did and when. A dated remediation record with a named standard is worth considerably more in a response to a demand letter than a subscription receipt for a widget.

One constraint I will not soften. Nothing on this list is a shield against being sued. Anyone can file. What code-level remediation changes is whether the allegations in the complaint are true, and how fast the thing ends.

The same code is what AI agents read

Here is the return nobody sells you, and it is the reason I would do this work even in a world with no plaintiffs’ bar.

When an AI agent visits your site, it does not look at your design. It reads the accessibility tree, the browser’s structured representation of roles and accessible names that was invented for screen readers. Playwright’s MCP server hands the model an ARIA snapshot rather than a screenshot, because a snapshot runs 2 to 5KB against 100KB or more for an image. The open source agent framework browser-use calls page.accessibility.snapshot() as its primary way of seeing a page, and its tagline is literally “make websites accessible for AI agents”.

Read that again with your remediation list next to it. Accessible names on buttons are how an agent knows which control books a consultation. Form labels are how it fills in your intake. Heading structure is how a retrieval system decides where to cut your practice-area page into chunks it can quote. Alt text is content that a text-only crawler can actually index.

The screen reader and the answer engine want the identical thing: a page that says what it is without being looked at. That is the whole argument in machine-first architecture, approached from the legal side instead of the search side. One remediation, two returns. It is the rare piece of work where the defensive spend and the growth spend are the same line item.

Which is also why the widget is worse than useless here. An overlay that reshapes the DOM at runtime is invisible to the crawlers that never execute JavaScript, and disruptive to the agents that do.

If this is the problem

Open your site’s most important practice-area page in Chrome, run Lighthouse, and look at the accessibility score. Then press Tab about fifteen times and watch where the focus ring goes. If you cannot see it, neither can a keyboard user, and neither can the tester who is about to screenshot your page for an exhibit.

Most firms will find their intake form is the worst thing on the site. That is the same form costing you clients who have no disability at all and no intention of suing, which is the argument I make in the conversion checklist. The remediation and the growth work were never separate projects. Your vendors sold them to you separately.

We at Carlos Arias have shipped production AI since 2022. The twenty five years before that in software engineering and digital marketing is how I know which of these fixes belongs in the template and which belongs in the design system, and why no script tag has ever done either one.

If this is your problem, write us at hi@carlosarias.com and tell me what your Lighthouse score was. You will get a straight read from the person who would do the work.