Web Accessibility Lawsuits at Rehab Centers: WCAG Checklist

Web accessibility lawsuits against private businesses are usually brought under Title III of the Americans with Disabilities Act, and the Department of Justice's web guidance says the ADA's requirements apply to businesses open to the public, including what they offer online. For a treatment center, the same defects that invite a demand letter also stop a prospective admit from finishing your contact form. Sweet Media builds treatment center websites with accessibility checks inside the build process, and this checklist reflects how we prioritize pages. It's general information, not legal advice.

Every lander we ship through our rehab conversion rate optimization service is tested against WCAG AA contrast and keyboard targets.

Can You Get Sued Over Web Accessibility Lawsuits?

Yes. A person with a disability, often someone who uses a screen reader or navigates by keyboard only, can allege that your site denies equal access. Plaintiff firms often send a demand letter first and file suit only if the matter doesn't resolve. One published guide notes that demand letters typically give 30-60 days to respond, while federal lawsuits require a formal answer within 21 days of being served.

A past fix or a past settlement doesn't protect you from the next complaint. Sites change, new forms and plugins get added, and each change can reintroduce a barrier. The same source reports that many businesses that settle once face 2-3 additional lawsuits within 18 months, so treat accessibility as ongoing maintenance, not a one-time project.

What the Law Actually Says

For private businesses, the DOJ guidance says there is no DOJ regulation setting a detailed technical standard, and businesses have flexibility in how they meet the ADA's general requirements. The same guidance points to the Web Content Accessibility Guidelines (WCAG) and the federal Section 508 standards as helpful technical references.

State and local governments face a more specific rule. DOJ's 2024 Title II rule adopted WCAG 2.1 Level AA as the technical standard. A county-run or publicly contracted program may fall under it, and a private center that contracts with a public agency should ask counsel whether the contract brings it in.

Healthcare adds another layer. The HHS Section 504 rule adopted WCAG 2.1 AA for recipients of HHS financial assistance, and a May 2026 interim final rule pushed each compliance date back one year. If your center accepts federal funds, ask counsel which date applies. For everyone else, WCAG 2.1 AA is a practical working target because both federal rules chose it, but it's a target, not a legal safe harbor.

Why Overlay Widgets Aren't a Fix

Overlay widgets sit on top of your code and don't repair missing labels, broken focus order, or unreadable PDFs. As one source puts it, overlays use JavaScript to modify how your site appears to users, but they don't fix issues in your source code. DOJ's guidance says automated checkers and overlays can be helpful tools but need to be used carefully, and that a clean automated report doesn't necessarily mean everything is accessible. Fix the underlying code, and don't rely on a widget as your accessibility plan.

Size isn't a shield either. Industry analysis finds the bulk of filings target small and mid-size service businesses, including clinics, because smaller sites are more likely to carry unresolved, machine-detectable failures. A small center with a basic site and a public intake form presents the same barriers to a screen reader user as a large operator, and a demand letter doesn't scale down with your census.

A WCAG 2.1 AA Checklist for Admissions Pages

Start with the pages that produce admissions, in this order: the contact page, the insurance verification form, the intake form, and the main menu. Those are the pages where a barrier costs you both legal exposure and a lost inquiry.

Forms

Every field needs a programmatic label, not placeholder text alone. Published guidance flags that forms must include clear labels for assistive technology users and text needs a contrast ratio of at least 4.5:1. Error messages should name the field and explain the fix in words, so color is never the only signal. For example, write the word required next to required fields instead of relying on red text. When someone submits a form with a mistake, the error should be announced to screen reader users, not just shown visually.

Keyboard and Focus

Keyboard navigation failures are among the most common findings, because interactive elements can't be accessed without a mouse.

Every field, button, menu and dropdown must work with the Tab, Enter and arrow keys, with a visible focus outline. Menus must open and close by keyboard, and nothing should trap focus. Auditors typically test with screen readers like JAWS or NVDA, keyboard-only navigation, and zoom testing at 200% magnification, and you can start by unplugging the mouse and trying to submit your own insurance form.

Phone Links

Unlabeled controls are a standard failure pattern, since screen readers can't identify what information form fields require, and the same logic applies to a phone button with no name.

Click-to-call links carry urgent mobile inquiries on a treatment center site, so give every tel: link descriptive text such as "Call admissions" and make the tap target large enough to hit with a thumb. An icon-only phone button with no accessible name stays silent to screen readers.

Images, Video, Contrast and Zoom

The most frequently cited failures include images without alternative text, forms that can't be completed by keyboard, missing headings, and low-contrast text.

