Paper Boat Media / Healthcare & patient access
05 / 05
Care starts
with access.
HHS Section 504 website accessibility, the revised deadlines and the patient journeys that need attention.
01
A patient should be able to reach the care you offer.
A healthcare website can explain a practice beautifully and still make it difficult to become a patient. The appointment form may be hard to navigate. A portal may lose context during sign-in. Instructions may arrive as an inaccessible document. A person trying to correct an error may have to start again.
These problems cross the usual boundaries between marketing, IT, compliance and operations. The patient experiences one journey, even when the organization sees four systems and three vendors.
The HHS Section 504 web accessibility rule requires covered recipients of HHS financial assistance to meet WCAG 2.1 Level AA for covered web content and mobile apps, subject to the rule’s provisions. HHS extended the technical compliance dates in 2026: May 11, 2027 for recipients with 15 or more employees, and May 10, 2028 for recipients with fewer than 15. The May 2026 extension confirms those dates and the employee threshold.
This guide explains how I would translate a confirmed obligation into a practical implementation plan. It does not determine whether a particular entity receives covered funding or provide legal advice. Those decisions should involve the organization’s compliance lead and counsel.
02
Confirm coverage before assigning the deadline.
Start with the legal entity and its funding arrangements. Do not decide applicability from the size of the practice, its specialty or whether its website accepts payments.
HHS defines recipients broadly, including entities receiving assistance directly or through another recipient. The relevant program or activity and organizational structure matter. A health system, independent practice, human-services organization or research institution may need a different applicability analysis.
Ask the compliance lead to document the funding basis and employee count used. If the organization has affiliates, acquired practices or shared systems, clarify which entities and services the work covers. A site branded as one organization may serve several legal entities.
| Covered recipient category | Revised technical compliance date | What the project team needs |
|---|---|---|
| 15 or more employees | May 11, 2027 | Confirmed coverage and the employee-count basis |
| Fewer than 15 employees | May 10, 2028 | Confirmed coverage and the employee-count basis |
These are the HHS dates. A public healthcare organization may also have ADA Title II obligations with a different schedule. Other laws or contractual requirements may apply as well. Keep a requirements register rather than assuming one article resolves every obligation.
The HHS extension announcement also emphasizes that existing accessibility obligations continue. The new date is not a reason to leave a patient without a usable way to obtain information or services now.
03
Map the patient journey before counting pages.
An inventory should begin with the actions a patient needs to complete. That gives the technical review a practical purpose and helps the organization find systems outside the main website.
Map provider discovery, location selection, appointment requests, registration, intake, portal access, telehealth entry, payment and follow-up information. Include the forms and documents sent during those steps. Identify the point at which each vendor or department becomes responsible.
| Patient task | Assets to include | Ownership question |
|---|---|---|
| Find the right care | Provider profiles, service pages, search and location information | Who approves the content and navigation? |
| Request an appointment | Scheduling controls, forms, confirmation and error states | Which team and vendor can repair the process? |
| Prepare for a visit | Intake forms, consent materials and preparation instructions | Who maintains the source documents? |
| Use the portal | Sign-in, recovery, messages and relevant documents | Who owns the vendor relationship and deployed configuration? |
| Join a virtual visit | Entry instructions, supported controls and assistance route | Who coordinates technical support and care delivery? |
| Understand next steps | Follow-up information, billing and patient communications | Who checks the format and responds to access requests? |
Do not collect real patient details merely to build the inventory. The first pass can describe systems, tasks and ownership without exposing protected information. Testing access and data handling should be agreed with the appropriate privacy and security staff.
04
Give forms the same attention as the homepage.
Patient forms contain decisions, instructions and information that must stay associated with the correct control. A visually neat layout can still be confusing when a person navigates it with assistive technology.
I would review field labels, required indicators, grouped questions, input instructions and error recovery. If a patient enters a date in the wrong format, the form should help them locate and correct the issue. It should not simply change a border color and leave them to search.
Multi-step forms need a complete review. Can someone understand where they are in the process? Is previously supplied information handled sensibly? What happens when they go back? Does the system preserve entered information where appropriate? Can they tell whether the submission succeeded?
Timeouts and session expiration deserve attention. The evaluation should consider the applicable requirements and actual security constraints rather than treating every timeout as either acceptable or prohibited. Include the people responsible for the form’s security and business rules in that discussion.
Use a test environment and synthetic records where available. If controlled production testing is necessary, agree on the procedure first. Accessibility work should not create unwanted appointments, accidental charges or unnecessary exposure of patient information.
05
The portal is part of the experience.
A practice may have limited control over a patient portal’s code, but it still needs to understand where patients encounter barriers and how those issues will be handled.
Ask the vendor for current accessibility evidence relevant to the product version and configuration in use. Review the scope of any conformance report. Identify known issues and request an explanation of the repair process.
Then test the relevant patient tasks. A general vendor statement does not tell you whether your sign-in instructions, embedded configuration or chosen workflow works as deployed. The path from the practice’s website into the portal should be included in the review.
Document each vendor finding with reproducible steps, the affected task and the test conditions. Assign an internal owner to follow up. If a repair will take time, coordinate an appropriate assistance process while the underlying issue is addressed.
The escalation should reach someone with authority over the relationship. Repeatedly sending the same report to a general support inbox may create activity without progress. Procurement, IT and the service owner may need to work together on the next decision.
06
Documents need source files and a publication owner.
Healthcare organizations often maintain a mixture of downloadable forms, instructions, patient education materials and automatically generated documents. The formats and sources vary, which makes a simple file count an incomplete measure of the work.
Identify documents used in current care access first. Record the source file, purpose, owner, publication location and update frequency. Determine whether a web page or accessible form would serve the patient better than a static download.
For documents that remain necessary, inspect structure and actual use. A file can contain selectable text yet have confusing reading order, poor table structure or unclear links. A scanned image may need substantially different work from a properly authored source document.
Avoid creating a maintenance arrangement in which every update requires someone to repair the same avoidable defects. Improve the source templates and teach the people who use them. Verify the exported result, because the source application and export process can affect the final file.
Clinical content should remain under the appropriate clinical review. The accessibility team can improve format and presentation, but should not independently alter medical instructions, consent language or the meaning of patient education material.
07
Understand the exceptions without overextending them.
The regulation includes limited exceptions for categories such as archived content, certain preexisting documents, specified third-party content, certain individualized password-protected documents and preexisting social media posts. The conditions matter. A document used to obtain or participate in a current service cannot simply be treated as exempt because it was created years ago.
Use the current regulation when making the decision. A compliance or legal lead should review the factual basis for an exception and the organization’s continuing duties to an individual who needs accessible information.
I would keep a record containing the asset, its purpose, the exception considered, the reviewer and the assistance process. That makes the decision reviewable and helps the team notice when the facts change.
For example, an old informational document might later be adopted as a required intake attachment. Its role has changed, so the earlier assessment needs another look. Accessibility governance should be able to detect that kind of ordinary operational change.
08
Web accessibility and kiosk access are related, but different assignments.
The HHS provisions also address kiosks. A check-in device in the lobby is a different environment from a browser-based form at home. The HHS section-by-section guidance describes access obligations for kiosk use and the possibility of appropriate procedures that provide access without using an inaccessible kiosk.
Do not assume a website plug-in repairs a physical check-in system. Inventory the kiosk and involve its vendor, facility staff and the compliance lead. Assess the actual process a patient follows when the device is not usable for them.
Staff need to know how to help without making the patient repeatedly explain the problem. The assistance route should be practical during ordinary operating hours and busy periods. Technical improvement and respectful service need to be coordinated.
Keep the deadlines and technical requirements of different accessibility provisions distinct. A web-content deadline should not be casually applied to every piece of medical equipment or every obligation in the broader Section 504 rule.
09
Software can support the work, but it cannot own the program.
An accessibility widget on a public website does not automatically extend into a separate patient portal, mobile app or PDF. A scanner may help identify issues at scale, but the organization still needs human review of important interactions and a team to make repairs.
Before adding software, define the job it will perform. Review the deployment boundary, the data it receives, account ownership and integration constraints. In a healthcare environment, involve privacy and security review where appropriate. Do not assume that a tool is suitable for a sensitive workflow because it is marketed as an accessibility solution.
Compare the product’s contribution with the underlying website changes available. Correct field labels, meaningful headings and sensible error handling can often be addressed in the source configuration. Those improvements should remain part of the plan even if the organization also uses monitoring or visitor adjustment tools.
The accessibility plug-in guide explains the distinction between widgets, scanning and manual evaluation. For a healthcare organization, that distinction also helps clarify which vendor or team is accountable for each part of the patient experience.
10
Set up a workstream with clinical and operational input.
I would assign an executive sponsor, a compliance lead, a technical lead and owners for the patient processes in scope. Include privacy, security, procurement and clinical reviewers when their responsibilities are affected.
The team needs a shared way to record findings and decisions. Each issue should identify the patient task, the observed barrier, the affected component, the repair owner and the evidence needed to close it. Where an interim assistance route is necessary, give that route an owner too.
The most useful progress discussion is specific. A form’s error handling is ready for retest. A portal vendor has acknowledged a defect but not provided a release date. A clinical team has approved an accessible source template. A scheduling change requires another security review.
Those details support decisions. A single percentage-complete number can hide the difference between many small content repairs and one unresolved barrier in the main appointment process.
11
An illustrative 90-day starting plan
This sequence is a way to organize the first stage of work. It is not a promise that every organization can finish remediation in ninety days or a substitute for its confirmed deadline.
Days 1–30: establish coverage, scope and immediate help.
Confirm the applicable rule, employee threshold and deadline. Inventory major patient journeys and vendors. Gather existing audits, complaints and accessibility reports. Agree on safe testing access and data handling. Identify barriers that need immediate assistance or escalation.
At the end of this period, leadership should understand the principal systems, the owners and the most important unknowns. It should have enough information to commission the right assessment rather than buying a generic homepage scan.
Days 31–60: evaluate, repair and change the source templates.
Review essential journeys and shared components. Begin direct repairs where the team has control, and send reproducible findings to vendors. Establish accessible document templates with the appropriate clinical approval. Improve the publishing process while the existing backlog is being addressed.
Use the findings to refine the implementation budget and schedule. A vendor dependency or substantial document collection may need its own workstream. Make that visible early enough for leadership to act.
Days 61–90: verify and establish the continuing routine.
Retest repaired tasks, review assistance requests and inspect the next group of content. Record open issues and decisions. Train the staff who publish or manage affected systems. Define review triggers for new forms, portal changes, document templates and software releases.
The result should be a functioning program with evidence and ownership. The organization will still need to maintain it as services and systems change.
12
Keep the evidence useful and proportionate.
A good record explains the scope, methods, environments, findings, repairs and verification results. It also records unresolved dependencies. It should support the people doing the work and the leaders making decisions.
Use synthetic examples in routine reporting where possible. Keep sensitive test material in the appropriate controlled system. Screenshots and recordings can be useful evidence, but they should not become a new store of unnecessary patient information.
Distinguish an observed failure from a recommendation to improve the experience. Both can matter, but they have different meanings. Tie a conformance finding to the relevant requirement and explain the context so the developer, vendor and compliance reviewer can understand it.
For prioritization, start with barriers that prevent patients from obtaining information or completing important tasks, then consider reach and dependencies. My accessibility repair planning guide explains that approach. Retest the original failure after the change and check adjacent behavior before closing it.
Questions & answers
Questions healthcare organizations ask
Is the HHS deadline still May 2026?
The 2026 extension changed the technical web and mobile compliance dates to May 11, 2027 for covered recipients with at least 15 employees and May 10, 2028 for those below 15. Use the current extension and regulation rather than an older summary.
Does this apply to every healthcare website?
This particular rule concerns recipients of HHS financial assistance. Applicability should be confirmed for the organization and its programs or activities. Other accessibility obligations can apply even when this specific rule does not. A consultant should not infer coverage solely from the site’s specialty or size.
Does a patient portal count if another company runs it?
Vendor arrangements need to be included in the applicability and inventory review. The rule addresses content made available through contractual, licensing or other arrangements. Identify the deployed service, request relevant vendor evidence and assign responsibility for addressing barriers.
Can we rely on a phone number while we repair the site?
An appropriate assistance route can help a patient with an immediate problem, but should not be assumed to replace the applicable technical requirements. The method needs to meet the person’s communication needs and the organization’s obligations. Involve the compliance lead in that decision.
Should we target WCAG 2.1 or 2.2?
The HHS rule specifies 2.1 AA. A 2.2 AA target for new work can address additional barriers while the organization documents how it meets the actual requirement. Keep the technical target, legal requirement and evaluation scope clear.
Are older PDFs automatically exempt?
No. The exception has conditions, and active use matters. Inventory the documents, identify their role in current services and review any exception with the appropriate lead. Source templates and new publication practices should be improved at the same time.
Does an accessibility review include HIPAA compliance?
Not automatically. Accessibility and privacy/security are distinct responsibilities that may intersect during implementation and testing. Define each scope and involve the qualified people responsible for it. Do not treat an accessibility tool or audit as a privacy certification.
Sources & scope
Sources and further reading
Reviewed October 20, 2026. This is operational guidance, not legal or clinical advice. Confirm coverage, employee count, exceptions and current requirements with the appropriate professionals.
Work with Rob
Make the next step toward care easier to complete.
If your organization needs to connect its accessibility requirements with the website, forms, documents and vendors patients actually use, I can help organize the assessment and implementation work around those journeys.
Explore website accessibility consulting or contact Rob Urban at 407-227-0741. Bring any existing audit, confirmed deadline and list of systems, and we can start with the work that needs a clear owner.
