Health systems and FQHCs got a one-year extension on web accessibility compliance — now due May 11, 2027 — but the rule and its vendor scope are unchanged.
When the original Section 504 web accessibility deadline passed on May 11, 2026, two reactions landed in equal measure: relief from organizations that weren’t ready, and dismissal from organizations that figured the rule would never bite. Both reactions were premature. On May 7, 2026, HHS issued an Interim Final Rule moving the compliance deadline forward by a year — not waiving the obligation, not narrowing the scope, just buying time. The rule is real. The clock is running.
The Interim Final Rule sets May 11, 2027 as the new compliance deadline for covered entities with 15 or more employees. Organizations with fewer than 15 employees have until May 10, 2028. Covered entities include hospitals, health systems, Federally Qualified Health Centers, and any organization receiving HHS funding. The standard is WCAG 2.1 AA. The extension changes nothing about what is required — it changes only when the enforcement clock resets.
One detail in the rule that surprises clients: third-party vendor tools are in scope. If a scheduling widget, a payment portal, or a patient intake form is embedded in your site, it carries the same obligation as code you wrote yourself. On a WordPress site, that means every embedded plugin, every external form, every hosted scheduling iframe gets audited to the same standard. The extension gives organizations time to surface those dependencies — not to ignore them.
The extension gives organizations time to surface their vendor dependencies — not to ignore them.
Daylit works with health system clients on both sides of this: the public-facing WordPress presence and the third-party tools woven into it. We’ve seen organizations treat vendor tools as someone else’s problem. HHS’s rule treats them as yours. The remediation work typically touches scheduling widgets, donation forms, and patient-facing portals — exactly the pieces that tend to be handled by outside vendors operating on their own timelines.
We’re planning to the May 2027 date. For any client who hasn’t started a WCAG 2.1 AA audit, the runway exists now to do it without pressure — and to hand remediation work to vendors with enough lead time for them to deliver. That window narrows considerably after the new year. The work itself is not dramatic; a proper audit and a realistic remediation roadmap are a defined project. What makes it hard is starting late.
If you receive HHS funding and haven’t opened the accessibility conversation yet, this is the right moment. We’re ready to lead it.