Healthcare Websites Have a New Accessibility Deadline. Here's What It Actually Requires
ClearPath Team · 2026-07-29 · 7 min read

If you run a website for a medical practice, hospital, clinic, or any organization that bills Medicare or Medicaid, you probably heard something about a May 2026 accessibility deadline. Then, just days before it hit, the deadline moved. That's led to a lot of confusion about what's actually required and when. Here's the short version: the rule didn't go away. The clock just got reset.
What the Section 504 rule actually says
In 2024, HHS finalized the first substantive update to its Section 504 regulations in nearly 50 years, overhauling the regulation implementing Section 504 of the Rehabilitation Act of 1973. For the first time, HHS made it explicit that web content and mobile apps used in health and human service programs must be accessible for people with disabilities. That's a big deal because Section 504 applies to any organization that receives federal financial assistance, which in practice means almost any provider that accepts Medicare or Medicaid.
WCAG 2.1 Level AA is the mandatory technical standard, covering 50 testable success criteria organized under four principles: content must be perceivable, operable, understandable, and robust. And the scope isn't limited to your marketing site. Your website, patient portal, mobile apps, and digital documents must meet WCAG 2.1 Level AA standards, which means your site needs to work for people using screen readers, keyboard-only navigation, and other assistive technologies, including things like color contrast, form labels, image alt text, video captions, and predictable navigation. A tool like ClearPath can give visitors on-page controls for some of these, like contrast and text sizing, but it won't add missing form labels or alt text to your underlying markup.
The deadline got pushed, but the obligation didn't
The original web content and mobile app compliance deadlines were set for May 11, 2026, and May 10, 2027, but on May 7, 2026, HHS published an Interim Final Rule extending those compliance dates by one year. Recipients with 15 or more employees now have until May 11, 2027, and recipients with fewer than 15 employees now have until May 10, 2028. HHS made the change just four days before the original deadline was set to arrive.
It's worth being clear about what this extension does and doesn't mean. The extension changes the compliance dates, not the legal obligation. Section 504's prohibition on disability-based discrimination in federally funded programs remains in full effect. Disability advocacy groups pushed back hard on the delay, arguing the regulation did not create a new obligation but clarified how covered entities should already be acting to comply with an existing one. In other words, the extension buys you time on the specific enforcement date, but it doesn't buy you an exemption from the underlying requirement, and it doesn't touch the ADA or Section 1557 claims that are already being filed against healthcare sites today.
Where healthcare sites actually fail
Patient-facing healthcare sites tend to fail in a handful of predictable places, and they're usually the highest-traffic pages on the whole site.
- Patient portal login and navigation. A disabled patient who cannot access a portal or complete intake forms faces a direct barrier to healthcare, and both courts and HHS OCR take this seriously.
- Intake and appointment forms. Appointment booking systems and patient intake forms are consistently the highest-risk areas for both ADA complaints and HHS investigations.
- Scanned health documents. Scanned PDFs cannot be read by screen readers, meaning visually impaired patients receive no information at all from after-visit summaries or care instructions posted as images of text.
- Kiosks and check-in devices. The rule extends beyond the website itself. The final rule adopts the U.S. Access Board's standards for accessible kiosks and medical diagnostic equipment, including exam tables, weight scales, and mammography machines.
And here's the detail that trips up a lot of well-meaning teams: the standard applies behind the login wall just as much as it does to the public-facing website. A beautiful, compliant marketing homepage doesn't help a patient who gets stuck trying to log in and read their lab results. A widget like ClearPath can be applied behind the login wall too, so patients get the same adjustment tools inside the portal, though it still can't fix a login flow that isn't keyboard operable in the first place.
Why overlays alone won't get you there, and why that matters for enforcement
If you're shopping for a fast fix, you'll run into accessibility overlay widgets everywhere. It's worth understanding their limits before you rely on one as your whole strategy. Overlays add a JavaScript layer on top of your site but don't fix the underlying code issues, and automated tools can only detect about 30% of WCAG problems, which means overlays miss the majority of violations. Worse, plaintiff attorneys specifically target sites with overlay widgets, because the presence of an overlay signals you knew about accessibility requirements, and about 25% of 2024 accessibility lawsuits cited overlays as part of the problem. That doesn't mean assistive tools are worthless. It means they need to sit on top of a site that's actually been fixed at the code level, not instead of that work.
What to prioritize before either deadline
- Run an audit that covers your website, patient portal, and any digital intake or scheduling tools, not just the homepage.
- Test your portal login, appointment booking, and document access using only a keyboard, no mouse.
- Re-export scanned health guides and after-care instructions as tagged, readable PDFs instead of image scans.
- Check that every form field on your intake forms has a real, programmatically associated label.
- Add captions to any patient education videos and verify color contrast on anything with a clinical status indicator (results ready, appointment confirmed, balance due).
Where ClearPath fits
ClearPath installs with one line of code and gives visitors 25 accessibility tools across 8 preset profiles (things like screen reader optimization, keyboard navigation support, cognitive-friendly reading modes, and content in 14 languages), plus an auto-generated accessibility statement you can point to when patients or auditors ask what you've done. For a healthcare site, that means ClearPath can help patients adjust contrast, font size, spacing, and language on the fly, and it strengthens keyboard and screen reader navigation for visitors who need it right now. What it can't do is rewrite your patient portal's underlying code, fix an intake form that's missing real HTML labels, tag a scanned PDF that has no text layer, or restructure a booking widget's markup so it's operable by keyboard by default. Those are code and content fixes your developers or a remediation partner need to make. Think of ClearPath as the layer that helps real visitors right now while your team works through the deeper fixes the Section 504 and WCAG 2.1 AA standards actually require.
Not sure how many of these issues are on your own site? Run a free scan, see what comes up, then switch on the tools that help your visitors today.
The May 2026 deadline moving to 2027 and 2028 gives healthcare organizations breathing room, not a pass. If your patient portal, intake forms, or appointment tools have accessibility gaps today, patients are running into them today, regardless of which year the enforcement date lands on.