Why Small Law Firm Websites Draw Accessibility Demand Letters, and What Actually Fixes Them

A demand letter about website accessibility tends to arrive without warning. It usually cites the Americans with Disabilities Act, lists a handful of problems a screen reader user supposedly encountered on the site, and proposes a settlement along with a promise to fix the site. For a solo or small firm, the first reaction is often surprise: the website is a brochure, not a store. Why is it a target?

The short answer is that accessibility failures are easy to find with automated tools, and many small business websites, law firm sites included, fail the same basic checks. This post walks through why that exposure exists, which failures show up most often, and what a sensible remediation plan looks like from an operations point of view. It is not legal advice. Whether and how to respond to a specific letter is a question for the firm's own counsel.

Why websites are in scope

Title III of the ADA covers businesses open to the public. The U.S. Department of Justice published guidance in March 2022 stating its consistent position that the ADA's requirements apply to the goods and services public accommodations offer, including those offered on the web. That guidance points to the Web Content Accessibility Guidelines, known as WCAG, as a helpful technical standard.

In 2024 the Department adopted a formal rule for state and local government websites that uses WCAG 2.1 Level AA. There is no matching regulation for private businesses, but WCAG 2.1 AA, and increasingly the newer WCAG 2.2 AA, has become the de facto benchmark that auditors, plaintiffs, and remediation vendors measure against. If a firm wants a target to build toward, that is the one.

The failures that show up again and again

Most findings on small firm sites fall into a short list. Images with no alternative text, or with useless alt text like a file name, leave screen reader users with nothing. Low color contrast, especially light gray text on white or white text over a photo, makes content hard to read for people with low vision. Menus, accordions, and pop-ups that only respond to a mouse lock out anyone navigating by keyboard, and a missing or invisible focus indicator makes it impossible to tell where you are on the page.

Forms are another frequent problem. A contact or intake form whose fields rely on placeholder text instead of real labels, or whose error messages are signaled only by color, is hard or impossible to complete with assistive technology. Finally, PDFs are often overlooked. A scanned brochure, fee schedule, or intake packet posted as an image-only PDF is, to a screen reader, a blank page.

Overlay widgets are not a fix

Accessibility overlay products promise compliance through a single line of script that adds a toolbar to the site. They are appealing because they look like a quick answer. In practice, an overlay does not repair the underlying code. Missing labels, broken keyboard paths, and untagged PDFs remain, and many users of assistive technology already have their own tools configured and find overlays get in the way.

Firms should treat an overlay as, at best, a cosmetic addition and never as a substitute for remediation. A site that relies on one still fails the same automated scans that generate demand letters in the first place.

A practical remediation plan

Start with a baseline. Run an automated scanner across every page template, then do a manual pass: navigate the whole site with only the Tab, Enter, and arrow keys, and listen to key pages with a free screen reader. Automated tools catch only part of the problem, so the manual pass matters. Record each issue with the page, the WCAG criterion, and the fix.

Then fix by template, not by page. On most small firm sites, a handful of templates (header, footer, practice area page, blog post, contact form) generate nearly every page, so repairing those templates resolves most issues at once. Replace image-only PDFs with tagged, accessible versions or with plain web pages. Add accessibility checks to the routine for new content, so a new blog post or attorney photo does not reintroduce problems a month after the cleanup.

Keep evidence. Save the before and after scan reports, the date of each fix, and the vendor or staff member responsible. If a letter does arrive, a documented, ongoing remediation effort gives the firm and its counsel something concrete to work with.

Publish an accessibility statement

An accessibility statement is a short page that names the standard the firm is working toward (for example, WCAG 2.1 or 2.2 Level AA), describes the steps taken, notes any known limitations, and gives visitors a working email address or phone number to report a barrier or request information in another format. It should be accurate, not aspirational. A statement that claims full conformance on a site that plainly does not conform does more harm than good.

The statement also creates a useful operational loop: someone at the firm has to own the inbox, respond to reports, and route fixes to whoever maintains the site.

Where to start

Accessibility is part of the website risk baseline LexAIAdvisors runs for small Florida firms, alongside disclaimers, forms, security headers, and uptime. If you want a prioritized list of what your site fails today and which fixes matter most, request an audit at /audit. Questions about a demand letter you have already received belong with your own counsel.