HHS Extends Web Accessibility Deadlines for Providers

The Health and Human Services Department has issued an interim final rule that extends the compliance dates for the web content and mobile application accessibility requirements adopted under section 504 of the Rehabilitation Act. Published as 91 FR 25496 on May 11, 2026, the rule is effective May 7, 2026. For healthcare providers that receive federal financial assistance from the Department, this is a change to the calendar — not to the underlying accessibility obligation — and understanding the new schedule now is what keeps a practice from planning around a date that has moved.

This guide explains, in plain English, what the rule does, who it touches, how the deadlines shift, and how a busy provider can keep up with the operational follow-through over a multi-year runway. It leads with the obligation and the dates, not with any product. The aim is to give compliance and operations teams a clear, sourced picture they can act on without re-reading the full Federal Register entry themselves.

Key Takeaways

• An HHS interim final rule, cited as 91 FR 25496, extends the section 504 web and mobile application accessibility compliance dates and is effective May 7, 2026.

• For recipients with 15 or more employees, the compliance date moves from May 11, 2026, to May 11, 2027.

• For recipients with fewer than 15 employees, the compliance date moves from May 10, 2027, to May 10, 2028.

• The rule revises the regulations at 45 CFR Part 84 and carries the RIN 0945-AA30; the underlying accessibility requirements were adopted on May 9, 2024.

• This post is informational only and is not legal or tax advice; consult a qualified attorney or tax advisor before acting on any specific situation.

What this rule actually does

The interim final rule revises the Department's regulations implementing section 504 of the Rehabilitation Act to extend the compliance dates for web content and mobile application accessibility requirements that were adopted on May 9, 2024. It is important to read that carefully: the rule does not repeal the accessibility requirements, and it does not change what "accessible" means under the regulation. It moves the dates by which recipients of departmental financial assistance must meet those requirements. In other words, the substantive obligation stays; the runway gets longer.

Because this is an interim final rule, the change carries the force of a final regulation. The agency adopted the extension to take effect on the published effective date of May 7, 2026, as stated in 91 FR 25496. For a healthcare provider, the practical reading is that any internal project plan, vendor contract milestone, or remediation budget that was keyed to the original section 504 web accessibility dates should be re-checked against the new schedule. A plan built around the old dates is now a plan built around a deadline that has been superseded.

The extension is tiered by employer size, which matters because many small and mid-sized practices sit on the line between the two tiers. The rule sets one new compliance date for recipients with a larger headcount and a separate, later date for the smallest recipients. The next section lays out exactly how the dates move.

How the compliance dates change

The table below paraphrases the rule's own statement of the extension. It does not add any date, figure, or requirement beyond what the regulation states, and every value traces to the rule abstract published in the Federal Register.

The authoritative source for both rows above is the rule itself, available at 91 FR 25496. The effective date of the extension — May 7, 2026 — is separate from the compliance dates above; the effective date is when the extension itself takes legal force, while the compliance dates are when covered recipients must have met the underlying accessibility requirements. Keeping those two ideas distinct is the single most common point of confusion with a rule of this kind.

Who is affected

The reach of this rule follows the reach of section 504 itself: it applies to recipients of financial assistance from the Department. In a healthcare context, that pulls in a wide range of providers and organizations whose web content and mobile applications fall within the scope of the section 504 regulation. The size tiers then determine which compliance date applies to a given recipient. A provider's first task is to confirm whether it is a covered recipient at all, and if so, which employee-count tier it falls into.

Covered recipients should note that the rule revises the regulations at 45 CFR Part 84, and the rulemaking carries the RIN 0945-AA30. A provider's compliance counsel will want to read the extension together with the underlying section 504 accessibility provisions adopted on May 9, 2024, because the extension only makes sense in light of the requirements whose deadlines it is moving. Reading the extension in isolation tells you when, but not what.

What providers should do before the date

The most important thing a healthcare provider can take from this rule is that the obligation did not disappear — it was rescheduled. That distinction shapes the right response. A provider that reads "extension" as "cancellation" and stops its accessibility work will simply arrive at the new date unprepared. A provider that uses the additional time to do the remediation properly is the one the extension is meant to help. The rule requires recipients to meet the underlying accessibility requirements by the applicable new date; it does not relieve them of those requirements.

A sensible, sourced preparation path looks like this. First, confirm whether the organization is a recipient of departmental financial assistance subject to the section 504 web and mobile accessibility requirements, and if so, determine the employee-count tier, because that decides whether the operative date is May 11, 2027, or May 10, 2028. Second, pull every internal plan, statement of work, or budget line that referenced the prior section 504 accessibility dates and re-baseline it against the new schedule, so no team is racing toward a date that has moved. Third, keep the remediation work itself on a steady cadence rather than deferring it to the edge of the new deadline, since accessibility work on a large web and mobile footprint takes time. Fourth, keep a current copy of the rule's text on hand, because the agency may issue corrections or related guidance, and the primary source remains the controlling document.

