The Department of Justice’s rule under Title II of the Americans with Disabilities Act requires state and local governments to make their web content and mobile apps conform to WCAG 2.1 Level AA. On April 20, 2026, the DOJ published an Interim Final Rule in the Federal Register extending the original compliance dates by one year. Public entities serving populations of 50,000 or more must comply by April 26, 2027. Entities under 50,000, and all special district governments, must comply by April 26, 2028.
The extension changed the timing, not the substance. The requirements, the technical standard, and the exposure for non-compliance are unchanged. The DOJ said plainly in the rule that it fully anticipates implementing the regulation at the new deadlines. In other words, the clock was reset, not stopped.
Who the Rule Covers
The rule applies to every state and local government entity. That includes cities, counties, school districts, community colleges, public universities, transit authorities, courts, police departments, public hospitals, libraries, and special districts such as water or park districts.
Two details trip entities up. First, your deadline depends on total population as defined in the rule, not on the size of your staff or budget. State-level entities are generally measured by state population under the rule, which places most of them, including public universities, in the April 26, 2027 group. Confirm your entity’s classification before relying on the later date. Second, ADA.gov’s guidance is explicit that a school district is not a special district government. School districts follow the population-based deadline like any other public entity.
The rule also covers web content and apps provided for the entity by contractors and vendors. If a third party runs your payment portal, your permit system, or your class registration platform on your behalf, that content is your compliance obligation. You cannot outsource the service and the responsibility with it.
What Must Conform
The scope is broad by design. It includes:
- Public-facing web content on every site the entity operates, including microsites and department subdomains.
- Mobile apps the entity provides, whether built in-house or by a vendor.
- Documents posted on the entity’s sites: PDFs, Word files, PowerPoint decks, and Excel spreadsheets.
- Third-party platforms used to deliver services, such as payment portals, reservation systems, and forms.
Limited exceptions exist. They cover archived content, preexisting electronic documents that are not currently used to apply for or access services, individualized password-protected documents, preexisting social media posts and third-party content the entity does not control and did not procure.
Read those exceptions narrowly, because the DOJ does. Each one has specific conditions, and content loses its exception the moment it is used to offer or deliver a current service. A 2019 PDF is not “preexisting” in the rule’s sense if residents still need it to apply for a permit today. Misclassifying content as exempt is one of the most common failure patterns we see in audits. Entities assume whole document libraries are archived when most of the files are still doing active work.
What Compliance Actually Takes
Getting a public entity to WCAG 2.1 Level AA is a program, not a project. Here is the path we recommend, sequenced to fit the time remaining before your deadline.
1. Baseline audit. Start with a full WCAG 2.1 AA audit of your websites, mobile apps, and document libraries. Automated scanning catches only a minority of WCAG failures. The rest require expert manual testing with assistive technology such as screen readers. The rest require expert manual testing with assistive technology such as screen readers. The audit should produce an inventory: what you have, what fails, and how severe each failure is.
2. Remediation plan sequenced by impact. Fix the content residents actually use first. Prioritize by traffic and service criticality: payment systems, permit applications, enrollment, emergency information, and transit schedules before legacy pages nobody visits. A documented, dated remediation plan is also your best evidence of good faith if a complaint arrives before you finish.
3. Document remediation at scale. Most public entities are sitting on thousands of PDFs. Triage them: retire what you can, apply the exceptions honestly, and remediate what remains to PDF/UA and WCAG standards. This workstream takes longer than most entities expect, so start it early.
4. Vendor and procurement language. Since vendor-provided content counts against you, your contracts have to carry the obligation. Require WCAG 2.1 AA conformance in new procurements, ask vendors for current accessibility documentation, and test their claims before renewal.
5. Ongoing monitoring. The deadline is not a finish line. Your sites change daily, and the rule requires you to be conformant on April 26, 2027 and every day after. Build a monitoring practice with scheduled scans, periodic manual testing, and staff training so new content is published accessible instead of fixed later.
Where We Come In
Accessibility Innovations helps public entities get to WCAG 2.1 AA and stay there. We deliver expert WCAG 2.1 AA website audits combining automated and manual assistive-technology testing, document accessibility remediation for PDF, Word, PowerPoint, and Excel libraries at scale, and accessibility training so your content teams stop creating new barriers. For entities that need to hold conformance after the deadline, our compliance management service provides scheduled scanning and evidence reporting, so you can show regulators and residents exactly where you stand at any time.
Don’t Spend the Extension Waiting
The DOJ gave public entities one extra year because so many were not ready. A full audit, a document backlog, vendor renegotiation, and remediation take most entities 12 to 18 months. That means the extension is not slack, it is the runway. Book a free consultation and we will scope your fastest path to WCAG 2.1 AA before your deadline arrives.
