The April 24, 2026, deadline many state and local government teams had been working toward for meeting the ADA Title II web and mobile accessibility requirements is no longer the current compliance date. In April 2026, the Department of Justice extended the timeline by one year.
For public entities with a total population of 50,000 or more, the current deadline is April 26, 2027. Public entities with a population under 50,000, along with special district governments, now have until April 26, 2028.
That update matters because outdated information is still circulating. Teams that planned around the original deadline should update their plans, communications, vendor expectations, and internal milestones to reflect the current rule.
The additional runway creates an opportunity to build accessibility into everyday digital work rather than relying on a last-minute push. For larger public entities, April 2027 is close enough to require focused action now.
What the DOJ’s Interim Final Rule actually did
The Department of Justice published its Interim Final Rule on April 20, 2026. The rule changed the compliance dates in the 2024 web and mobile application accessibility rule by one year.
For ADA Title II, the updated deadlines are:
April 26, 2027: State and local government entities with a total population of 50,000 or more
April 26, 2028: State and local government entities with a total population below 50,000, plus special district governments
The population calculation is based on the public entity’s total population under the rule’s methodology. It is not necessarily the number of people who use a service, visit a website, or attend a public university.
The Interim Final Rule applies to state and local government entities. This includes many:
- Cities
- Counties
- Public school districts
- Public colleges
- Public universities
- Libraries
- Transit agencies
- Other public entities
- Vendors and contractors that provide websites, apps, or digital content through contractual, licensing, or other arrangements with public entities
What has not changed
The deadline moved, but the technical standard did not. The rule continues to require covered public entities to ensure that relevant web content and mobile apps meet WCAG 2.1 Level AA.
The rule’s scope also remains the same. It addresses web content and mobile applications that public entities provide or make available directly or through arrangements with third parties. This means accessibility planning should include public-facing websites, online forms, mobile apps, digital service portals, embedded tools, and documents connected to those services.
The Interim Final Rule did not rewrite the 2024 requirements or replace WCAG 2.1 Level AA with a different version of the standard. It changed the dates only. The Department states that the amendments “do not alter any other provisions” of the 2024 final rule.
Title II is also still distinct from private-sector accessibility obligations. This specific rule applies to state and local government entities, not to every U.S. business or professional. For broader context on the law and digital access, see how the ADA shapes digital accessibility.
Why more time still calls for focused planning
The extension gives public entities more time to prepare. It also recognizes the practical work involved in reviewing complex websites, document libraries, mobile applications, publishing practices, and third-party tools.
In its Interim Final Rule, the Department cited reported resource constraints and slower-than-expected advancement and availability of technology as factors behind the extension. The Department also stated that it expects to implement the regulation at the revised deadlines.
This is a useful window for a structured approach to accessibility. A thoughtful program can improve access for residents, students, employees, and visitors while giving teams time to establish durable processes.
The extension is also the subject of a federal court challenge filed by the National Federation of the Blind. The case challenges the deadline extensions, and its outcome remained pending as of October 8, 2026.
The underlying accessibility obligation remains important regardless of that litigation. Public entities have longstanding responsibilities to provide equal access to their services, programs, and activities, and the 2024 rule provides a clear technical benchmark for web content and mobile apps.
Use the six-month runway to create lasting capability
For larger entities, the period before April 26, 2027 is best used to create a practical, repeatable accessibility program. A clear workflow helps teams move forward without trying to solve every issue at once.
Start with an inventory. Identify the websites, mobile apps, online forms, PDFs, shared document libraries, and third-party platforms that support public services. Include content managed by communications teams, departments, educational institutions, and external vendors.
Prioritize high-impact user journeys. Focus early work on tasks people need to complete independently. That may include tax payments, emergency updates, class registration, school communications, permit requests, and service forms.
Assess the current experience. Combine automated evaluation with human review. Automated tools can identify many technical issues, while manual review helps confirm whether a page, form, app, or document is understandable and usable with assistive technology.
Remediate critical barriers. Address the issues that most directly affect access to essential services. For websites and apps, that may include keyboard access, form labels, heading structure, focus visibility, error messages, and media alternatives. For PDFs, it may include reading order, document tags, tables, images, links, and form fields.
Improve how new content is created. Accessible authoring practices, templates, training, procurement requirements, and quality checks can reduce the amount of remediation required later. Include accessibility expectations in vendor agreements and ensure external partners understand their responsibilities.
Measure and maintain progress. Accessibility is an ongoing operational practice. Establish owners for key digital properties, track remediation work, review new content before publication, and create a clear process for responding to feedback.
The Department of Justice similarly encourages public entities to determine which of their web content and mobile apps must meet WCAG 2.1, prioritize remediation, train staff, and review vendor relationships.
Support accessibility through practical tools and workflows
Tools help teams make accessibility work more manageable, especially when content is distributed across multiple departments. The most effective approach combines accessible authoring, automated checks, remediation capability, and human review.
Authoring-first tools help prevent barriers from entering a workflow. For teams creating source documents in Microsoft Office, Grackle Office supports accessibility checking and remediation before files are shared or converted to PDF.
Existing PDFs require a different approach. Grackle PDF supports PDF accessibility validation and guided remediation for tags, reading order, tables, links, images, form fields, and metadata. The guided process supports measurable improvements to document structure and accessibility.
Automation can accelerate early work, particularly when teams are reviewing a large volume of content. It can identify missing metadata, incomplete tagging, unlabeled form elements, and other machine-detectable issues. Human review remains important for decisions that depend on context, such as whether alternative text conveys the purpose of an image, whether a table communicates relationships clearly, or whether a reading order truly makes sense.
A strong workflow gives content creators practical support while providing accessibility, legal, and compliance teams with visibility into progress. It also helps public entities create digital services that are clearer and more usable for everyone.
Turn the extension into meaningful progress
The current ADA Title II compliance deadline for larger public entities is April 26, 2027. That date is a practical planning marker for creating more accessible websites, mobile apps, documents, and digital services.
Start with the content and services people rely on most, establish a clear remediation plan, and strengthen accessible publishing practices across the organization.
Get started with Grackle PDF to explore guided PDF accessibility remediation and validation for your public-facing documents.
