Public website and provider search
Navigation, service pages, location information, physician directories, filters, maps, and contact paths.
- Keyboard and screen reader use
- Search and filter states
- Content structure and contrast
Healthcare accessibility
Make the full patient journey accessible—not only the homepage.
DigitxlLink reviews patient-facing websites, scheduling, intake, portals, billing, telehealth, mobile apps, documents, and vendor-supported workflows. Findings are tied to real tasks, WCAG criteria, and the code or system responsible for the barrier.
No codebase access is required for the initial conversation.
- WCAG 2.2 AA
- Section 504
- ADA-related accessibility
- Web + mobile
What belongs in scope
Four surfaces patients experience as one system.
The review follows the patient task across organizational and vendor boundaries. A public website can pass a scan while scheduling, records, payment, or mobile steps still block assistive-technology users.
Scheduling and intake
Appointment selection, registration, insurance details, consent, validation, confirmation, and error recovery.
- Labels and instructions
- Date pickers and dynamic updates
- Multi-step form completion
Patient portals, results, and billing
Sign-in, MFA, messages, test results, records requests, statements, payment, and session-management states.
- Authenticated workflow access
- Status and error announcements
- Tables, documents, and payments
Mobile, telehealth, PDFs, and vendors
Native apps, embedded tools, video visits, downloadable forms, instructions, and third-party patient services.
- Platform-specific interaction
- Document and media access
- Vendor ownership and escalation
Current healthcare context
Accessibility obligations reach into portals and mobile services.
These government materials help healthcare teams understand why a review should follow the patient workflow beyond marketing pages.
U.S. v. Springfield Clinic, LLC
The Department of Justice alleged that patient and records-request portals did not work properly with screen readers. The settlement covered websites, portals, web-based services, and mobile apps, along with training, accessibility ownership, testing, and independent evaluation.
Why it matters: The patient journey can extend through scheduling, records, communication, and billing systems operated across multiple platforms.
Read the DOJ case materials (opens in a new tab)Extended web and mobile compliance dates
15 or more employeesMay 11, 2027
Fewer than 15 employeesMay 10, 2028
These dates apply to covered recipients of HHS funding under the updated Section 504 rule. Applicability and legal obligations should be confirmed with qualified counsel.
Read the HHS announcement (opens in a new tab)Review model
From patient task to verified fix.
Each issue stays connected to the user impact, affected workflow, WCAG criterion, owner, fix direction, and retest outcome. The result is an implementation record—not a blanket legal conclusion.
Planning range
Audit-only work is typically planned for 5–10 business days. Audit plus approved remediation and validation is commonly planned for 2–4 weeks. The written scope controls.
- 01
Map the patient journey
Identify public pages, authenticated steps, vendor transitions, documents, mobile surfaces, and the highest-impact tasks.
- 02
Test critical workflows
Combine automated checks with keyboard, screen reader, zoom, responsive, form, content, and component-state review.
- 03
Assign and remediate
Route findings to the internal team, DigitxlLink, or a third-party vendor with evidence and practical fix guidance.
- 04
Retest and document
Record resolved, partial, open, regressed, and vendor-blocked findings against the tested release and scope.
Engagement outputs
Useful to clinical, digital, engineering, and compliance teams.
Prioritized finding log
Severity, reproduction steps, affected users, screenshots, WCAG mapping, and workflow ownership.
Code and vendor guidance
Developer-ready direction for internal components plus clear escalation notes for third-party systems.
Scope-aware status record
Retest outcomes, tested version, known limitations, open items, and recommended next actions.
Maintenance plan
Ownership, release checkpoints, issue reporting, training priorities, and recurring review recommendations.
Scope boundaries stay explicit.
Pricing shown elsewhere for up to five core pages or templates does not automatically include authenticated portals, native mobile apps, PDF remediation, video captioning, telehealth platforms, or third-party widgets. Those surfaces are included only when named in the written scope.
Start with the workflow
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.
Request an accessibility risk review
No codebase access required for the initial conversation.
Last reviewed July 2026. DigitxlLink prioritizes government, court, standards-body, and original settlement materials where available.
DigitxlLink provides technical accessibility services, not legal advice. An audit, remediation engagement, validation record, or ACR does not guarantee legal compliance or protection from claims. See the service disclaimer.