Summary
ADA Title II requires all state and local government websites and mobile apps to meet WCAG 2.1 Level AA. The first compliance deadline for entities with populations of 50,000 or more is April 24, 2026. Entities with populations under 50,000 and special district governments must comply by April 26, 2027.
The April 24, 2026 compliance deadline under ADA Title II has arrived. For state and local governments serving populations of 50,000 or more, the obligation to meet WCAG 2.1 Level AA on their websites and mobile apps is no longer forthcoming. It is current law, enforceable today.
If your organization is in that first tier and hasn't completed your accessibility audit and remediation, you are now operating in an enforcement window. DOJ enforcement actions, administrative complaints and private lawsuits by individuals with disabilities are all live risks. For entities with populations under 50,000 and special district governments, the deadline is April 26, 2027 but the planning work needs to be underway now.
This article breaks down what ADA Title II actually requires, who it covers, the technical standard at its core and what the post-deadline landscape means for government agencies and the organizations that contract with them.
What is Title II of the ADA?
Title II of the ADA provides that no qualified individual with a disability shall, by reason of such disability, be excluded from participation in or denied the benefits of the services, programs, or activities of a public entity.
What does the rule cover?
This rule aims to ensure that people with disabilities can access the services, programs, and activities offered by state and local governments through websites and mobile apps. Additionally, it will offer clearer guidelines for state and local governments to comply with the ADA.
Making these government websites and mobile apps accessible to everyone is an important part of digital equity.
What is the technical standard specified?
The Department of Justice (DOJ) has set specific requirements to ensure state and local governments comply with the Americans with Disabilities Act (ADA) Title II. WCAG 2.1, Level AA is the technical standard for state and local governments’ web content and mobile apps.
Understanding the ADA Accessibility Guidelines: WCAG 2.1 at a Glance
When people ask about ADA accessibility guidelines for websites, they are really asking about WCAG 2.1 Level AA, the technical standard the DOJ formally adopted in its final rule. WCAG stands for Web Content Accessibility Guidelines, published by the World Wide Web Consortium (W3C). Level AA is the middle conformance tier, more rigorous than Level A, but achievable for most government digital properties without exceptional engineering effort.
WCAG 2.1 is organized around four principles, often called POUR. Content must be Perceivable (users can see or hear it), Operable (users can navigate using keyboard or assistive technology), Understandable (content is readable and predictable), and Robust (content works reliably with current and future assistive technologies).
Who does this apply to?
The new rule applies to all state and local governments (which includes any agencies or departments of state or local governments) as well as special purpose districts, Amtrak, and other commuter authorities. State and local governments that contract with other entities to provide public services for them also have to make sure that their contractors follow Title II.
Examples of state and local governments include:
-
- Food assistance, health insurance, or employment services
-
- Public schools, community colleges, and public universities
-
- State and local police departments
-
- State and local courts
-
- State and local elections offices
-
- Public hospitals and public healthcare clinics
-
- Public parks and recreation programs
-
- Public libraries
-
- Public transit agencies
Compliance Deadlines
State and local governments must make sure that their web content and mobile apps meet WCAG 2.1, Level AA within two or three years of when the rule is published, depending on their population.
-
- For public entities with a population of 50,000 or more, the compliance date is April 24, 2026.
-
- For public entities with a population of less than 50,000 or a special district government, the compliance date is April 26, 2027.
How to know the total population of a school district?
-
- If it is a city school district, it would use the population of the city to know when to comply.
-
- For a county school district, it would use the population of the county.
-
- If it is an independent school district, it would use population estimates.
| Entity type | Population threshold | Compliance deadline |
|---|---|---|
| State/local governments, public universities, Amtrak, commuter authorities | 50,000 or more | April 24, 2026 |
| State/local governments | Fewer than 50,000 | April 26, 2027 |
| Special district governments | Not calculated by Census | April 26, 2027 |
Exceptions
The DOJ has set forth specific exceptions - If the content falls under an exception, that means that the public entity would not need to make the content conform to WCAG 2.1 Level AA. However, a person may request the public entity to provide the web content or content in mobile apps to in an accessible format and the entity will need to address the person’s request.
-
- Archived web content
-
- Content posted by a third party where the third party is not posting due to contractual, licensing, or other arrangements with a public entity
-
- Preexisting conventional electronic documents
-
- Individualized documents that are password-protected
-
- Preexisting social media posts
Use of Conforming Alternate Versions
The concept of conforming alternate versions refers to having two versions of the same content:
-
- Inaccessible main version: This is the primary page most users see.
-
- Accessible alternate version: This is a separate page with the same information but designed to be accessible for people with disabilities.
The use of conforming alternate versions is, however, discouraged as the goal is for everyone to have equal access to the information directly on the main page. There is limited exception for the Alternate Versions. The rule allows conforming alternate versions where there must be a technical barrier (e.g., limitations of a specific software) or a legal restriction preventing the main page from being accessible.
For any other scenario, the focus should be on making the main content accessible to all users directly.
Minor Accessibility Issues: A Narrow Exception
The rule acknowledges that there might be some rare cases where a government website or app doesn't fully meet WCAG accessibility standards in a very minor way.
-
- Focus on No Impact on Users: The key factor is whether this minor issue actually hinders access to the information or functionality for people with disabilities.
-
- Difficult to Claim Exception: It is important to note that governments can't simply use this as an excuse to avoid making accessibility efforts.
-
- High Burden of Proof: If a government agency does claim this exception, they would have to provide significant evidence to demonstrate that the minor issue has no real-world impact on accessibility.
In simpler terms, while there's a narrow exception for absolutely minimal accessibility issues, the overall emphasis is on state and local governments taking concrete steps to make their websites and apps accessible to everyone.
What happens if you miss the April 2026 deadline?
Missing the April 24, 2026 deadline does not simply mean your organization is out of compliance on paper. It opens the door to real enforcement consequences. Under ADA Title II, the DOJ has the authority to initiate enforcement actions, enter consent decrees and impose remediation timelines through administrative proceedings. Separately, individuals with disabilities retain independent private rights to file lawsuits, a path that exists entirely outside the federal enforcement process.
Private organizations that provide digital services to state and local governments are also affected. Contractors, SaaS vendors and service providers are increasingly being required to meet WCAG 2.1 AA as a condition of government contracts. If your product or platform is deployed inside a covered entity's ecosystem, your client's obligation effectively becomes yours.
The most practical step any organization can take right now is a professional ADA accessibility audit, a structured assessment of where your digital properties stand against WCAG 2.1 AA, followed by a prioritized remediation plan. Documented, good-faith compliance efforts matter in enforcement proceedings. Waiting does not.
Conclusion
The ADA Title II rule is no longer a future obligation. It is a present one. For larger public entities, the compliance window is closing. For those approaching the 2027 deadline, time is shorter than it looks. Accessibility audits, remediation and accessibility policy changes all take significant planning cycles to execute properly.
If you work with state or local government agencies, or if your organization is itself a covered entity, the right move is to assess your current conformance posture against WCAG 2.1 Level AA and close the gap before enforcement catches up. BarrierBreak's accessibility testing team has been working with government agencies and enterprise organizations on ADA compliance for over two decades. Learn more about our ADA compliance testing service or reach out at sales@barrierbreak.com to talk through your compliance roadmap.