The WCAG compliance date and your broader accessibility obligations are not the same thing. HHS just moved the first one. The second one hasn’t moved since 1973.

On May 11, 2026, the Department of Health and Human Services quietly dropped an Interim Final Rule (IFR) extending the web accessibility compliance dates under Section 504 of the Rehabilitation Act.

If you receive federal financial assistance – and if you’re in healthcare, higher education, social services, or local government, you almost certainly do – here’s what changed, what didn’t, and what you should actually be doing right now.

What changed

The compliance dates for WCAG 2.1 AA conformance under the HHS Section 504 final rule moved by one year:

  • Organizations with 15 or more employees: May 11, 2026 → May 11, 2027
  • Organizations with fewer than 15 employees: May 10, 2027 → May 10, 2028

That’s it. One year. One very specific thing.

What didn’t change

Everything else.

Section 504 has required nondiscriminatory access to federally funded programs since 1973. The IFR’s own language is worth reading carefully here: the delay “does not relieve recipients of their other obligations under Section 504,” including the requirement to make reasonable modifications to ensure accessibility and avoid discrimination on the basis of disability.

HHS gives examples directly in the document. A college or university is still expected to make course materials accessible for an enrolled student with a disability. A state agency running Medicaid enrollment is still expected to ensure residents with disabilities can access and apply for benefits.

The deadline moved. The obligation didn’t.

If this framing sounds familiar, it should – it’s the same argument I made in The ADA Deadline Doesn’t Matter. Here’s What Does. Accessibility obligations don’t suddenly appear when a compliance date arrives.

The delay itself is revealing. HHS cited widespread implementation challenges among recipients, including PDF remediation backlogs, staffing limitations, third-party vendor dependencies, and uncertainty around large-scale WCAG 2.1 conformance efforts. In other words: many organizations underestimated how much accessibility work had accumulated over time.

The extension gives recipients more time to address those problems. It does not remove the expectation that they address them.

The enforcement reality

Section 504 has two main enforcement mechanisms, and only one of them cares about your WCAG deadline.

OCR complaints – filed with HHS’s Office for Civil Rights – can result from inaccessible web content right now, today, under 504’s general nondiscrimination and effective communication provisions. They don’t require a named technical standard to proceed.

The private right of action is the one with sharper teeth. Barnes v. Gorman (2002) confirmed that Section 504 is privately enforceable in federal court. Private plaintiffs can seek injunctive relief and attorneys’ fees. The IFR itself explicitly cited the risk of private litigation as one of its primary reasons for extending the deadline – HHS is worried about what happens when a significant number of recipients miss the date. That concern doesn’t disappear because the date moved. It moves with it.

A year from now, you’ll be in the same position you’d have been in this week – except with less goodwill if you spent the extension doing nothing.

What you should be doing

The IFR is not a pause button. It’s an argument for using the time you now have more deliberately.

Start with your key user journeys. What does someone need to do on your website to access your programs or services? Schedule an appointment. Apply for assistance. Find information about their benefits. Enroll in a course. Those flows are where the legal and ethical risk lives, and they’re where your remediation effort will have the most impact.

Audit your PDFs. This comes up in the IFR’s own justification – counties cited PDF remediation specifically as the area creating the most compliance difficulty. If your organization is document-heavy, that backlog doesn’t get easier with time.

Check your third-party content. The IFR notes that recipients are struggling to ensure contractors and vendors meet WCAG 2.1 requirements. If your web content is partially or fully managed by outside parties, that’s a contract conversation you need to have now, not in May 2027.

Document your progress. If a complaint is filed against you – through OCR or in court – demonstrated good-faith effort matters. An organization that can show ongoing remediation work is in a fundamentally different position than one that treated the extension as permission to wait.

The bigger picture

Section 504 is the oldest legal framework for disability rights in the United States. It predates the ADA by 17 years. It has required accessible programs and services since before the web existed. The 2024 final rule didn’t create a new obligation – it named a technical standard for one that was already there.

The deadline that just moved was never the reason to do this work. The reason is that people with disabilities need to access your services, have needed to for decades, and have a legally protected right to do so.

That part was always true. It still is.

This article does not constitute legal advice.