ADA Title II Web Accessibility Requirements for Healthcare Organizations
Most healthcare compliance teams aren't sure whether ADA Title II's new web accessibility rule applies to them, which deadline they're facing, or what compliance actually requires. This guide walks through all three, plus the scope-map question most teams can't answer: which federal accessibility law applies to your organization in the first place.
Author: Missy Jensen, Senior SEO Copywriter
Published: 05/26/2026
)
Most healthcare compliance teams know that the Americans with Disabilities Act(opens in a new tab) (ADA) applies to their organization. Fewer know that the DOJ rewrote what that means for digital experiences in 2024, gave covered entities a fixed deadline for the first time, and extended the deadline by a year on April 20, 2026.
For public hospitals, county health systems, and state-operated clinics, the result is a regulatory clock that’s already running on websites, patient portals, and telehealth platforms most teams have never tested for accessibility.
If a state or local government operates your healthcare organization, the new web accessibility deadlines(opens in a new tab) under ADA Title II apply to you. The first deadline lands on April 26, 2027; the second on April 26, 2028. Both require your websites, patient portals, and mobile apps to meet the Web Content Accessibility Guidelines(opens in a new tab) (WCAG) 2.1 Level AA.
Below, we’ll explain who’s covered, when the deadlines hit, and what compliance actually requires. We’ll also address the question most healthcare buyers can’t answer on their own: which federal accessibility law applies to your organization if you’re not sure whether you count as “state or local government” in the first place.
Does ADA Title II Apply to Your Hospital?
ADA Title II applies to healthcare organizations operated by a state or local government. That includes:
Public hospitals owned and run by a state, county, or municipality
County and municipal health systems
State-operated clinics
Public health departments at every level of government
Academic medical centers operated by a public university (covered through the parent university’s Title II obligation)
If your organization falls into any of these categories, you must be ADA-compliant. The April 24, 2024 DOJ final rule and the April 20, 2026 Interim Final Rule set the timeline, and your deadline depends on the population you serve.
If your organization is a private hospital, a private practice, or a federally funded nonprofit health system, Title II does not apply. But a different law does; we’ll discuss that in more detail below.
When Does the Title II Web Accessibility Deadline Apply to Your Healthcare Organization?
The compliance deadline depends on the size of the population your covered entity serves.
These dates reflect the one-year extension granted by the DOJ in the April 20, 2026 Interim Final Rule.
Plan around these dates being firm. There is no indication that a second extension is coming, and recipients who build their compliance program around the original 2026 deadline are already ahead. If you’re just getting started with accessibility, you have less runway than the calendar suggests.
The DOJ has also signaled it plans further rulemaking on the substance of the 2024 rule during the extension window. The deadlines are firm, but the technical requirements could shift before they hit.
Which Law Applies to Your Hospital?
This is the question that most healthcare buyers can’t answer cleanly, and it’s the one that determines everything else. Three federal laws govern web accessibility for healthcare organizations, and most healthcare entities are covered by at least one, some by two.
Most U.S. hospitals fall under Section 504 because they participate in Medicare and Medicaid.
Many healthcare organizations are covered by more than one of these laws. A federally qualified health center, for example, falls under both Section 504 (HRSA funding) and Title III (private nonprofit status).
The good news is you don't need a separate compliance program for each one. All three laws require the same accessibility standard: WCAG 2.1 Level AA. So if you meet that standard, you're meeting all three. The only thing that changes from law to law is who enforces it.
What Counts as a Covered Digital Property?
Title II’s web accessibility requirements apply to all web content and mobile applications operated by a covered entity. For a healthcare organization, that scope is wider than most compliance teams realize:
Public-facing websites
Patient portal
Mobile apps (patient-facing and provider-facing if the provider side serves the public in any way)
Telehealth platform
Online scheduling and intake forms
Payment and billing forms
In-facility kiosks (check-in, wayfinding, prescription pickup)
Patient-facing modules in an EHR
Embedded third-party widgets (chatbots, appointment reminders, symptom checkers, etc.)
An important note: Vendor-built does not mean vendor-covered. For example, if your patient portal is licensed from Epic or Cerner, your telehealth platform is white-labeled from a vendor. Or if your scheduling form is embedded from a third party, the covered entity, your organization, is still responsible for compliance. “Our vendor handles it” is not a defense the DOJ has accepted.
)
What Title II Healthcare Compliance Actually Requires
For healthcare organizations to be considered ADA-compliant, you must meet the guidelines outlined in WCAG 2.1 Level AA. Accessible design is the starting point for meeting those requirements, but meeting ADA requirements is an ongoing process, not a one-time audit.
The rest of this section outlines what that process actually looks like.
Documentation
Title II compliance leaves a paper trail. You need an accessibility statement that’s findable from your homepage, conformance reports that show where you stand against WCAG 2.1 Level AA, and fix records that show what you’ve fixed and when. If your organization receives a complaint, your documentation is the first thing investigators will ask for.
Ongoing Accessibility Improvements
Healthcare websites change constantly. New patient education pages, new portal features, and new telehealth integrations — each can inadvertently introduce accessibility issues. A compliant site today is not a compliant site in six months unless someone is actively maintaining it. That means periodic accessibility testing on a defined cadence, a published complaint procedure, and a designated accessibility coordinator who actually owns the program.
Vendor and Platform Responsibility
As mentioned above, you’re responsible for everything on your website, even if a vendor builds it. That includes your patient portal, your telehealth platform, your scheduling forms, and any embedded tools. To stay compliant, your organization needs to:
Require accessibility in every vendor contract
Test what vendors deliver, the same way you test your own work
Make accessibility part of how you choose a vendor
Most public hospitals work with a lot of vendors, so this is where compliance gaps usually show up.
Enforcement and What’s at Stake
If your organization isn’t compliant with the ADA, three things can happen:
A demand letter from a law firm. This is the most common first contact. ADA demand letters usually arrive before the DOJ gets involved, and most settle for somewhere between $50,000 or more.
A DOJ investigation. This happens when complaints pile up against the same organization or when the DOJ sees a pattern across a region.
A lawsuit from an individual. Title II gives people the right to sue your organization directly if they can’t access your services.
Public hospitals also face two extra layers of risk. State attorneys general are paying closer attention to accessibility, and an accessibility settlement in healthcare can severely damage patient trust and increase additional litigation.
How AudioEye Helps Healthcare Organizations Meet Title II
Title II compliance isn’t a project you “finish.” It’s a program you run, and for most public healthcare organizations, that’s exactly the problem. The documentation, ongoing testing, vendor oversight, and coordinator responsibilities don’t go away after the first audit. They compound.
AudioEye is built for that reality. Our platform combines AI-powered automation, expert audits, and expert-written custom fixes in one system, giving designated coordinators a single place to manage continuous coverage, track conformance, and produce reporting that withstands DOJ scrutiny. A public hospital with a patient portal, a county telehealth integration, and a dozen patient-facing forms gets protection across the entire system, without building an internal accessibility team from scratch.
See how AudioEye supports healthcare accessibility. Schedule a demo now.
Frequently Asked Questions
Share Article
)
)
)