Quick answer
Inventory the resident-facing web and mobile services the organization provides, including contracted services. Determine applicable coverage and deadlines, then test complete tasks with assistive technology and manual review. As of November 10, 2026, the HHS Section 504 WCAG 2.1 A/AA dates are May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller recipients; existing accessibility duties continue.
Use the current dates and the correct organizational scope
A SNF group replacing its resident portal needs an accessibility plan tied to the services it provides, not an outdated deadline copied from a 2024 article. HHS announced a one-year extension in May 2026. Current 45 CFR 84.84 sets the WCAG 2.1 Level A and AA dates at May 11, 2027 for recipients with at least 15 employees and May 10, 2028 for recipients with fewer than 15.
The rule addresses recipients of HHS financial assistance and includes web content and apps supplied through contractual, licensing or other arrangements. Have qualified reviewers establish entity coverage, employee category, applicable exceptions and other laws. Do not use a single facility's staffing count to determine an enterprise recipient's deadline without that analysis. The extension does not remove existing accessibility obligations.
Inventory services from the resident's perspective
List admission inquiries, portal registration, proxy access, messages, bills, electronic signatures, notices, downloadable documents and telehealth entry. Include third-party pages reached from the main site. A compliant-looking landing page does little for a resident who cannot complete the external payment or signature step.
This original inventory prioritizes complete tasks:
| Resident task | Surfaces to inspect | Material barrier example |
|---|---|---|
| Create an account | Form, verification, error and recovery screens | Unlabeled field or inaccessible verification step |
| Read a notice | Portal viewer and downloaded document | Reading order or text unavailable to assistive technology |
| Pay a bill | Balance, payment service and receipt | Keyboard trap or error not announced |
| Sign an approved document | Document review, consent and signature controls | Required action cannot be completed without a pointer |
| Join a visit | Invitation, device check and video interface | Needed accommodation unavailable at the final step |
The examples are test targets, not an exhaustive WCAG checklist. Use qualified accessibility assessment against the applicable criteria.
Test tasks with more than one method
Combine automated checks with manual keyboard, zoom/reflow, focus, screen-reader and other relevant assessments. Include people with disabilities in appropriately supported usability evaluation. Usability feedback and formal conformance testing answer related but different questions; retain both rather than treating one as a substitute for the other.
In a fictional test, a resident can read a bill with a screen reader but cannot identify the payment error or return focus to the corrected field. The task has failed even if most pages pass a scanner. Record the exact step, environment, expected behavior, observed barrier and reproduction details without exposing resident information.
Turn findings into a funded remediation plan
Classify barriers by affected tasks and consequences, not only by the number of technical findings. Assign the responsible supplier or internal team, target release, interim assistance and retest evidence. A supplier accessibility conformance report can inform the review, but confirm its product version, scope and known exceptions against the proposed deployment.
Contract for correction and regression handling where needed. Ask what happens when a supplier updates a component or changes an external service. Acceptance should require that important journeys work in the configured product, with remaining issues and their approved handling visible. Do not claim that an overlay or accessibility badge proves conformance.
Keep an accessible service available while work continues
Residents need a practical way to report barriers and obtain effective assistance. Define the route, staff responsibilities and how requests reach the team fixing the underlying problem. An alternative channel should not be assumed to excuse every digital barrier or satisfy all legal conditions; review the specific circumstances.
The purchasing decision should connect coverage, actual user tasks, observed barriers, remediation commitments and ongoing testing. That gives the organization a realistic path to accessible resident services instead of a deadline-only compliance project.
Questions & answers
Did the 2026 extension suspend all accessibility duties?
No. HHS expressly retained existing duties to make programs and activities accessible. The extension concerns specified web and mobile conformance dates.
Is an automated scan enough to accept a resident portal?
No. Automated tools find some issues, but complete task testing, manual assessment and relevant assistive-technology use are needed to understand important barriers.
Primary sources
Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.