The short answer
Whether a private law firm's website is legally required to be accessible is genuinely unsettled — courts increasingly treat business sites as covered by ADA Title III, but there's no federal technical standard for private businesses. The lawsuits proceed regardless, and WCAG 2.1 AA is the practical target. A firm sued over its own inaccessible website is a bad look as well as a cost.
A law firm website should meet WCAG 2.1 AA, the accessibility standard courts lean on, because website accessibility lawsuits keep climbing, there's no safe-harbor rule that makes a private business definitively compliant, and a firm getting sued over its own inaccessible site is not a look you want. It's also, setting the legal risk aside, just good practice that makes your site usable for more clients and cleaner for search engines. This is general information, not legal advice, and the law here is genuinely unsettled, so treat it as a reason to act sensibly rather than a compliance checklist.
Here's what the standard is, how real the risk actually is, and what compliance looks like in practice.
Is a law firm website legally required to be accessible?
The honest answer is that it's unsettled, and that uncertainty is itself the problem. The ADA's Title III covers "public accommodations," and courts have increasingly treated business websites as falling under it, but there's still no official federal technical standard telling a private business exactly what compliant means. So you're in a position where the obligation is plausible, the target is undefined, and the plaintiffs aren't waiting for clarity.
The regulatory picture reinforces the ambiguity. In 2024 the Department of Justice issued a rule setting WCAG 2.1 AA as the standard for state and local governments under Title II, but that rule doesn't cover private businesses, and DOJ isn't expected to issue an equivalent Title III standard any time soon. The result, as legal commentators including the ABA's Business Law Today have laid out, is that private businesses face real litigation exposure without a clear rule to comply with. For a law firm, "the law is unclear so I'll wait" is a weak position to be caught in, because the lawsuits proceed regardless.
How real is the lawsuit risk?
Real and growing. Plaintiffs filed more than 3,000 website accessibility lawsuits under ADA Title III in federal court in 2025, up sharply from the year before, and once state court filings are counted the total runs well past 5,000 a year. Many come from a small number of serial plaintiffs and firms who file in volume against sites with common, detectable barriers.
Data tracked by firms that monitor this litigation, like Seyfarth's ADA Title III team, shows the trend has been climbing for years. And a law firm is a particularly awkward defendant. A demand letter arguing that your own website excludes people with disabilities is both a financial nuisance and a reputational one, especially for a firm whose brand is built on competence and doing things properly. The suits usually settle, which is exactly why they keep getting filed: it's a numbers game for the plaintiff's side, and an inaccessible site is an easy target to spot from the outside.
What standard should you aim for?
WCAG 2.1 Level AA. Even though the ADA itself names no technical standard for private businesses, the Web Content Accessibility Guidelines at 2.1 AA are what courts, settlements, and the DOJ's government rule all treat as the benchmark. Building to that level is the closest thing to a defensible target that exists, and it's a concrete spec your developer can actually work against.
WCAG is maintained as a versioned standard, currently at 2.2, with the earlier 2.1 AA remaining the de-facto legal reference point and 3.0 still on the horizon. You don't need to memorize the guidelines; you need whoever builds and maintains your site to know them and to test against them. Aiming for 2.1 AA, and keeping an eye on 2.2, gives you a real standard to point to if a demand letter ever arrives, which is worth far more than a vague assurance that the site "looks accessible."
What are the common accessibility failures on law firm sites?
A predictable handful, and they're exactly what serial plaintiffs scan for:
- Missing alternate text. Images without descriptive alt text, so screen readers can't convey them.
- Poor color contrast. Light-gray text on white, a common design choice that fails contrast requirements.
- No captions or transcripts. Video and audio without a text equivalent.
- Keyboard traps. Menus, pop-ups, or widgets that can't be navigated without a mouse.
- Screen-reader incompatibility. A page structure that assistive technology can't parse.
- Inaccessible PDFs. Scanned or untagged documents, common on law firm sites, that screen readers can't read.
The unsettling part is how findable these are. A WebAIM analysis of the top million home pages found that around 95% had detectable accessibility failures, which is why automated scanning makes mass filing so easy. Most of these barriers are also fixable, and several overlap with plain good design, like the contrast problems we flag in the five design mistakes that kill conversion on lawyer websites.
Do accessibility overlay widgets fix it?
No, and reaching for one can make things worse. The one-line "accessibility" plugins that promise instant compliance with a floating icon don't actually achieve WCAG conformance, the accessibility community has criticized them heavily, and sites using them have still been sued, sometimes with the overlay itself cited as a barrier. There's no button you can paste in that makes the underlying problems go away.
Treat the overlay pitch the way you'd treat any "one trick fixes everything" claim in this space, including the schema and llms.txt versions of it: skeptically. Real accessibility comes from how the site is built, semantic HTML, proper labels, sufficient contrast, keyboard navigation, text alternatives, not from a script layered on top. That's more work than a widget, and it's the only thing that actually reduces both the barrier and the risk. If a vendor sells you an overlay as compliance, they're selling the easy fake instead of the real fix.
Does accessibility help beyond avoiding lawsuits?
Yes, in two ways that matter to a firm. It makes your site usable for a wider set of clients, including the older visitors who make up a large share of many practices, and it overlaps heavily with the technical foundations that help search and AI engines read your site. Alt text, semantic structure, real text instead of images, and clean navigation serve a screen reader and a crawler alike.
That overlap is worth leaning into, because it means accessibility work isn't a pure compliance cost. The same clean, semantic, text-first construction that makes a site accessible also makes it legible to the engines, which is the exact opposite of the JavaScript-dependent, hard-to-parse construction we describe in why website builders hurt law firm AI search. Build the site well and you get accessibility, usability, and search legibility from the same effort. Accessibility is one more reason the foundation matters, which is the through-line of the full guide to what a law firm website should cost, take, and leave you owning. To see where your current site stands, including the structural issues that touch both accessibility and search, run the free audit, and every site we build is constructed on accessible, semantic foundations through our web design service.
Questions we get about this
-
Is a law firm website legally required to be accessible?
The honest answer is that it's unsettled, and the uncertainty is itself the problem. ADA Title III covers "public accommodations" and courts have increasingly treated business websites as falling under it, but there is still no official federal technical standard telling a private business what compliant means. The Department of Justice's 2024 rule setting WCAG 2.1 AA applies to state and local governments under Title II, not to private businesses. So the obligation is plausible, the target is undefined, and plaintiffs aren't waiting for clarity.
-
How real is the website accessibility lawsuit risk?
Real and growing — more than 3,000 website accessibility suits were filed under ADA Title III in federal court in 2025, and the total runs well past 5,000 a year once state filings are counted. Many come from a small number of serial plaintiffs filing in volume against sites with common, externally detectable barriers, which means being sued has little to do with whether anyone was actually harmed. These cases usually settle, which is precisely why they keep being filed. A law firm is an especially awkward defendant.
-
What accessibility standard should a law firm aim for?
WCAG 2.1 AA, because it's the standard courts and settlements reference even though no rule imposes it on private businesses. Aiming at it gives you a defined target in an area with no official one, and it covers the failures that actually get sites sued: missing text alternatives, poor contrast, unlabeled form fields, and content unreachable by keyboard. You don't need a certification. You need the site to work for someone using a screen reader or a keyboard.
-
Do accessibility overlay widgets make a site compliant?
No, and reaching for one can make things worse. The one-line plugins promising instant compliance don't achieve WCAG conformance, the accessibility community has criticized them heavily, and sites using them have still been sued — sometimes with the overlay itself cited as a barrier. Real accessibility comes from how the site is built: semantic HTML, proper labels, sufficient contrast, keyboard navigation, text alternatives. If a vendor sells you an overlay as compliance, they're selling the easy fake instead of the fix.
