Skip to main content
The Complete Guide · Updated 2026

ADA Title II Website Compliance for Government

Federal law now requires every U.S. state and local government website to meet WCAG 2.1 Level AA. This is the definitive guide to what the rule requires, who it covers, the deadlines, and how to get compliant.

Written by My Media Matters — an agency that builds every website to WCAG 2.1 AA by default and audits, remediates, and rebuilds government websites nationwide.

The deadlines at a glance

Entity sizeCompliance deadlineWho this is
Population 50,000+April 26, 2027Larger cities & counties
Population under 50,000April 26, 2028Most U.S. towns & small cities
Special district governmentsApril 26, 2028Any size — water, fire, school, utility, hospital districts

Standard required: WCAG 2.1 Level AA, adopted by the U.S. Department of Justice under ADA Title II.

What the Rule Covers

It’s more than your web pages.

The rule reaches everything a government publishes online — including the documents residents actually use. Inaccessible PDFs are the single most common failure.

  • Public websites and every page on them
  • Web applications and online services (payments, permits, forms)
  • Mobile apps the entity offers
  • PDFs & documents — agendas, minutes, budgets, notices, forms
  • Video and audio (captions, transcripts)
  • Content posted by third parties on the entity's behalf
Why It Matters

Legal exposure

DOJ investigations and private lawsuits under the ADA for non-compliant entities.

Funding risk

Non-compliance can put federal funding at risk for state and local governments.

Access to services

An inaccessible site shuts residents with disabilities out of public information and services.

How to Get Compliant

Four steps to WCAG 2.1 AA.

1

Audit against WCAG 2.1 AA

Automated scan plus manual testing — keyboard navigation, screen-reader review, and PDF/document checks — producing a prioritized, plain-English report.

2

Remediate or rebuild

Fix the existing site or build a compliant one from the ground up, including accessible documents. Accessibility engineered in, not bolted on.

3

Publish an accessibility statement

A public conformance statement and documentation — the paper trail that demonstrates good-faith compliance.

4

Monitor continuously

Every new agenda, notice, and PDF has to stay accessible. Ongoing monitoring keeps you compliant as you publish.

Everything, Answered

ADA Title II website compliance, answered.

Does ADA Title II apply to government websites?
Yes. Title II of the Americans with Disabilities Act applies to all state and local government entities — states, counties, cities, towns, villages, special districts, public school districts, public colleges, libraries, and transit authorities. In April 2024 the U.S. Department of Justice published a final rule making explicit that Title II covers these entities' websites and mobile apps, and setting a specific technical standard and compliance deadlines.
What accessibility standard must a government website meet?
The DOJ rule adopts WCAG 2.1 Level AA (Web Content Accessibility Guidelines) as the technical standard. WCAG 2.1 AA covers requirements like sufficient color contrast, keyboard operability, text alternatives for images, captions for video, clear labels and headings, and content that works with screen readers. It applies to web pages, web applications, mobile apps, and the documents a government publishes online.
When is the ADA Title II website compliance deadline?
The deadline depends on population. Public entities with a total population of 50,000 or more must comply by April 26, 2027. Public entities with a population under 50,000, along with special district governments of any size, must comply by April 26, 2028. (In April 2026 the DOJ extended both original deadlines by one year; these are the current dates.)
Who has to comply with the ADA Title II web rule?
Every state and local government entity: state agencies, counties, cities and towns, villages, townships, special districts (such as rural water, fire protection, hospital, and utility districts), public school districts, public universities and community colleges, public libraries, and public transit authorities. It also reaches the online content those entities post through third parties on their behalf.
Does the rule cover PDFs and documents, or just web pages?
It covers both. The rule applies to the content a government publishes online, which includes PDFs and other documents — agendas, meeting minutes, budgets, permit and license forms, public notices, and maps. Inaccessible PDFs are one of the most common and most overlooked compliance failures for government websites.
What happens if a government website is not compliant by the deadline?
Non-compliant entities can face U.S. Department of Justice investigations and enforcement, complaints filed by members of the public, and private lawsuits under the ADA. Non-compliance can also put federal funding at risk. Beyond the legal exposure, an inaccessible website excludes residents with disabilities from public information and services they are legally entitled to access.
Are there any exceptions to the ADA Title II web rule?
The rule includes limited exceptions, such as certain archived web content, pre-existing conventional electronic documents (unless used to apply for or access a service), content posted by third parties where the entity does not control it, individualized password-protected documents, and pre-existing social media posts. These exceptions are narrow — the safest assumption is that your public-facing website and the documents residents use must meet WCAG 2.1 AA.
How is ADA Title II different from Section 508?
Section 508 applies to federal agencies and their technology; ADA Title II applies to state and local governments. Both point to WCAG as the practical standard (Section 508 references WCAG 2.0 AA; the Title II rule adopts WCAG 2.1 AA). If you run a city, county, or special district, ADA Title II — and WCAG 2.1 AA — is the standard that governs your website.
How do we know if our government website is already compliant?
Start with an accessibility audit against WCAG 2.1 AA. Automated scans catch a portion of issues (contrast, missing alt text, form labels), but full conformance requires manual testing — keyboard-only navigation, screen-reader review, and checking that PDFs and embedded third-party tools are accessible. A proper audit produces a plain-English report of what is failing, how serious each issue is, and what remediation requires.
How does a city or county become ADA compliant?
Four steps: (1) audit the current site and documents against WCAG 2.1 AA; (2) remediate the existing site or rebuild it to the standard, including accessible PDFs; (3) publish a public accessibility statement documenting conformance; and (4) monitor continuously, since every new agenda, notice, and document must stay accessible. My Media Matters builds every site to WCAG 2.1 AA by default and can audit, remediate, or rebuild for public entities.

This guide is general information about web-accessibility requirements, not legal advice. For how the ADA applies to your specific entity, consult your attorney.

Find out where your government website stands.

My Media Matters runs free WCAG 2.1 AA accessibility audits for cities, counties, special districts, and chambers — a plain-English report of what’s failing and what it takes to fix it.

Related: WCAG 2.1 AA checklist · Free ADA scan · ADA-compliant government websites · Our accessibility statement