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
For HHS-funded healthcare organizations
Prepare patient-facing systems for the current Section 504 web and mobile deadline.
DigitxlLink maps the digital path patients use to find care, schedule, complete intake, access records, pay bills, and attend telehealth visits—then combines manual WCAG testing, code-level remediation, assistive-technology validation, and review-ready evidence across the systems responsible for that journey.
Current HHS date for covered 15+ employee recipients: May 11, 2027. Technical accessibility services—not legal advice.
- WCAG 2.1 AA regulatory mapping
- WCAG 2.2 AA enhanced benchmark
- Web + mobile
- No overlay-dependent remediation
What belongs in scope
Patients experience four systems as one journey.
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. The rule’s web and mobile provisions use WCAG 2.1 Level AA. Applicability and legal obligations should be confirmed with qualified counsel.
Read the HHS announcement (opens in a new tab)Fixed-scope starting point
Section 504 readiness assessment
Start with one priority patient workflow and leave with a practical record your compliance, IT, operations, and vendor teams can use.
$1,500fixed scope
- Up to five priority pages or application screens
- Manual findings tied to patient impact and WCAG criteria
- System and ownership map across internal and vendor teams
- Prioritized remediation roadmap and stakeholder walkthrough
Apply the full assessment fee to a $4,500 remediation pilot started within 30 days.
Request the readiness assessment Final scope is confirmed in writing before work begins.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.
Project handoff
Clear records for the work that follows.
We organize the handoff around the people who need to act: engineering, vendor management, compliance, and operations.
Priorities, reproduction steps, screenshots, affected workflow, owner, and WCAG reference.
Code guidance for internal teams and concise escalation notes for vendor-owned systems.
Pass, partial, open, regressed, and blocked statuses tied to the tested release.
Release checkpoints, ownership, training needs, and follow-up recommendations.
The written scope controls.
Portal work, native apps, PDFs, captions, telehealth, and third-party tools are included only when they are named in the scope. Page or template limits in standard pricing do not automatically extend to those systems.
Review notes
Sources and boundaries
Reviewed August 2026. We prioritize government, court, standards-body, and original settlement materials.
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.
Read the service disclaimerStart with one patient workflow
Turn the Section 504 timeline into an owned remediation plan.
Share the website, portal, form, or mobile flow you want reviewed. We’ll map the surfaces, owners, verified barriers, and next practical step before any codebase access is needed.
Request a Section 504 readiness assessment
Initial scoping conversation · no code access required
