HHS Just Extended Its Section 504 Web Accessibility Deadline — What Healthcare WordPress Sites Need to Know

Today — May 11, 2026 — was supposed to be the hard deadline for healthcare organizations and other recipients of HHS funding to bring their websites into full WCAG 2.1 Level AA compliance under Section 504 of the Rehabilitation Act. Then, four days ago, HHS blinked. An Interim Final Rule published on May 7 pushed the deadline back by one year. If you run a healthcare-related WordPress site and breathed a sigh of relief, read this before you close the tab.

What Just Happened with the HHS Section 504 Deadline

In May 2024, HHS finalized a rule updating Section 504 of the Rehabilitation Act to include explicit WCAG 2.1 Level AA requirements for websites, mobile apps, and kiosks used by organizations that receive federal financial assistance. That covers a wide range of entities: hospitals, clinics, dental practices, community health centers, universities receiving HHS grants, social service agencies, and more.

The original compliance dates were May 11, 2026 for organizations with 15 or more employees, and May 10, 2027 for smaller organizations. On May 7, 2026, HHS issued an Interim Final Rule extending those dates by exactly one year:

• Organizations with 15 or more employees: Now must comply by May 11, 2027
• Organizations with fewer than 15 employees: Now must comply by May 10, 2028

HHS cited the need to “reduce regulatory burden” and allow organizations more time to assess and implement changes. Sound familiar? It should — DOJ did the same thing with its ADA Title II deadline for state and local governments just weeks ago. Deadline extensions are becoming a pattern.

Why an Extension Is Not a Free Pass

Here is the thing about regulatory deadline extensions: they move the compliance date, not the legal risk. Section 504 itself has been enforceable for decades. Organizations that receive HHS funding have always been prohibited from discriminating against people with disabilities — the new rule simply made the WCAG 2.1 AA standard explicit. That means complaints and investigations were possible before May 11, and they remain possible after it.

There is also a broader litigation environment to consider. Federal court filings for ADA website accessibility lawsuits jumped 27% in 2025, reaching over 3,100 cases. AI tools are making it easier for individuals to file pro se complaints without a lawyer. An extension from HHS does not insulate a healthcare organization from an ADA Title III lawsuit filed by a patient who could not use the online appointment booking system or read a PDF treatment summary.

The year you just gained is best spent actually fixing things — not waiting for the next extension.

What WCAG 2.1 Level AA Actually Requires

If you are new to WCAG, here is a plain-language summary of what the standard covers and what it means for a typical healthcare WordPress site:

Perceivable

All content must be perceivable by users regardless of disability. In practice: images need descriptive alt text, videos need captions, audio needs transcripts, and your color contrast ratios must meet minimum thresholds (4.5:1 for normal text, 3:1 for large text). A lot of healthcare sites fail on color contrast alone — pale gray text on white backgrounds is a common culprit.

Operable

Every function on your site must be reachable using a keyboard alone, with no mouse required. This includes appointment booking forms, patient portal logins, medication refill requests, and contact pages. If a user cannot tab through your form fields in a logical order and submit the form without a mouse, you have an operability failure.

Understandable

Pages must declare their language in code, form fields must have clear labels, error messages must explain what went wrong and how to fix it, and navigation must be consistent across pages. Healthcare sites often fail here with generic “invalid input” error messages on patient intake forms.

Robust

Your HTML must be clean enough that assistive technologies — screen readers, switch controls, voice navigation software — can reliably parse it. Duplicate IDs, missing ARIA roles, and poorly structured heading hierarchies are the most common failure points.

What to Do With Your Extra Year

One year sounds like plenty of time. It goes faster than you think, especially if accessibility work has to compete with patient portal upgrades, EHR integrations, and whatever else is on your organization’s roadmap. Here is a practical approach to using the extension productively:

1. Audit first. You cannot fix what you have not measured. Run a scan of your site to identify actual WCAG failures at the code level — not just a surface-level check, but something that looks at markup, contrast, form structure, and interactive components.
2. Prioritize high-traffic pages. Your appointment booking page, patient portal login, and homepage matter more than your 2019 blog post about flu shots. Fix those first.
3. Fix the code, don’t mask it. Accessibility overlays — widgets that bolt onto your site and claim to make it compliant — do not fix underlying code failures. Courts and regulators are increasingly skeptical of them. Fix the actual HTML.
4. Test with real users. Automated scanners catch roughly 30-40% of WCAG issues. Manual testing with a keyboard and screen reader catches more. Testing with actual users who have disabilities catches the rest.
5. Document your progress. If a complaint is filed against you, demonstrating that you had an active accessibility program — audits, remediation plans, staff training — matters. Keep records.

How This Differs from the DOJ Title II Extension

It is worth being clear about which rule applies to your organization, because they are different:

• DOJ ADA Title II applies to state and local governments — public schools, city websites, county agencies, public libraries, government health departments. The DOJ extended its deadline in April 2026.
• HHS Section 504 applies to private and nonprofit organizations that receive HHS funding — hospitals, clinics, dental practices, universities with NIH grants, social service nonprofits, and similar entities. This is the deadline that just moved.
• ADA Title III applies to places of public accommodation, including private businesses. There is no specific WCAG rule here — just the general prohibition on discrimination — but courts have consistently ruled that inaccessible websites violate Title III.

Many healthcare organizations are subject to more than one of these. A nonprofit hospital might face both Section 504 and Title III obligations simultaneously.

Take Action

Whether your deadline is now May 2027 or you are simply trying to reduce legal risk before then, the first step is knowing what is actually broken on your site. LEWCA is a WordPress accessibility plugin that scans your site for real WCAG code-level issues — not just surface-level checks — and flags what needs to be fixed. LEWCA Pro adds AI-powered code fix suggestions, scheduled scans, and compliance reports you can share with administrators or legal counsel. Unlike overlay tools that claim to make sites compliant without changing the underlying code, LEWCA surfaces the actual problems so you can fix them for real. See LEWCA plans and pricing or download the free version to start your audit today.