Images need meaningful alt text, and decorative images should be marked so screen readers skip them. Campus tours and testimonial videos need accurate captions. Body text needs at least a 4.5:1 contrast ratio against its background, and every form must stay usable at 200% browser zoom. Use real headings to structure each page so screen reader users can jump between sections, a point the same analysis ties to WCAG 1.3.1.

Documents and Third-Party Tools

PDFs such as consent forms and intake packets need tags, a logical reading order and real text, not scans. Chat tools, scheduling widgets and embedded insurance verification tools fall under the same expectations, so ask each vendor for conformance documentation before you embed it, and write accessibility into the contract. Automated tools help, but manual audits are essential for full compliance.

What Failed Accessibility Costs Beyond Legal Risk

A form a person can't complete is a lost inquiry, whether or not anyone ever writes a demand letter. Someone using a keyboard or screen reader who hits an unlabeled field leaves, and your admissions team never sees the lead. Accessibility work and conversion work overlap more than most owners expect.

A complaint adds other costs, including remediation under a deadline, attorney fees, and possibly a settlement you didn't budget for. One source notes that the ADA is a fee-shifting statute, so you pay the plaintiff's lawyers as well as the settlement. Costs vary by case, so ask counsel for realistic ranges rather than trusting a headline figure.

Audit Cadence and Evidence to Keep

Run an audit at least once a year and again after any redesign, new form, or plugin change. Start with an automated scan, then test the four key pages by hand with a screen reader and keyboard. One source estimates that automated tools catch about 30% of WCAG violations, and tools like WAVE and Lighthouse are great for automated checks, but manual audits are essential.

Keep dated records of each scan, each fix, and each retest. One published description of defensible evidence lists a dated WCAG audit against Level AA, remediation records, and continuous monitoring. Records don't guarantee you won't receive a complaint, but they document good-faith effort and give counsel something to work with.

Who Owns Accessibility Inside a Treatment Center

Accessibility tends to break within a few months when nobody on staff owns pre-publish sign-off. Marketing adds a landing page, admissions asks for a new form field, and a vendor updates a chat widget, and none of them checks the change with a keyboard or screen reader. Defense lawyers have noted that repeat defendants reveal the gap between one-time responses and ongoing efforts. Name one person, often the marketing lead or the website manager, who signs off on any change to admissions pages and keeps the audit log.

Admissions staff are a useful early warning. If callers mention that the form wouldn't submit or that they couldn't find the phone number, log it and test that page the same week.

Before Any Page Goes Live

Run this list on every admissions page change, drawing on published audit guidance.

• Every form field has a visible, programmatic label
• The whole page works by keyboard with a visible focus outline
• Phone links have descriptive text and a large tap target
• Images have alt text and videos have captions
• Text passes a contrast check and the page works when zoomed
• Embedded tools have vendor conformance documentation on file
• The change is recorded in the accessibility log with a date

How Sweet Media Builds Accessibility Into Web Development

Our web development work treats accessibility as part of admissions infrastructure. We check forms, labels, focus order, contrast and phone links during the build, so problems are fixed before launch instead of after a complaint. We design the intake path with your admissions team in mind, and we keep the audit records in your hands.

What to Do If You Receive a Demand Letter

Don't ignore it and don't reply on your own. Send the letter to an attorney experienced in ADA website matters, preserve your records, and commission an independent audit of the pages named. Response windows are short, since demand letters typically give 30-60 days. Begin remediation promptly, because early fixes with dated documentation give counsel more options.

Frequently Asked Questions

Which WCAG level should a rehab website meet?

WCAG 2.1 AA is a practical target because it's the standard the DOJ Title II rule and the HHS Section 504 rule both adopted. WCAG 2.2 adds further criteria and is a reasonable forward target, and one commentator notes WCAG 2.2 only adds 6 additional considerations to 2.1 AA. Confirm what applies to your center with counsel.

Do overlay widgets protect us?

No. A widget doesn't repair the underlying code, so it can't make a site accessible on its own, and overlays don't fix issues in your source code. DOJ's guidance cautions that automated tools need to be used carefully.

Do insurance forms and chat tools need to be accessible?

Yes. If a visitor must use them to reach your services, they belong in the audit, including third-party tools you embed. Reviewers of these cases stress that manual audits are essential for catching problems in embedded tools.

Does the HHS Section 504 rule apply to every treatment center?

It applies to recipients of HHS financial assistance. Whether your center is a recipient depends on your funding, so ask counsel to confirm.

If you want a clear view of where your admissions pages stand, request a free media audit or book a free strategy call and we'll walk through your forms, phone links, and menus with you.