A blind person in Chicago wants to book a dental check-up. She opens the practice’s website with her screen reader, finds the appointment form, and gets stuck: the date and time controls cannot be reached with the Tab key, and nothing tells her whether a checkbox is required. A few months later the practice receives a demand letter asking for $15,000. That is the story told, from both sides, in the court filings of a case brought in January 2026, and it is far from the only one.
Defence law firms are warning that dental and other health care practices are a growing target for website accessibility suits. We read the dockets to see what that looks like in the court record. Here is what the complaints allege, which laws apply to a practice website, and the five things that most often go wrong.
A note before the detail: the cases below are allegations, none has produced a ruling on whether a website broke the law, and this post is not legal advice.
At a glance
- Who is suing: blind people who use screen readers and say they could not book an appointment or use a form, usually in federal class actions under Title III of the Americans with Disabilities Act.
- The ADA hook: Title III lists the “professional office of a health care provider” as a public accommodation (42 U.S.C. 12181(7)(F)).
- The second rule: practices receiving federal financial assistance from HHS must meet WCAG 2.1 AA under Section 504 from 11 May 2027 (15 or more employees) or 10 May 2028 (fewer than 15).
- How big is the trend? smaller than the warnings suggest. UsableNet’s 2025 year-end report, which our lawsuit tracker uses, put healthcare at about 2.5% of digital accessibility suits. But one plaintiff can sue several practices in a day.
What the complaints say
Three dental complaints, one day, one barrier list
On 1 July 2026 one blind New Jersey resident, through one law firm, filed class actions in the District of New Jersey against three dental businesses (2:26-cv-08035, 08038 and 08039). Each says he last visited the practice’s website on 19 July 2025, almost a year earlier, to book a dental check-up, and could not do it with his screen reader.
The barrier list is word for word the same in all three: missing alt text, hidden elements, badly formatted lists, unannounced pop-ups, unclear labels, and actions that need a mouse. The same list appears in his complaint against a restaurant filed that day (2:26-cv-08042). Each asks for an injunction requiring a consultant, regular WCAG 2.1 testing, training and an accessibility policy, plus nominal damages and fees.
Boilerplate does not make the barriers imaginary; each is a common, real failure. But identical wording and a shared visit date suggest suits produced at volume from a template. In one case the practice answered in late August 2026 and the case continues.
The Chicago case: a demand letter, a fast fix and an overlay
Anderson v. American Dental Associates, Ltd. was filed in the Northern District of Illinois on 30 January 2026. The complaint lists eight problems the blind plaintiff says she met with JAWS, including controls unreachable by Tab, a skip link that did not move focus, a logo link with no text alternative, links opening new windows without warning, and a form that did not say whether a checkbox was required (paragraph 35).
The practice’s motion to dismiss gives its side. It says a demand letter arrived on 15 December 2025 asking for $15,000 and naming three barriers, including date and time controls that could not be focused with Tab. A consultant began fixes on 8 January 2026. The day before the complaint was served, the practice also deployed accessiBe’s accessWidget overlay, whose report counted 500 remediations. It published an accessibility statement on 8 February and argued the case was moot.
The plaintiff replied that follow-up testing found barriers still present, and that the evidence of remediation came largely from the overlay vendor’s own report. She cited the Federal Trade Commission’s 2025 order requiring accessiBe to pay $1 million and barring it from claiming, without evidence, that its tools make any website WCAG compliant. The court never ruled. On 2 September 2026 the plaintiff voluntarily dismissed the case without prejudice; the docket does not say why.
Two lessons. The practice responded quickly and still spent seven months in federal court. And the other side did not accept an overlay vendor’s report as proof of a fix. Our overlay guide explains the wider problem.
Which laws apply to a practice website
ADA Title III
Title III bans disability discrimination by places of public accommodation, and its list expressly includes the “professional office of a health care provider.” Courts have long split on whether websites count, but a practice with a physical office will struggle to argue its booking site is separate from the office it books you into. Even the dental practice’s own brief in Chicago quoted a 1999 Seventh Circuit opinion naming a dentist’s office and a website side by side.
No Justice Department regulation sets a technical standard for private websites. The department’s March 2022 guidance says businesses have flexibility in how they comply but must still make what they offer online accessible, and points to WCAG. The complaints above measure sites against WCAG 2.1 or 2.2.
Private plaintiffs can get an injunction and, if they prevail, reasonable attorney’s fees (42 U.S.C. 12188(a) and 12205). The ADA gives them no damages, though some state laws do, and the complaints above still ask for nominal or compensatory damages.
Section 504 and the HHS web rule
Section 504 of the Rehabilitation Act covers programs receiving federal financial assistance. HHS’s May 2024 rule (45 CFR part 84, subpart I) requires its recipients’ web content and mobile apps to meet WCAG 2.1 Level A and AA, including content provided “through contractual, licensing, or other arrangements.” HHS says its recipients include health care providers of all sizes, down to small local clinics, and the 2024 rule notes that state Medicaid programs are covered. Whether your practice’s payments make it a recipient is a question for counsel.
An interim final rule effective 7 May 2026 moved the dates to 11 May 2027 (15 or more employees) and 10 May 2028 (fewer). The later date covers most practices: HHS noted that 52% of firms providing health care services, including doctors and dentists, have fewer than five employees and another 20.4% have five to nine. HHS said the delay does not remove other Section 504 duties, such as reasonable modifications, and that it may revisit the rule’s substance. More in our Section 504 deadline guide.
Two details matter for practices. A separate accessible version of web content is allowed only where the main content cannot be made accessible for technical or legal reasons (45 CFR 84.86). And HHS dropped a proposed exception for linked third-party content, so a booking or intake tool you send patients to is not automatically outside the rule.
Section 1557 of the Affordable Care Act
The ACA’s nondiscrimination rule requires health programs delivered through technology to be accessible, and says recipients’ websites and apps must meet Section 504 requirements (45 CFR 92.204). It points back to the same obligations rather than adding a new standard.
The five places practice websites most often fail
HHS’s own example fits: a clinic that has patients book online must make that booking usable by a blind patient with a screen reader.
1. The online booking widget
This is the heart of every dental complaint we read. Date pickers and time grids built from clickable divs cannot be reached by keyboard, and icon buttons have no name. Test the whole flow, from choosing a service to the confirmation, with only a keyboard and then a screen reader.
- WCAG 2.1 AA criteria: 2.1.1 Keyboard, 4.1.2 Name, Role, Value.
2. Patient intake forms and PDFs
New patient forms are often scanned PDFs, or web forms with placeholder text instead of labels, so a screen reader announces a row of unnamed boxes. Mark required fields in text, not only with a red asterisk. Under the HHS rule, older documents are exempt only if they are not currently used to take part in a program, and an intake form is used for exactly that.
- WCAG 2.1 AA criteria: 1.3.1 Info and Relationships, 3.3.2 Labels or Instructions.
3. Patient portal links
The portal link is often a logo with no text alternative or a vague “Click here,” sometimes opening a new window without warning, as alleged in Chicago. The HHS rule exempts individual documents behind a login, such as a patient’s own statement, but not the portal’s pages when the practice provides it through a contract.
- WCAG 2.1 AA criteria: 2.4.4 Link Purpose (In Context), 1.1.1 Non-text Content.
4. Offers and key information in images
Whitening specials, new patient offers and office hours are often posted as banner images. Without a text alternative a screen reader user gets nothing, and low vision users cannot resize or recolour the text. Put the offer in real text.
- WCAG 2.1 AA criteria: 1.1.1 Non-text Content, 1.4.5 Images of Text.
5. CAPTCHA, phone-only contact and skipped navigation
An image CAPTCHA with no alternative blocks blind users entirely; the New Jersey complaints list unlabelled CAPTCHA prompts among common barriers. The opposite mistake, a contact page with only a phone number, shuts out many deaf patients. And menus with no working skip link force keyboard users through every link on every page, another Chicago allegation.
- WCAG 2.1 AA criteria: 1.1.1 Non-text Content (CAPTCHA), 3.3.2 Labels or Instructions, 2.4.1 Bypass Blocks.
Your booking vendor is still your problem
Most practices license their scheduling, forms and portal. That does not move the legal risk. In Chicago, one of the three barriers in the demand letter was in the appointment date and time controls, and the letter and lawsuit went to the practice. Under the HHS rule, content provided through a contract or licence is yours to make accessible.
Before you sign or renew with a booking, intake or portal vendor:
- Ask for an Accessibility Conformance Report (ACR). A completed VPAT stating, criterion by criterion, how the product meets WCAG 2.1 or 2.2 AA, and who tested it when. “ADA compliant” on a sales sheet is not an ACR.
- Put it in the contract. Require WCAG 2.1 AA conformance, a timeline for fixing reported issues, and cooperation if you receive a complaint or demand letter.
- Test it yourself. Book a fake appointment using only a keyboard. If you cannot, neither can your patients.
What to do this month
- Scan the homepage, booking, contact and intake pages, then test booking by keyboard and screen reader. Automated tools catch only part of the problems.
- Fix booking first, then replace image-only offers and scanned forms.
- Publish an accessibility statement with a monitored email and phone number.
- If you are an HHS recipient, plan for WCAG 2.1 AA by your Section 504 date. If a demand letter arrives, call counsel before buying a quick fix.
Our free tools and guides cover each of these steps:
- Scan a practice page with the URL accessibility auditor.
- See what a full manual review covers in our sample audit report.
- Fix booking and intake forms with the accessible forms guide.
- Make patient documents usable with our PDF accessibility guide.
- Learn how to read a vendor’s ACR in our VPAT and ACR guide.
- See how the ADA applies to websites on our ADA compliance page.
- Read the decisions that shaped website coverage in our ADA case law reference.
- Follow filing numbers by year and industry in the accessibility lawsuit tracker.
Sources
- CourtListener: Docket, Anderson v. American Dental Associates, Ltd., No. 1:26-cv-01084 (N.D. Ill.)
- US District Court, N.D. Ill.: Class Action Complaint, Anderson v. American Dental Associates (filed 30 January 2026)
- US District Court, N.D. Ill.: Memorandum in Support of Defendant’s Motion to Dismiss, Anderson v. American Dental Associates (27 February 2026)
- US District Court, N.D. Ill.: Plaintiff’s Memorandum in Opposition to Motion to Dismiss, Anderson v. American Dental Associates (23 March 2026)
- CourtListener: Docket, No. 2:26-cv-08038 (D.N.J., filed 1 July 2026)
- US District Court, D.N.J.: Class Action Complaint, No. 2:26-cv-08038 (1 July 2026)
- US District Court, D.N.J.: Class Action Complaint, No. 2:26-cv-08035 (1 July 2026)
- US District Court, D.N.J.: Class Action Complaint, No. 2:26-cv-08039 (1 July 2026)
- US District Court, D.N.J.: Class Action Complaint, No. 2:26-cv-08042 (1 July 2026)
- Legal Information Institute: 42 U.S.C. 12181, Definitions (public accommodations)
- Legal Information Institute: 42 U.S.C. 12188, Enforcement
- Legal Information Institute: 42 U.S.C. 12205, Attorney’s fees
- US Department of Justice: Guidance on Web Accessibility and the ADA (18 March 2022)
- eCFR: 45 CFR 84.84, Requirements for web and mobile accessibility
- eCFR: 45 CFR 84.85, Exceptions
- eCFR: 45 CFR 92.204, Accessibility of information and communication technology
- Federal Register: HHS interim final rule extending Section 504 web and mobile compliance dates, 91 FR 25496 (11 May 2026)
- Federal Register: HHS final rule, Nondiscrimination on the Basis of Disability in Programs or Activities Receiving Federal Financial Assistance, 89 FR 40066 (9 May 2024)
- Federal Trade Commission: FTC Approves Final Order Requiring accessiBe to Pay $1 Million (22 April 2025)