The ADA Title II web and mobile accessibility compliance dates have shifted, but the practical work for public entities is still urgent. In April 2026, the Department of Justice issued an interim final rule that extended the compliance dates by one year. For many teams, that created a little more runway. It did not remove the need to build an inventory, test real service journeys, remediate barriers, document decisions, and bring vendors into the accessibility plan.
The important change is simple: large public entities now have until April 26, 2027, while smaller public entities and special district governments have until April 26, 2028. Teams that were planning around the original 2026 and 2027 dates should update calendars, executive briefs, procurement plans, and remediation roadmaps.
The new ADA Title II dates
- State and local governments with a total population of 50,000 or more: April 26, 2027.
- State and local governments with a total population below 50,000: April 26, 2028.
- Special district governments: April 26, 2028.
- The technical baseline remains WCAG 2.1 Level AA for covered web content and mobile apps.
The extra year is most useful when it is used to sequence the work correctly. Accessibility projects get expensive when teams start with isolated page scans and discover late that the largest barriers live in PDFs, payment forms, permit workflows, third-party portals, embedded maps, or systems owned by vendors.
What did not change
Public entities still need an accessible digital service model. Residents, applicants, students, patients, vendors, employees, and members of the public still need to complete essential tasks. A deadline extension does not make an inaccessible benefits form, emergency update, public notice, mobile app, or payment flow easier to use today.
The legal date is only one part of the operating risk. Public trust, service access, complaint response, procurement accountability, and staff workload all depend on whether teams understand the real surface area and can show steady progress.
How teams should use the extra time
- Update leadership materials with the new dates and the unchanged WCAG 2.1 AA baseline.
- Create an inventory of websites, mobile apps, portals, forms, documents, vendors, and high-impact service journeys.
- Prioritize tasks people depend on before low-risk cosmetic cleanup.
- Use accessibility RFP language to ask vendors for current accessibility conformance reports, known exceptions, and remediation timelines.
- Turn findings into a backlog with owners, severity, public impact, due dates, and acceptance criteria.
- Create governance so new pages, documents, embeds, and releases do not recreate the same barriers.
The next useful step
Start with the services the public depends on most. A single priority journey can reveal the patterns that will shape the broader plan: unlabeled fields, inaccessible PDFs, missing focus states, unclear error handling, third-party barriers, content governance gaps, or templates that keep reproducing issues.
The deadline moved. The work is still real. Teams that start now can turn accessibility from a scramble into a manageable program with clear ownership, measurable progress, and better public service delivery.