Key takeaways
- The Justice Department says the ADA applies to the websites of businesses open to the public, and points to WCAG as helpful guidance.
- Automated testing found WCAG failures on 95.9% of the top million home pages in 2026, with an average of 56.1 errors per page.
- More than 1 in 4 US adults have some type of disability, so an inaccessible intake form turns away real prospective clients.
- Six error types account for 96% of detected problems, and most are quick to fix: contrast, alt text, form labels, empty links and buttons, page language.
- Fix intake paths first: the contact form, the phone number, booking and chat.
The legal baseline
The Department of Justice's guidance on web accessibility states that the ADA applies to state and local governments under Title II and to businesses that are open to the public under Title III[1]. It explains that businesses must ensure the goods and services they provide to the public, including those offered on the web, are accessible to people with disabilities[1]. Law firms that serve the public fall squarely within that description.
The same guidance is candid about what it does not do. The Department does not have a regulation setting out detailed web standards for businesses, and businesses currently have flexibility in how they make online content accessible, though they must still comply with the ADA's nondiscrimination and effective communication requirements[1]. It points to the Web Content Accessibility Guidelines (WCAG) and the federal Section 508 standards as helpful technical guidance[1]. In 2024 the Department did publish a rule with specific technical requirements for state and local government websites[1], which shows the direction of travel even though it does not govern private firms.
Pick a named target, such as WCAG 2.2 level AA, write it into your web developer's contract and test against it. A documented standard is the clearest way to show good faith.
Who you are excluding
Accessibility is not a niche concern. The CDC reports that more than 1 in 4 US adults have some type of disability[2]. Cognitive disabilities affect 13.9% of adults, mobility disabilities 12.2%, hearing 6.2% and vision 5.5%[2]. Many prospective clients, including injured people, older adults in estate and elder law matters and veterans seeking benefits, are more likely than average to fall into these groups.
Mobile access adds pressure. About 16% of US adults are smartphone-dependent, with a smartphone but no home broadband[3]. For them, a form that is hard to use with a screen reader or with zoomed text on a phone may be the only route to your firm, and they will simply not finish it.
What testing finds on most sites
WebAIM's 2026 analysis of the top one million home pages found detectable WCAG failures on 95.9% of them, up from 94.8% in 2025, and an average of 56.1 errors per page[4]. Because only automatically detectable failures were counted, WebAIM notes that full conformance was certainly lower than the small share of pages with no detected errors[4]. Six error types made up 96% of all detected errors[4].
Law sites are not exempt. WebAIM's category breakdown grouped 10,829 law, government and politics home pages, which averaged 46.6 errors each, better than average but far from clean[4].
Fix list for intake pages
Start where accessibility failures cost clients: the paths a prospective client uses to reach you. The DOJ guidance lists poor color contrast, missing text alternatives for images, videos without captions, inaccessible forms without labels or clear error messages, and pages that cannot be used with a keyboard among common barriers[1].
| Problem | Where it hurts intake | Fix |
|---|---|---|
| Low contrast text | Pale gray form hints and disclaimers no one can read | Raise text contrast; test with a contrast checker |
| Missing form labels | Screen readers announce 'edit text' with no field name | Give every field a visible, programmatic label |
| Missing alt text | Attorney photos and award badges are skipped or read as file names | Add short, meaningful alt text; mark decorative images as such |
| Empty links and buttons | Icon-only phone, chat or menu buttons have no name | Add accessible names such as 'Call our office' |
| No captions | Video explainers and testimonials exclude deaf visitors | Add accurate captions, not auto-captions left unedited |
| Keyboard traps | Pop-ups and chat widgets cannot be closed without a mouse | Test every page with the Tab key alone |
| Unclear errors | Form rejects a phone number with no explanation | Explain what went wrong in text next to the field |
| Time limits | Booking pages time out mid-entry | Warn before timeouts and allow more time |
Pay special attention to the contact form, since it is often the one page every practice area funnels into. Each field needs a visible label that stays on screen while the visitor types, required fields must be marked in text and not by color alone, and the confirmation message after submitting should be announced to screen reader users. Then try the form yourself with your eyes closed and a screen reader running; it is a quick and humbling test.
Widgets, documents and other blind spots
Many accessibility failures on law firm sites come from things the firm did not build. Chat widgets, booking tools, review carousels, embedded maps and payment pages are supplied by vendors and dropped into the page. Visitors do not know or care whose code it is. Before adding any widget, ask the vendor for its accessibility documentation and test it with a keyboard and a screen reader yourself.
Documents are the other blind spot. Intake questionnaires, fee information sheets and practice-area guides are often posted as scanned PDFs, which screen readers cannot read at all. Publish key information as normal web pages, and where a PDF is unavoidable, create it from a tagged source document rather than a scan.
Finally, accessibility includes the alternatives. The DOJ guidance describes accessible websites as one part of effective communication. A clearly displayed phone number, a text-based way to reach the firm and staff who know how to take a relay call give visitors a route in when something on the site fails.
A practical audit process
List the key journeys
Home page to contact form, practice-area page to phone call, booking a consultation, opening chat, and reading the privacy policy. These get tested first.
Run an automated scan
Use a free checker on each page in those journeys. The DOJ cautions that a clean automated report does not necessarily mean everything is accessible, and suggests pairing automated checkers with a manual check[1].
Test by hand
Complete each journey using only a keyboard, then with a screen reader on a phone and a computer, and with the browser zoomed to twice the normal text size. Note every point where you get stuck.
Fix in order of impact
Anything that blocks submitting a form or finding the phone number comes first, then readability, then everything else.
Publish an accessibility statement
Say what standard you aim for, what you know is not yet fixed, and how visitors can reach you another way, such as by phone, if something does not work.
Build it into changes
Ask your web developer to check accessibility before any new page, form or widget goes live, and re-scan the key journeys every quarter.
Put it in the web developer's contract
Most firms rely on an agency or freelancer for their site, so accessibility has to be written into that relationship. Name the target standard, require testing before launch and after major changes, ask for a short report of what was tested and how, and make fixing accessibility defects part of normal maintenance rather than extra work. Agree who is responsible for third-party widgets the developer installs. These terms cost little to add and avoid arguments later about whether accessibility was ever part of the job.
If a demand letter arrives
Website accessibility demand letters and lawsuits are common enough that a firm should have a plan. Because readers of this guide are lawyers, the legal analysis is yours to make; the operational steps below make that analysis easier:
- Preserve the site as it existed on the dates the letter cites, using an archive or a crawl, before you change anything.
- Test the specific barriers the letter describes and record what you find.
- Start fixing genuine barriers immediately; continuing problems undercut any response.
- Check the contracts with your web developer and website platform for responsibility and indemnity terms.
- Notify your insurer if your policies might respond, and consider outside counsel who handles these claims regularly.
Example: a two-week cleanup
Example (fictional): an elder law firm's website has a contact form with placeholder text instead of labels, light gray disclaimers, a chat pop-up that cannot be closed with the keyboard and attorney videos without captions. Over two weeks, its web developer adds labels and clear error messages, darkens the text, fixes the chat widget's focus order and adds edited captions. The firm publishes an accessibility statement with its phone number. The intake team then tracks form completions from phones each month to see whether the changes made a difference.
Related work
Accessibility, privacy and security often touch the same pages. When you review intake forms, also check what they collect and where it goes using securing intake data in forms and email, review third-party scripts with tracking pixels, cookies and analytics, and make sure the privacy policy is itself readable with assistive technology.
Frequently asked questions
Does the ADA apply to law firm websites?
The Justice Department's guidance says the ADA applies to businesses open to the public, including what they offer on the web. It does not set a detailed technical standard for private businesses, but points to WCAG and Section 508 as helpful guidance.
Which WCAG level should a law firm aim for?
Choose a named WCAG version and level, commonly level AA, and write it into your web developer's contract. Apply it to every page, starting with intake paths.
Will an accessibility overlay or widget make our site compliant?
Automated tools can help find problems, but no add-on fixes missing labels, poor structure or inaccessible third-party widgets by itself. Fix the underlying code and test by hand.
How often should we test our website for accessibility?
Before any new page or form goes live, and at least quarterly for the main intake journeys, with a full review each year.
References
U.S. Department of Justice, Civil Rights Division (2026). Guidance on Web Accessibility and the ADA (opens in a new tab) โ
Centers for Disease Control and Prevention (2024). Disability Impacts All of Us (opens in a new tab) โ
Pew Research Center (2026). Americans' Use of Mobile Devices in 2026 (Mobile Fact Sheet) (opens in a new tab) โ
WebAIM, Utah State University (2026). The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pages (opens in a new tab) โ