ADA Title II Explained

ADA Title II Explained

What It Is, Who It Affects, and Why It Matters Now

ADA Title II is one of the more recent misunderstood but most impactful parts of U.S. accessibility law. It governs how state and local government entities provide access to their services, programs, and digital products. From April it is no longer a theoretical compliance topic. It is actively enforced, increasingly digital, and directly shaping how public sector technology is bought and built.

This article explains what ADA Title II is, what it requires and why it matters to product, engineering, and compliance teams today.

What Is ADA Title II?

ADA Title II is part of the Americans with Disabilities Act (ADA). Its core principle is simple:

State and local governments must ensure people with disabilities have equal access to their services.

Historically, this applied to physical spaces like courthouses, schools, and public transport. Today, it very clearly applies to digital services, including:

• Government websites
• Online forms and applications
• Public sector software platforms
• Citizen portals
• Education, healthcare, and benefits systems

If a government service is available digitally, it must be accessible digitally.

Who Must Comply?

ADA Title II applies to:

• State governments
• Local governments
• Cities, counties, and municipalities
• Public universities and colleges
• Public hospitals and healthcare systems
• Public transport authorities
• Any third-party vendor building or running digital services for the above

This last point is critical. If you sell software, platforms, or digital services to the public sector, ADA Title II applies to you indirectly through procurement, contracts, and liability transfer.

What Does ADA Title II Require Digitally?

ADA Title II does not name a specific technical standard in the statute itself. In practice, enforcement and guidance consistently point to WCAG 2.1 AA as the baseline for digital accessibility.

This means public sector digital services must be:

• Perceivable
  Content can be seen, heard, or otherwise understood by users with disabilities.
• Operable
  Interfaces work with keyboards, screen readers, voice input, and assistive tech.
• Understandable
  Content and interactions are predictable and clear.
• Robust
  Compatible with current and future assistive technologies.

If a citizen cannot use a digital service because of a disability, that is considered discrimination under Title II.

Enforcement Is No Longer Passive

This is the part many teams miss.

ADA Title II is enforced by the U.S. Department of Justice, and enforcement has accelerated. Recent DOJ rule making has made it explicit that:

• Websites and mobile apps are covered
• WCAG 2.1 AA is the expected technical standard
• Compliance is not optional or future-dated
• Lack of resources is not a valid defense

Enforcement happens through:

• DOJ investigations
• Civil complaints
• Settlements and consent decrees
• Procurement disqualification
• Contract termination or non-renewal

In other words, accessibility is now a go to market requirement for public sector technology.

How ADA Title II Affects Procurement

Public sector buyers are under pressure. They are expected to prove that the technology they buy is accessible.

As a result, vendors are increasingly asked for:

• Accessibility conformance statements
• VPATs
• Evidence of ongoing accessibility testing
• Proof accessibility is built into development workflows

If you cannot demonstrate this, you risk:

• Being blocked in RFPs
• Losing deals late in procurement
• Being removed during vendor reviews
• Becoming the compliance liability

This is why accessibility is shifting from a legal checkbox to a product and engineering responsibility.

Common Misconceptions

“We are not a government organization.”
If your customer is, ADA Title II still affects you.

“We passed an audit last year.”
Point in time audits do not equal ongoing compliance.

“Accessibility slows development.”
Accessibility debt slows development. Building it in early does not.

“This is a legal problem.”
It becomes a legal problem when it is not treated as a product problem.

What Good Compliance Actually Looks Like

Strong ADA Title II compliance is not about last minute audits. It looks like:

• Accessibility embedded into design systems
• Automated testing in CI pipelines
• Clear ownership across product and engineering
• Manual testing where automation cannot reach
• Continuous monitoring as products evolve

This is the difference between passing procurement once and staying compliant as you scale.

Why This Matters Now

ADA Title II is setting the tone for the future of digital accessibility in the U.S. It is already influencing:

• Federal and state procurement
• Healthcare and education technology
• Civic platforms and citizen services
• How software vendors are evaluate