October 19, 2026

ADA Title II Web Deadline Extended to April 2027: What Changed and What to Do Now

On April 20, 2026, the U.S. Department of Justice published an Interim Final Rule that pushes back the dates by which state and local governments must make their websites and mobile apps accessible. If you work for a city, county, school district, public university, transit agency or special district, here is what changed, what did not, and how to use the extra time well.

The new dates

Who Old deadline New deadline
State and local governments serving 50,000 or more people April 24, 2026 April 26, 2027
Governments serving fewer than 50,000 people, and all special district governments April 26, 2027 April 26, 2028

The rule took effect on the day it was published. The Department also opened a public comment period that closed on June 22, 2026.

What did not change

The extension moves the dates. It does not lower the bar.

  • The standard is still WCAG 2.1 Level AA. The rule covers web content and mobile apps that a government provides or makes available, including through contractors and outside vendors.
  • The same exceptions still apply. These include archived content kept only for reference, documents posted before the deadline that nobody uses to get services, content posted by unrelated third parties, password-protected documents about a specific person or account, and social media posts made before the deadline. Each exception has conditions, so check the details on ada.gov before relying on one.
  • Existing duties still apply. Governments still have to provide effective communication and reasonable modifications to people with disabilities today, deadline or not.

Why "we have another year" is risky thinking

A year sounds like a lot until you count what has to happen inside it. Most public websites have hundreds or thousands of pages, plus PDFs, forms and third-party tools such as payment portals and meeting platforms. Vendors have to be asked for fixes, and contracts may need new accessibility terms. Content editors need training so new pages don't undo the work.

The most common problems are also the most fixable. WebAIM's 2026 analysis of the top one million home pages found that low-contrast text, missing image alternative text, unlabeled form fields, empty links, empty buttons and a missing page language made up 96% of detected errors. Automated tools find these quickly.

A practical plan for the next 12 months

  1. List what you publish. Websites, subdomains, mobile apps, online forms, PDFs people use to apply for things, and vendor tools you link to.
  2. Run an automated scan of every site. It gives you a baseline score and finds the common problems in hours instead of weeks.
  3. Fix the critical problems first. Missing form labels, keyboard traps and images without text block people completely. Contrast and heading problems come next.
  4. Ask your vendors. Request each vendor's accessibility conformance report (often a VPAT) and a date for fixing known gaps.
  5. Test the important tasks by hand. Paying a bill, applying for a permit or finding a meeting agenda should work with only a keyboard and with a screen reader. Automated tools cannot judge this.
  6. Publish an accessibility statement and a way to report problems. People need a way to tell you when something doesn't work.
  7. Keep monitoring. New pages and updates bring new problems. A dated record of regular scans also shows the steady effort regulators and courts look for.

How WCAG Pulse can help

WCAG Pulse scans your sites against WCAG 2.1 and 2.2 on a schedule, lists every problem with where it is and how to fix it, and keeps a history you can download as a PDF. It can also publish an accessibility statement that updates after each scan. You can check a page for free with no account, or monitor one site free with monthly rescans.

Automated scans find many problems, but not all of them, so pair them with manual testing.

This article explains public information and is not legal advice.

Sources