What Does ADA Title II Require for Government Websites?

That is the short version. The detail matters, because the scope is wider than most public entities assume and the exceptions are narrower than they look.

Who Does the ADA Title II Web Rule Actually Apply To?

Every state and local government entity in the United States. There is no size threshold that removes the obligation, only one that changes the date.

In practice that means:

• Cities, towns, counties and townships
• School districts, public universities and community colleges
• Public libraries and museums
• Transit authorities and airport authorities
• Courts, police departments and fire departments
• Special districts, including water, sanitation, parks and hospital districts

It applies whether the entity built the website itself, uses a commercial government CMS, or contracted an agency. Responsibility sits with the public entity, not the vendor. That is worth understanding clearly before assuming a platform provider has handled it.

What Is the Compliance Deadline After the 2026 Extension?

On 17 April 2026 the Department of Justice issued an Interim Final Rule moving both compliance dates back by one year.

Two things are worth saying plainly about the extension. First, the underlying rule did not change, only the dates. The standard is still WCAG 2.1 Level AA and the obligation still exists. Second, an extension is not a reprieve. Remediating an established government website is typically six to twelve months of work once auditing, content remediation, template fixes and document conversion are counted. An entity in the 2027 group that starts in early 2027 will not finish in time.

There is also a separate track that catches many organisations by surprise. Entities receiving federal financial assistance from Health and Human Services have their own Section 504 obligations on a different timetable. If your entity receives HHS funding, check that separately rather than assuming the Title II date is the only one that applies to you.

What Technical Standard Do You Have to Meet?

WCAG 2.1 Level AA, published by the World Wide Web Consortium. It is a specific, testable set of success criteria rather than a general principle of accessibility, which is genuinely helpful: conformance is something you can verify rather than argue about.

The criteria group under four principles. Content must be perceivable, operable, understandable and robust. In day to day terms, the requirements that most often fail on government sites are text alternatives for images, sufficient colour contrast, full keyboard operability, visible focus indicators, correct heading structure, labelled form fields, captions on video, and content that still works at 200 percent zoom.

We have written a separate plain English walkthrough of the standard rather than compress it here. See what WCAG 2.1 Level AA means in plain English.

Does the Rule Cover PDFs and Documents?

Yes, and this is where most public entities have the largest problem.

Council minutes, budget documents, planning applications, permit forms, board agendas and public notices are usually PDFs, and usually scanned or exported without an accessibility pass. A scanned PDF is an image. To a screen reader it contains nothing at all.

There is a limited exception for archived content and for electronic documents posted before the compliance date, but it is narrow. Content is only archived if it is kept solely for reference, is clearly identified as archived, is stored in a designated archive area, and has not been changed since it was archived. A budget PDF a resident is expected to read today does not qualify.

For most entities the honest answer is that document remediation is the single largest line item in the project, and it should be scoped first because it takes longest.

What About Third Party Systems and Vendors?

If a public entity delivers a service through a third party platform, that content generally has to meet the standard as well. Online payment portals, permit and licensing systems, job application platforms, meeting streaming services and hosted forms are all in scope when they are used to deliver the entity's services.

The practical step is contractual. Accessibility conformance should be a written requirement in any vendor agreement, with evidence such as a current accessibility conformance report requested before signing. Any vendor managing or contributing to your website should be held to WCAG 2.1 Level AA in the contract itself.

What Happens If You Miss the Deadline?

There is no certifying body, no inspection regime and no compliance certificate. That leads some entities to assume the risk is theoretical. It is not.

Non conformance exposes an entity to Department of Justice enforcement and to private litigation under Title II. In practice, the usual sequence is a complaint from a resident or a disability advocacy organisation, followed by a settlement agreement that mandates remediation on a fixed external timetable, with legal costs on top. Remediation forced by settlement is materially more expensive than the same work planned and phased in advance, because the timetable is no longer yours.

The reputational dimension is real too. Roughly one in four American adults lives with a disability. A public entity whose services are unusable by a significant share of the residents it serves has a service delivery problem before it has a legal one.

What Should a Public Entity Do First?

In this order, because each step tells you what the next one costs:

1. Confirm which deadline applies to you. Population served, and whether you are a special district. This determines whether you have until 2027 or 2028.
2. Run an audit that combines automated and manual testing. Automated tools reliably catch somewhere around a third of issues. Keyboard operability, focus order, meaningful alt text and screen reader logic all require manual testing.
3. Inventory your documents. Count the PDFs that residents are actually expected to use. This number usually determines the project budget more than the website itself does.
4. Fix templates before pages. Most government sites are built from a small number of templates. Correcting heading structure, contrast, focus states and form labelling at template level resolves a large share of individual page failures at once.
5. Publish an accessibility statement and a feedback route. It demonstrates good faith and gives residents a way to report barriers directly rather than through a complaint.
6. Write conformance into procurement. Otherwise you remediate, then buy a new system that reintroduces the same failures.

One judgement call worth making early: whether to remediate the existing site or rebuild it. If the current site is on an ageing template, is difficult for staff to publish to, and would need template level intervention anyway, remediation often costs a meaningful fraction of a rebuild while leaving the underlying problems in place. We work through that comparison honestly on our government website design and ADA compliance page, including the cases where we recommend keeping what you have.