Public website and provider search
Location pages, provider directories, insurance details, filters, and contact pathways.
ADA case library
ADA Case Library
Where patient-facing accessibility becomes real legal exposure.
A working library of government guidance, healthcare enforcement, landmark ADA rulings, and settlement patterns. Built for healthcare leaders, counsel, product teams, and procurement teams weighing risk across the full patient journey.
Start with healthcare2025 filings
Federal
8,667
ADA Title III federal suits tracked by Seyfarth in 2025
Useful for showing overall volume, not just website-specific claims.
2024 website suits
Digital
2,452
Website accessibility filings reported in federal court for 2024
A quick benchmark for teams tracking web-only litigation pressure.
DOJ rule
2024
WCAG 2.1 AA
Title II web and mobile app rule for state and local governments
A practical anchor for public-sector teams, procurement, and roadmap timing.
Last reviewed July 2026
DigitxlLink prioritizes government, court, and original settlement materials where available. Lawsuit totals shown above cover different time periods and categories and should not be compared directly.
Healthcare priority
Accessibility risk follows the patient workflow, not just the public homepage
Current federal enforcement and HHS deadlines make the operational scope clear: patient-facing portals, web services, mobile apps, documents, and vendor tools all belong in the accessibility conversation.
Healthcare enforcement
May 7, 2024
U.S. v. Springfield Clinic, LLC
The clinic's patient and records-request portals did not work with screen readers. The settlement requires WCAG 2.1 AA alignment across websites, web content, mobile apps, web-based services, and contractors, plus accessibility ownership, staff training, monitoring, and independent evaluation.
Why it matters: Healthcare exposure extends beyond the marketing website into scheduling, patient records, provider communication, billing, and the third-party systems used to deliver them.
HHS Section 504
May 7, 2026
HHS extends web and mobile accessibility compliance dates
Recipients of HHS funding with 15 or more employees now have until May 11, 2027 to meet the web and mobile requirements. Recipients with fewer than 15 employees now have until May 10, 2028.
Why it matters: The one-year extension provides implementation time, but HHS continues to require accessible programs and effective communication while recipients work toward WCAG 2.1 AA.
What this means for healthcare teams
Appointment scheduling and intake
Calendars, registration, authentication, intake forms, consent, and error recovery.
Patient portals, test results, and billing
Secure records, results, messaging, statements, payments, and account-management workflows.
Mobile apps, telehealth, PDFs, and third-party tools
Vendor platforms remain part of the patient journey and should be included in scoping.
Featured references
Start here if you need the shortest path to the legal signal
These are the links most teams need first: the DOJ's own guidance, the current Title II rule, and the enforcement hub that shows how accessibility failures move from issue backlog to government action.
DOJ guidance
March 18, 2022
Guidance on Web Accessibility and the ADA
The DOJ's baseline explanation of how the ADA applies to web content, with practical references to accessibility principles businesses and public entities should already be thinking about.
Rulemaking
April 8, 2024
New Rule on the Accessibility of Web Content and Mobile Apps
The DOJ fact sheet summarizing the Title II rule. This is the cleanest external explainer for public-sector deadlines, scope, and why WCAG alignment matters operationally.
Enforcement hub
Ongoing
ADA Case Archive and Enforcement Actions
The DOJ case hub is where you can follow settlement activity, statements of interest, and accessible technology enforcement examples without relying on recycled summaries.
Lawsuits and settlements
Cases teams keep citing when digital accessibility becomes a litigation question
This section mixes appellate decisions with DOJ settlement examples. Together they show where courts, regulators, and plaintiffs have focused pressure around websites, apps, online ordering, and transaction flows.
Appellate case
9th Cir. 2019
Robles v. Domino's Pizza, LLC
One of the most cited website accessibility opinions. Frequently referenced when discussing the link between digital barriers and access to goods and services at a physical business.
Supreme Court
2023
Acheson Hotels, LLC v. Laufer
Important for teams tracking tester standing and hotel website litigation. The case ended as moot, but it remains part of the current debate around who can sue and when.
DOJ settlement
March 6, 2014
H&R Block Web and Mobile Accessibility Settlement
A widely cited enforcement example because it covered both the website and mobile apps, along with policy, training, and ongoing monitoring obligations.
DOJ settlement
November 17, 2014
Peapod Settlement Agreement
Useful for showing that digital accessibility enforcement has been tied to ecommerce and online ordering for more than a decade, not just recent overlay debates.
DOJ settlement
November 1, 2021
Rite Aid Vaccine Registration Portal Agreement
A strong example for form-heavy workflows. It shows how inaccessible scheduling and registration experiences can create immediate service barriers, not just abstract compliance issues.
Archive
Reference
Accessible Technology Settlement Archive
A broader historical view of DOJ actions touching web access, kiosks, online services, and procurement-sensitive technology. Useful when building risk narratives for leadership.
Interpretation note
These links are best used as litigation and enforcement signals, not as a substitute for legal advice. Circuit law, settlement posture, and standing issues continue to evolve.
Trend tracking
Resources for teams monitoring where the market is moving now
These links help answer the higher-level questions leadership usually asks: are filings rising or falling, how are courts treating standing, and what does current government attention look like in practice?
Annual data
February 11, 2026
ADA Title III Federal Lawsuit Filings Fall Slightly to 8,667 in 2025
Seyfarth's annual filing report is one of the quickest ways to frame overall ADA litigation volume for boards, insurers, and executive teams.
Web-specific data
April 22, 2025
Federal Court Website Accessibility Lawsuit Filings Continue to Decrease in 2024
Helpful for isolating the website accessibility slice of the broader ADA litigation landscape and showing where digital claims are concentrating geographically.
How we work
How we'd review a patient-facing workflow
Here is how we review patient-facing workflows and document accessibility findings. The examples below are illustrative rather than excerpts from a client audit, but they reflect the standards, format, and code-level recommendations included in an engagement. For healthcare work, the scope follows the patient journey across public pages, forms, portals, mobile apps, and vendor integrations.
Form fields use placeholders, not labels
Inputs with placeholder text and no <label> lose their name on focus, so
screen readers and voice control can't identify the field.
<!-- Before -->
<input placeholder="Email" />
<!-- After -->
<label for="email">Email</label>
<input id="email" name="email" />Body text fails minimum contrast
Light-gray text measured 2.9:1 against white — below the 4.5:1 minimum. We adjust the color token, not the whole palette.
/* Before — 2.9:1 */
color: #b5b5bd;
/* After — 4.6:1 */
color: #6b6b74;Meaningful images have no alt text
Content images shipped with empty or filename alt, so screen readers announce “image” or a filename instead of the meaning.
<!-- Before -->
<img src="chart.png" alt="chart.png">
<!-- After -->
<img src="chart.png"
alt="Q3 revenue up 18% vs Q2">Every fix is re-verified with NVDA (Chrome) and VoiceOver (Safari) before sign-off.
Manual audit
Every key screen driven by keyboard and screen reader (NVDA, VoiceOver) — not just an automated scan, which catches only a fraction of WCAG issues.
Code-level remediation
We fix the source markup and components directly. No overlay widget — the kind courts and plaintiffs increasingly reject.
Retest & evidence
We re-run against WCAG 2.2 AA and hand back a documented ACR / VPAT you can give to counsel or procurement.
Fixed scope, fixed price
You approve a written scope and price before any work starts. No surprise hours, no open-ended retainers.
Healthcare accessibility review
Find out where patients may be getting blocked.
Send us your website or patient-facing workflow. We'll identify the surfaces that should be included in a proper WCAG review and explain the next practical step. No codebase access is required for the initial conversation.
Patient-facing scope
Start with the website or workflow patients use; codebase access can come later if remediation is needed.