The ADA Title II web accessibility deadline: what nonprofits and health centers need to know

The short version: In 2024, the U.S. Department of Justice finalized a rule under Title II of the Americans with Disabilities Act that makes WCAG 2.1 Level AA the technical standard for websites and mobile apps. Public entities serving 50,000 or more people must comply by April 26, 2027; smaller entities and special districts have until April 26, 2028. If your organization is a government entity — or works closely with one — this is now a deadline, not a suggestion.

What actually changed

Website accessibility has been litigated for years, but the law rarely named a specific technical bar. That ambiguity is gone for the public sector. The DOJ's rule adopts the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — a widely used, testable set of criteria published by the W3C — and ties it to firm compliance dates. For the first time, "is our website compliant?" has a concrete answer you can measure against.

The deadlines

• April 26, 2027 — public entities serving a population of 50,000 or more.
• April 26, 2028 — smaller public entities (under 50,000) and special districts.

The standard is the same for everyone: WCAG 2.1 Level AA. Only the timeline differs by the size of the entity.

Does this apply to nonprofits and health centers?

This is where it gets nuanced, and where a careful answer matters. Title II directly covers state and local government entities. Many nonprofits and community organizations are still affected — in one of two ways:

• Directly, as public accommodations. Under Title III of the ADA, businesses and nonprofits open to the public have long faced accessibility obligations, and courts routinely reference WCAG as the yardstick — even though Title III doesn't yet name its own technical standard.
• Indirectly, through government ties. Organizations that receive government funding, operate under government contracts, or deliver services on behalf of a public entity can find the public entity's obligations flowing through to them.

Community health centers sit squarely in this overlap: they serve the public, and they're deeply intertwined with federal and state funding. Even where a center isn't strictly bound by the Title II date, that date has become the practical benchmark everyone is being measured against. If you're unsure which category you fall into, confirm it with legal counsel — the right answer depends on your specific structure and funding.

What WCAG 2.1 AA means in plain terms

You don't need to memorize the guidelines to understand the spirit of them. In practice, AA conformance means things like:

• Every meaningful image has descriptive alternative text so screen-reader users know what it shows.
• Text has enough color contrast against its background to be readable.
• The entire site can be operated with a keyboard alone, with a visible focus indicator.
• Every form field has a proper label that assistive technology can announce.
• Content is structured with real headings and landmarks, not just visual styling.
• Motion and animation respect a visitor's “reduce motion” preference.

Why waiting is the expensive option

Beyond the regulatory deadline, there's litigation risk that already exists today. Web accessibility complaints and lawsuits have climbed sharply in recent years, and healthcare is among the most frequently targeted sectors. An inaccessible site is also a quieter cost: patients and community members who can't use it simply go elsewhere. Accessibility done well isn't only about avoiding a lawsuit — it widens the front door to the people you exist to serve.

What to do now

1. Get an honest audit. Have your site checked against WCAG 2.1 AA so you know exactly where you stand and what's worth prioritizing.
2. Decide: remediate or rebuild. Sometimes targeted fixes are enough. Often — especially on dated, vendor-locked sites — it's faster and cheaper to migrate to an accessible, self-managed platform than to patch the old one indefinitely.
3. Document your conformance. Keep a record of the work and publish an accessibility statement, so you have evidence of good-faith compliance.