Section 504's digital accessibility clock got reset by a year — the standard, the scope, and the pressure did not.
The call came in two flavors. Some of our health system clients breathed out — “we got another year.” Others shrugged it off entirely — “see, they keep pushing it back.” Both reactions miss the point, and both are going to cost someone.
On May 7, 2026, HHS published an Interim Final Rule extending its Section 504 digital accessibility deadlines by twelve months. Organizations with 15 or more employees now have until May 11, 2027 to bring their web and mobile properties into compliance. Smaller recipients have until May 10, 2028. The rule took effect immediately — four days before the first wave of organizations would have hit the original deadline. The required standard is still WCAG 2.1 AA. The scope of what must be accessible is unchanged. Only the enforcement calendar moved.
That distinction matters more than it sounds. An organization that was behind on May 6 is still behind on May 8. The extension reset the clock on enforcement, not on the obligation. Federally Qualified Health Centers, Medicaid-participating providers, hospitals receiving HHS funding — they were covered before, they are covered now, and the year they just received is not a signal that the rule is softening. It is, at most, a second chance to do the remediation correctly instead of in a sprint.
The extension reset the clock on enforcement, not on the obligation.
For clients already mid-remediation, the extra runway is genuinely useful. Accessibility work done under deadline pressure tends to be shallow — a pass at color contrast and alt text that satisfies an audit checklist but leaves the underlying structure brittle. Twelve more months means there is time to audit what you actually have, fix it at the component level, and build the internal process that keeps it compliant as the site evolves. That is the work worth doing.
For organizations that have not started, the calculus is different. This is the second time regulators have extended rather than enforced. A third extension would be a policy reversal, not a pattern — and auditors have been watching the field long enough to know which organizations treated the first extension as preparation time and which ones treated it as permission to wait. The ones who waited the first time are the ones whose files are already open.
We work with health systems and nonprofits on exactly this kind of remediation — a structured audit against WCAG 2.1 AA, prioritized by user impact, with a sprint that leaves clients with something durable rather than a one-time fix. If you have the year, that is the right use of it. We are ready when you are.