The Department of Justice published a final rule under Title II of the Americans with Disabilities Act that makes WCAG 2.1 Level AA the enforceable accessibility standard for the web content and mobile apps of state and local governments. Public entities serving populations of 50,000 or more must comply by April 24, 2026. Smaller entities and special district governments have until April 26, 2027. Public colleges and universities are covered, and most fall under the 2026 date.
Who is covered
Title II applies to state and local government entities and their instrumentalities. That includes city and county governments, public school districts, transit agencies, libraries, and public colleges and universities. Because most public institutions are instrumentalities of states with populations well over 50,000, the earlier April 2026 deadline generally applies to them. Private universities are not covered by Title II, though they carry their own obligations under Title III and face the same practical expectations from students.
What the rule requires
Web content and mobile apps that a covered entity provides or makes available must conform to WCAG 2.1 Level AA. That includes the main website, departmental sites, online forms and services, and password-protected content such as course materials, with a small set of defined exceptions. The notable exceptions cover archived web content, preexisting electronic documents that are not currently used to apply for or participate in services, and certain third-party content the entity does not control through a contractual relationship. The exceptions are narrower than most teams assume, so treat them as edge cases rather than a strategy.
Where public sites typically fail
- PDF libraries: forms, agendas, syllabi, and reports that were never remediated.
- Forms without proper labels, error handling, or keyboard support.
- Video without accurate captions and audio description where needed.
- Color contrast failures baked into brand palettes and data visualizations.
- Third-party widgets: calendars, payment portals, maps, and chat tools procured without accessibility requirements.
- Documents and pages published daily by hundreds of editors with no training or monitoring.
A pragmatic 6-step compliance plan
- 1. Audit against WCAG 2.1 AA now. Automated scanning plus expert manual review of your highest-traffic templates and critical service journeys.
- 2. Fix the system, not individual pages. Remediating templates and components corrects thousands of pages at once and keeps new content compliant by default.
- 3. Triage your documents. Inventory PDFs, archive what qualifies for the exception, remediate what people actually use, and move recurring documents to accessible HTML.
- 4. Caption and describe media. Set a standard for new media and work through the backlog by traffic priority.
- 5. Put accessibility in procurement. Every new tool, widget, and platform contract should require WCAG 2.1 AA conformance and evidence.
- 6. Train editors and monitor continuously. Compliance is an operating practice. Monitoring plus editor training is what keeps you compliant in month thirteen.
What this looks like when it works
When the City of Chandler, one of America’s fastest-growing cities, rebuilt its civic platform with KWALL, accessibility was engineered in from the start: a multilingual, fully ADA Title II compliant platform serving 290,000 residents. The same approach applies on campus. Accessibility lives in the design system, the editorial workflow, and the procurement process, not in a yearly audit PDF.
Frequently asked questions
What is the ADA Title II website compliance deadline?
April 24, 2026 for public entities serving populations of 50,000 or more, and April 26, 2027 for smaller entities and special district governments. Most public colleges and universities fall under the April 2026 date.
What accessibility standard does the ADA Title II rule require?
WCAG 2.1 Level AA, applied to web content and mobile applications that a state or local government entity provides or makes available, including most password-protected course content for public institutions.
Does the rule apply to private universities?
No. Title II covers public entities. Private institutions have obligations under ADA Title III, and many adopt WCAG 2.1 AA anyway because it is the de facto standard courts and students expect.
Are PDFs covered by the Title II rule?
Yes. Documents are covered unless they qualify for narrow exceptions such as archived content or preexisting documents not currently used to access services. Active forms, schedules, and informational PDFs need to be accessible or replaced with accessible HTML.
What happens if we miss the deadline?
You face complaint-driven DOJ enforcement and private lawsuit exposure. Demonstrable progress, a remediation plan, and fixed high-traffic journeys materially reduce risk compared to doing nothing.
KWALL runs accessibility as an ongoing program: audit, remediation, monitoring, and editor training. See our Accessibility and Compliance program, our work for government and higher education, or get a Title II readiness assessment.
