The compliance deadlines most government and education websites were preparing for just shifted by one year. In April 2026, the Department of Justice extended the original ADA Title II digital accessibility deadlines, giving covered entities more time but no change in what’s required.
WCAG 2.1 Level AA is still the standard. The scope of covered content is unchanged. And the consequences for non-compliance, including DOJ investigations, private lawsuits, and significant litigation risks, remain exactly the same.
This article covers everything covered entities and their web partners need to know right now.
Here’s what we cover:
- What the ADA Title II final rule requires and who it covers
- The updated compliance dates after the April 2026 extension
- What content and mobile apps must be accessible
- Exceptions that apply and how narrowly they are construed
- The consequences of missing compliance deadlines
- A practical step-by-step compliance preparation plan
Our WordPress ADA compliance service helps government agencies, local governments, and educational institutions audit their websites and reach WCAG 2.1 Level AA compliance. If your deadline is approaching, get in touch, and we’ll walk you through exactly what your site needs.
Background: the ADA Title II final rule
On April 24, 2024, the U.S. Department of Justice (DOJ) finalized a new rule under Title II of the Americans with Disabilities Act (ADA), imposing significant digital accessibility requirements on public entities, including public colleges and universities.
Title II of the Americans with Disabilities Act prohibits discrimination by state and local government entities on the basis of disability. For decades, the ADA required that government services be accessible, but those requirements applied primarily to physical spaces. The 2024 final rule extended those obligations formally and explicitly to digital environments: websites, web content, mobile apps, and supporting documents.
The rule was published on April 24, 2024, and took effect on June 24, 2024. The Department of Justice adopted WCAG 2.1 Level A/AA as the benchmark for accessible websites, mobile apps, and digital documents across state and local governments.
The rule applies to all state or local government covered entities, regardless of size, though the compliance dates differ based on the total population served.
Updated compliance dates: what changed in April 2026
The original compliance deadlines were April 24, 2026, for large public entities and April 26, 2027, for smaller entities and special district governments. On April 17, 2026, the DOJ issued an interim final rule extending both dates by one year.
The DOJ’s Interim Final Rule (IFR) adjusts two compliance dates. Public entities with a total population of 50,000 or more: April 24, 2026, moves to April 26, 2027. Public entities with a total population under 50,000, and any special district government: April 26, 2027, moves to April 26, 2028. The IFR was signed on April 16, 2026, by Acting Attorney General Todd Blanche.
Here are the current compliance deadlines:
| Entity type | Total population | Compliance date |
|---|---|---|
| Large public entities | 50,000 or more | April 26, 2027 |
| Smaller public entities | Under 50,000 | April 26, 2028 |
| Special district governments | Any size | April 26, 2028 |
Critical note: The substantive requirements of the 2024 final rule remain unchanged. WCAG 2.1 Level AA is still the technical standard for web content and mobile app accessibility under ADA Title II. The only change is timing. Covered entities still have ongoing obligations under the ADA itself, independent of the rule’s compliance dates. Accessibility is still required for services, programs, and activities delivered through the web. The extension is not a pause on accessibility work.
Who does the ADA Title II rule cover?
The rule applies to all state and local government entities. This includes but is not limited to:
- City and county governments
- State government agencies and departments
- Public school districts and public universities
- Public libraries
- Special district governments including water districts, transit districts, and fire districts
- Any state or local government entity that offers online services to the public
Local governments that offer online services such as permit applications, utility payments, meeting agendas, public notices, and service request forms are all covered entities under this rule, regardless of the size of the jurisdiction.
Private companies that provide web development, hosting, or content management services to covered entities are not directly covered by the rule, but private companies that work with covered entities are likely to see an increase in the number and stringency of contractual obligations governing digital accessibility in their contracts with public entities.
What content and mobile apps must be accessible
The rule covers a broad range of digital content. Covered entities must ensure the following meet WCAG 2.1 Level AA success criteria:
Web content
- All public-facing web pages and subdomains
- Web pages used to provide government services
- Online forms, including permit applications, registration forms, and service requests
- Documents embedded in or linked from web pages
- Online meeting platforms and virtual government services
Mobile apps
Mobile app accessibility requirements are included in the rule. All mobile applications used to deliver state or local government services must meet the same WCAG 2.1 Level AA standard as web content. This includes apps for paying bills, reporting issues, accessing public transportation, and any other government service delivered through mobile applications.
Documents and file formats
Conventional electronic documents published or made available for download after the compliance date must meet accessibility requirements. This includes:
- Portable document formats (PDFs)
- Word processor file formats such as .doc and .docx
- Spreadsheet file formats such as .xls and .xlsx
- Presentation file formats such as .ppt and .pptx
Preexisting social media posts and archived content
Preexisting social media posts published before the compliance date are excluded from the rule’s requirements. Similarly, archived web content that is kept only for historical reference and not used to provide current services is excluded. However, if archived content is updated or used in current service delivery, the exception no longer applies.
WCAG 2.1 Level AA: what the standard actually requires
The Web Content Accessibility Guidelines (WCAG) 2.1 Level AA is the technical standard incorporated by reference into the final rule. It was developed by the World Wide Web Consortium (W3C) and organizes accessibility requirements around four core principles:
- Perceivable: Information and user interface components must be presented in ways users can perceive.
- Operable: User interface components and navigation must be operable.
- Understandable: Information and the operation of the interface must be understandable.
- Robust: Content must be robust enough to be interpreted reliably by assistive technologies.
Key requirements under WCAG 2.1 Level AA include:
- The ability to navigate the website or platform exclusively via a keyboard, with a visible focus indicator
- Alternative text or text alternatives for images, links, buttons, and other non-text content
- Captions for all prerecorded and live video content
- Sufficient color contrast between text and background elements
- Readable and predictable page structure with proper heading hierarchy
- Error identification and suggestions in forms
- No content that flashes more than three times per second
- Consistent navigation and identification of repeated components
- Text resizable up to 200 percent without loss of content or functionality
WCAG 2.2 has since been released and builds on 2.1 with additional success criteria. While WCAG 2.2 is not currently required under the final rule, beginning compliance planning against WCAG 2.2 can help future-proof digital assets against future rulemaking processes.
Exceptions to the rule
The final rule includes limited exceptions to WCAG compliance requirements. These exceptions are construed narrowly, and covered entities should consult legal counsel before relying on any of them.
Archived web content
Web content maintained solely for historical reference and not used to provide current services is excluded. This applies to true archives, not content that is referenced, updated, or used in active service delivery.
Preexisting conventional electronic documents
Certain preexisting conventional electronic documents, including word processor file formats, spreadsheet files, presentation file formats, and portable document formats, that were available before the compliance date are excluded from the requirement. However, new documents published after the compliance date must be accessible, and preexisting documents used to provide active services remain covered.
Individualized password-protected documents
Individualized password-protected documents created for a specific individual are excluded from the requirement. Documents made available to multiple users are not covered by this exception.
Preexisting social media posts
Social media posts published before the compliance date are excluded. New social media content published after the compliance date is covered.
Third-party content
Content posted by a third party that is not under the direct control of the covered entity and not hosted on the covered entity’s web pages is excluded. However, content published by third parties on behalf of the covered entity or hosted on the entity’s platforms remains covered.
Fundamental alteration and undue burden
A covered entity may be exempt from a specific accessibility requirement if compliance would result in a fundamental alteration in the nature of the service or program, or would impose an undue burden given the entity’s size, resources, and nature of operations. These exceptions are construed narrowly. Covered entities should exercise caution when relying on a potential exception and consult with legal counsel prior to doing so.
The consequences of missing compliance deadlines
Covered entities that fail to meet the ADA digital accessibility deadlines for websites face significant consequences.
DOJ investigations and enforcement
The DOJ can investigate complaints from individuals with disabilities who are denied equal access to government digital services. An investigation can result in required remediation, technical assistance mandates, and ongoing monitoring.
Private lawsuits
Individuals with disabilities and disability advocacy organizations can file private lawsuits against covered entities. Non-compliance carries significant risks, including DOJ investigations and private lawsuits. These can result in costly settlements, mandatory remediation, and legal fees.
Ongoing existing obligations
Even before the specific compliance dates in the final rule take effect, covered entities still have ongoing obligations under the ADA itself, independent of the rule’s compliance dates. This means that relying solely on the deadline extension as justification for not acting creates legal exposure under existing ADA obligations that predate the final rule.
Reputational and community impact
Beyond legal consequences, inaccessible government websites deny equal access to services for residents with disabilities. For local governments specifically, the accessibility of digital services directly affects the community’s ability to participate in civic life, access essential services, and engage with government processes.
A practical compliance preparation plan
Given the extended deadlines, covered entities now have more time to prepare. The extension is not an invitation to delay. It’s an opportunity to do the work properly.
Step 1: Inventory all digital assets
Create a complete inventory of every digital touchpoint your organization maintains, including:
- All websites and subdomains
- Mobile applications
- Online forms and portals
- Linked documents in portable document formats, spreadsheet file formats, and word processor file formats
- Social media accounts and the content posted through them
- Third-party tools embedded in your web pages
Step 2: Conduct a WCAG 2.1 Level AA audit
A thorough audit combines automated scanning with manual expert review. Automated tools identify roughly 30 to 40 percent of accessibility issues. Manual testing by accessibility specialists and users of assistive technology identifies the remaining issues that automated tools miss. Our WordPress ADA compliance service provides exactly this type of combined audit for WordPress-based government and education websites.
Step 3: Prioritize remediation
Not everything can be fixed at once. Prioritize remediation in this order:
- High-traffic web pages used to access essential services
- Online forms, including service requests, permit applications, and registration
- Documents currently in active use for service delivery
- Mobile app content
- Lower-traffic informational pages
- Archived content that qualifies for exception consideration
Step 4: Establish workflows for ongoing compliance
Accessibility compliance is not a one-time fix. Content added after the compliance date must also meet WCAG 2.1 Level AA. Establish content creation workflows that include accessibility review, train staff on document accessibility for word-processor file formats and portable document formats, and implement dynamic compliance assessment standards to catch new issues before they accumulate.
Step 5: Document your compliance progress
Documentation serves two purposes: it helps track progress internally, and it creates a defensible record if your entity faces a complaint or investigation. Document your audit results, your remediation timeline, your staffing and resource allocations, and any decisions made regarding exceptions or undue burden claims.
Step 6: Work with a local web design company experienced in ADA compliance
Whether staffing and budget constraints mean your internal team cannot complete remediation alone, or whether you simply want expert assurance that your implementation meets the technical standard, working with experienced web developers who understand the full requirements of WCAG 2.1 Level AA is one of the most efficient paths to compliance.
Our team has worked with government agencies and local governments across the US on exactly this work. Contact us for a free initial assessment of your current compliance status.
What the deadline extension means for your planning
The April 2026 extension gives covered entities additional time, but it changes nothing about what’s required. The scope of web content and mobile apps covered, the technical standard of WCAG 2.1 Level AA, and the legal obligations under the ADA all remain exactly as they were before the extension.
For entities that were already well into their compliance work, the extension provides breathing room to complete remediation thoroughly rather than rushing through it. For entities that were behind, the extension provides an opportunity to begin. It should not be interpreted as a signal that enforcement is being relaxed or that the requirements may change materially.
Covered entities still have ongoing obligations under the ADA itself, independent of the rule’s compliance dates. The extension addresses the specific deadline in the final rule. It does not eliminate existing legal obligations.
Your deadline is closer than it looks — Freshy helps government and education sites reach compliance
ADA digital accessibility deadlines for websites represent one of the most significant regulatory changes to affect local governments and public institutions in years. The extended timelines give organizations more runway, but accessibility compliance involves auditing, remediation, documentation, and ongoing process changes that take time to implement properly.
Key takeaways:
- The DOJ extended original ADA Title II compliance deadlines by one year in April 2026
- Large public entities with total populations of 50,000 or more must now comply by April 26, 2027
- Smaller public entities and special district governments now have until April 26, 2028
- WCAG 2.1 Level AA is unchanged as the technical standard for all web content and mobile apps
- Covered content includes public-facing websites, mobile applications, online forms, and new documents in portable document, word processor, spreadsheet, and presentation file formats
- Exceptions are narrowly construed and should be evaluated with legal counsel
- The extension does not change existing ADA obligations, which remain in effect regardless of the final rule’s compliance dates
If your organization needs help understanding where it stands and what steps to take next, our WordPress ADA compliance team can audit your site and build a remediation roadmap. Get a free review, and we’ll help you understand your compliance status before your deadline arrives.
FAQs
What are the current ADA digital accessibility deadlines for websites?
Following the April 2026 interim final rule, large public entities with a total population of 50,000 or more must comply by April 26, 2027. Smaller public entities and any special district government must comply by April 26, 2028. The technical standard, WCAG 2.1 Level AA, is unchanged.
Who does the ADA Title II digital accessibility rule apply to?
The rule applies to all state and local government entities, including city and county governments, public school districts, public universities, public libraries, and special district governments. Any state or local government entity that offers online services to the public is a covered entity under the rule.
What content must be accessible under ADA Title II?
All public-facing web content, mobile apps, online forms, and conventional electronic documents in portable document formats, word processor file formats, spreadsheet file formats, and presentation file formats published after the compliance date must meet WCAG 2.1 Level AA. Exceptions apply to archived web content, preexisting conventional electronic documents, individualized password-protected documents, and preexisting social media posts.
What is WCAG 2.1 Level AA?
WCAG 2.1 Level AA is the Web Content Accessibility Guidelines standard developed by the World Wide Web Consortium that defines the technical requirements for accessible web content and mobile apps. It requires keyboard navigability, text alternatives for non-text content, captions for video, sufficient color contrast, and other specific success criteria organized around four principles: perceivable, operable, understandable, and robust.
What happens if a local government misses the ADA digital accessibility compliance date?
Non-compliant covered entities face DOJ investigations, private lawsuits from individuals with disabilities and disability advocacy organizations, costly settlements, and mandatory remediation orders. Covered entities also continue to face existing obligations under the ADA itself that apply independent of the final rule’s specific compliance dates.
How should a local government prepare for ADA website compliance?
Start with a full inventory of digital assets, conduct a WCAG 2.1 Level AA audit combining automated and manual testing, prioritize remediation of high-traffic pages and essential service forms, establish workflows for ongoing accessible content creation, and document all compliance progress. Working with experienced web developers who understand both the technical requirements and the regulatory context accelerates this process significantly.
What web accessibility obligations do local government entities face under federal regulations?
Local governments’ websites must meet WCAG 2.1 Level AA under the ADA Title II final rule published in the Federal Register in April 2024. Local governments’ web content, including all pages where residents gain access to services, must be fully accessible. Entities that fail to comply face significant litigation risks from both DOJ enforcement and private lawsuits filed by disability advocacy organizations.
What do state and local governments need to make accessible beyond their main websites?
State and local governments must ensure web accessibility across everything they offer online, not just their primary websites. Local governments’ web content includes online forms, mobile apps, and such documents as PDFs and spreadsheet files.
Where full remediation is not immediately possible, other arrangements must be provided to ensure residents can still gain access to the same government services through alternative means, consistent with existing obligations under federal regulations.
