As of May 7, 2026, the U.S. Department of Health and Human Services (HHS) has extended the Section 504 digital accessibility compliance deadline. This is critical information for any organization that receives HHS funding, as well as any third-party vendors selling software into this market.
However, while the news may seem straightforward, the implications are anything but. In this post, I’ll clarify what did and didn’t change, and what your organization needs to do. The most important thing to know is this: you can still be held accountable for inaccessible digital experiences today.
What changed
The compliance timeline for meeting the Web Content Accessibility Guidelines (WCAG) 2.1 A/AA has been moved out by one year.
Originally, organizations with 15 or more employees were required to comply by May 11, 2026, with smaller organizations following on May 10, 2027.
- Recipients with 15 or more employees will now have until May 11, 2027, to comply.
- Recipients with fewer than 15 employees will now have until May 10, 2028, to comply.
That’s the full extent of the change.
What didn’t change
There is no rollback in requirements, no narrowing of scope, no modification to what must be made accessible.
Digital accessibility is still required today. Section 504 has always prohibited discrimination based on disability for organizations receiving federal funding. That obligation did not start with the 2024 rule, and it does not pause because of this deadline extension.
In short, while you now have more time to achieve compliance with the new HHS 504 rule, you still need to make sure all of your (public, patient, and/or student) digital information and communication technology (ITC) is accessible today.
The legal reality (right now)
Your organization can still face complaints, investigations, and lawsuits today if your digital experiences are not accessible. And while the deadline may have shifted, you still need to be able to demonstrate forward motion, with a clear, documented path to WCAG 2.1 A/AA by the newly extended deadline.
In practice, enforcement has already moved beyond WCAG 2.0 A/AA. The U.S. Department of Justice has consistently pointed to WCAG 2.1 A/AA in consent decrees and settlements. This is the critical distinction. The updated rule does not create new liability. Organizations are already accountable for inaccessible experiences today. What it does is remove ambiguity by defining how that accountability is measured.
How to make the most of this extension
A deadline extension creates a real opportunity. By moving now, your organization can reduce risk, control costs, and build capability in a steady, sustainable way. You can focus on the digital experiences that matter most, fix real barriers your users are facing today, and put the right systems in place to prevent issues from recurring.
The alternative—deferring work, letting issues pile up, and underestimating the time you’ll need—will result in higher costs, greater complexity, and more risk. Now is the ideal time to ensure your organization is making the right decisions for the long term.
Where to focus first
Don’t try to fix everything at once. Start where access matters most. User portals. Scheduling. Billing. Enrollments. Forms and documents.
If someone needs it to receive support, care, or services, it needs to work.
Use this extension to build capability, not delay action. Define ownership. Build accessibility into procurement, design, and development. Monitor continuously. Hold vendors accountable. And measure progress over time.
Section 504 protects more than digital access
It’s important to remember that, in addition to its other applications, HHS Section 504 specifically ensures equal access to healthcare, including medical equipment and treatment decisions. For people with disabilities, this can be life-altering. In some cases, individuals have been denied appropriate care based on assumptions about quality of life. That is the kind of discrimination these protections are meant to address. A deadline extension does not change the urgency of that responsibility.
The bottom line
This is a shift in the timeline for explicit expectations for meeting WCAG 2.1 A/AA. But it’s also an opportunity. Organizations that act now can replace uncertainty with a clear, defensible plan.
This process starts with a gap analysis—a clear view of what’s working and where your digital experiences fall short. What you’re doing is developing a prioritized roadmap for remediation and a practical path to align with WCAG 2.1 AA over time.
If you’re ready to move forward, Deque can help you establish that baseline. With the right visibility and a focused plan, progress becomes manageable and measurable. And the progress you make can literally change lives for the better.
