ADA Title II Deadline Delayed? What We Know Right Now (August 2026 Update)

ADA Title II Deadlines: April 2027 and 2028 (What to Know)

The short answer. ADA Title II now sets two web accessibility compliance deadlines, after the Department of Justice extended the original dates by one year in April 2026: April 26, 2027 for public entities serving 50,000 or more people, and April 26, 2028 for smaller public entities and special district governments. The required standard is WCAG 2.1 Level AA.

If you run or build for a state or local government website, the deadline did not disappear. It moved, and it is now split by the size of the population you serve.

What changed, and when

• April 2024: the DOJ published its final rule under ADA Title II, setting web and mobile accessibility requirements for state and local governments for the first time, with deadlines of April 24, 2026 (entities serving 50,000+) and April 26, 2027 (entities under 50,000 and special districts).
• Early 2026: the DOJ moved to revisit those dates, and an Interim Final Rule entered the process.
• April 20, 2026: the DOJ finalized the Interim Final Rule, extending each deadline by roughly one year. The requirement itself (WCAG 2.1 AA) did not change; the time to meet it did.

So the earlier "is the deadline delayed" uncertainty is resolved: yes, it was extended, and the new dates are firm.

The two deadlines, by who you are

Your entity	Compliance deadline
Public entity serving a population of 50,000 or more	April 26, 2027
Public entity serving fewer than 50,000, and special district governments	April 26, 2028

These cover the websites and mobile apps that state and local governments use to offer their services, programs, and activities to the public. If a private contractor delivers a government service on the entity's behalf, that service is generally expected to meet the same standard.

What the standard actually requires: WCAG 2.1 Level AA

The rule points to a specific, testable target: the Web Content Accessibility Guidelines (WCAG) version 2.1, Level AA. In practice that means your site works for people using screen readers, keyboard navigation, and other assistive technology, and that things like color contrast, form labels, headings, and focus order meet the Level AA success criteria.

WCAG 2.1 AA is the same bar most other accessibility laws reference (the ADA more broadly, Section 508, the EAA in Europe), so meeting it here also moves you toward compliance elsewhere.

What "compliant" means here, honestly

Reaching WCAG 2.1 AA is not something a single automated tool can certify on its own. Automated testing reliably catches a large share of issues (missing alternative text, insufficient contrast, missing form labels), but it cannot judge whether alternative text is meaningful, whether a screen reader can complete a form, or whether the keyboard path through a service actually works. Those require a person.

The workable path is to automate what is safe to automate, put an expert on the rest, and keep a record of what you tested and fixed, so you can show your work if a complaint arises.

The risk of waiting

Missing the deadline does not trigger an automatic fine, but it does raise real exposure: complaints to the DOJ, DOJ enforcement action, and private lawsuits, all of which are far more expensive and disruptive than remediating ahead of time. For public entities, an inaccessible service also means residents who cannot access benefits, permits, records, or emergency information they are entitled to. The cost of accessibility caught early is a fraction of the cost caught under a complaint.

How to prepare before your deadline

1. See where you stand. Run a free accessibility scan of your site against WCAG 2.2 to get a categorized list of issues, and run your site through the free ADA Title II compliance checker.
2. Get an expert audit of the pages and services that carry the most risk (anything a resident must be able to complete). See how a professional accessibility audit works.
3. Remediate, automating the machine-fixable issues and putting a human on the rest.
4. Document what you tested, what you fixed, and your ongoing plan. See our broader ADA compliance guidance.

Starting now, well before April 2027 or 2028, is the difference between a planned project and a scramble under a complaint.

Frequently asked questions

What is the ADA Title II web accessibility deadline?

There are two, after the April 2026 extension: April 26, 2027 for public entities serving 50,000 or more people, and April 26, 2028 for smaller entities and special district governments.

Was the ADA Title II deadline extended?

Yes. The DOJ finalized an Interim Final Rule on April 20, 2026 that extended the original 2026 and 2027 deadlines by about one year, to 2027 and 2028. The WCAG 2.1 AA standard did not change.

Which deadline applies to us?

It depends on the population you serve. Entities serving 50,000 or more have until April 26, 2027; entities under 50,000 and special district governments have until April 26, 2028.

What standard do we have to meet?

WCAG 2.1 Level AA, for the websites and mobile apps your government uses to offer services to the public.

What happens if we miss the deadline?

There is no automatic fine, but you face DOJ complaints and enforcement and private lawsuits, and residents lose access to services they are entitled to. Remediating early is far cheaper than responding to a complaint.

See where your site stands

The deadline moved, but it did not go away, and the work takes time. Run a free accessibility scan against WCAG to see your issues in seconds, no signup. For the pages that carry real risk, our IAAP-certified team handles the audit and remediation.