Throughout, the operative framing is that the rule requires covered recipients to meet the accessibility requirements by the extended date, and covered providers must understand which date applies to them. This is a description of the law as published in the Federal Register, not a personalized legal command to any reader, and it is not a substitute for advice from your own counsel.

Operationalizing the monitoring at volume

The hard part for most providers is not the first read of this extension — it is staying current across a multi-year runway, during which the agency may issue corrections or related guidance and adjacent rulemakings may land on top of this one. That is a monitoring problem, and monitoring at volume is where US Tech Automations fits. Configured against the Federal Register feed, the platform can monitor new documents tied to this rulemaking, the assigned RIN 0945-AA30, and the affected part of the regulations, then flag a matching change and route it to a named compliance reviewer instead of letting it sit unread in a shared inbox. The goal is a workflow that surfaces the right document to the right person on time, without anyone re-reading the entire daily Federal Register by hand. You can see how that monitoring workflow is structured on the US Tech Automations AI agents page.

The second half of the work is the follow-through after a change is caught. Here a configured pipeline can extract the relevant fields from a flagged document, draft a short internal summary for the reviewer, and escalate items that look material — such as a correction to a compliance date or new guidance under 91 FR 25496 — into your existing ticketing or task system so the flag, the draft, and the human sign-off all live in one place. The point is not to replace your counsel's judgment; it is to make sure nothing relevant reaches either new date unseen. For a provider tracking a deadline more than a year out, that kind of automated follow-up is what keeps a long runway from becoming a forgotten one.

How this fits the broader regulatory window

This rule does not exist in a vacuum. It is one of 128 federal rules sealed in our point-in-time index of rules published January 1, 2026 – June 20, 2026 by 9 agencies governing our covered industries. A single extension like this one is easy to read once; the challenge is that healthcare providers are subject to many rules at once, each with its own effective date, its own affected CFR part, and — as this rule shows — its own moving compliance schedule. A provider that tracks only the rules it already knows about, on the dates it first wrote down, will eventually plan around a deadline that has shifted underneath it. That is the structural case for treating Federal Register monitoring as an ongoing operational function rather than a one-time project.

The takeaway for leadership is straightforward: the section 504 web and mobile accessibility requirements are still coming, the dates have simply moved later, and that movement is itself a reminder that compliance calendars are not static. Building a durable way to watch the regulatory stream — and to route what matters to the people who can act — pays off well beyond this single extension.

Frequently asked questions

What is the effective date of this HHS extension rule?

The interim final rule is effective May 7, 2026, as stated in the rule published at 91 FR 25496. The rule was published on May 11, 2026. Note that the effective date of the extension is distinct from the compliance dates it moves.

How exactly do the compliance dates change?

For recipients with 15 or more employees, the compliance date moves from May 11, 2026, to May 11, 2027. For recipients with fewer than 15 employees, the compliance date moves from May 10, 2027, to May 10, 2028. Both changes are stated in 91 FR 25496.

Does this extension cancel the web accessibility requirements?

No. The rule extends the compliance dates for the web content and mobile application accessibility requirements that were adopted on May 9, 2024; it does not eliminate them. Covered recipients must still meet the underlying section 504 requirements, just by the later dates set out in 91 FR 25496.

Which part of the Code of Federal Regulations does this rule affect?

The rule revises the regulations at 45 CFR Part 84, which implement section 504 of the Rehabilitation Act for recipients of the Department's financial assistance. The RIN for the rulemaking is 0945-AA30.

How do I know whether my practice is in the 15-or-more or the under-15 tier?

The applicable compliance date depends on the recipient's employee count, with a separate date for recipients with 15 or more employees and recipients with fewer than 15 employees. The thresholds and definitions are set out in the rule at 91 FR 25496, and a qualified attorney can help confirm how they apply to a specific organization.

How can a provider keep up with corrections and related guidance over a multi-year deadline?

Treat Federal Register monitoring as an ongoing function. Many providers configure an automated workflow to monitor for new documents tied to the rulemaking and route material changes to a compliance reviewer, so a correction or new guidance does not slip past during the long runway to the new dates. The primary text remains the rule itself at 91 FR 25496.

Related guidance

For related healthcare and regulatory deadline coverage, see our notes on the Medicaid program community engagement requirement, the federal independent dispute resolution operations and accounting requirements, and the broader small business lending under the Equal Credit Opportunity Act.

Disclaimer

This article is provided for informational purposes only and does not constitute legal or tax advice. Reading it does not create an attorney-client relationship. Regulatory requirements are fact-specific, and you should consult a qualified attorney or tax advisor before acting on any matter discussed here. Every date, citation, RIN, CFR reference, and figure in these posts is copied verbatim from the Federal Register and eCFR as of the snapshot date. Nothing is estimated, modeled, or extrapolated. This is not legal or tax advice.

Last reviewed: June 20, 2026.

Source: U.S. Federal Register (91 FR 25496); current text via eCFR, 45 CFR Part 84.