Universities and the April 2027 deadline
Higher education publishes more documentation than almost any other sector, and much of it is reachable without logging in. That combination is why the ADA Title II web rule lands harder here than anywhere else.
The dates, as they now stand
The Department of Justice extended both compliance dates in April 2026. As things stand:
| Entity | Deadline |
|---|---|
| Public entities serving a population of 50,000 or more | 26 April 2027 |
| Smaller entities and special district governments | 26 April 2028 |
The standard is WCAG 2.1 level AA.
The detail most universities get wrong
A public university's population, for the purposes of this rule, is the population of its state — not its enrolment. A university of four thousand students in a state of six million is treated as a large entity.
In practice that puts almost every US public university, and every community college system, in the earlier group. If you have been planning against 2028 because your campus is small, the date is 26 April 2027.
What is in scope
Web content and mobile apps that a public entity provides or makes available. For a university that reaches considerably further than the marketing site:
- Course material and learning management content
- Student handbooks, policy libraries, academic calendars
- IT and research documentation published from wikis
- Departmental knowledge bases and help centres
- Forms, applications and portals
- Documents linked from any of the above
The exceptions in the rule are narrow and specific — archived content, certain pre-existing documents, some third-party content, individualised password-protected documents. They are worth reading precisely rather than assumed, because most content people hope is exempt is not.
Where the work actually is
The main site is usually the smallest part of the problem. It has an owner, a budget and a redesign cycle. The difficulty is everywhere else: the wiki that eleven departments write into, the research group pages nobody has audited since 2018, the knowledge base the service desk maintains.
These estates share three traits that make them hard. They are large, often thousands of pages. They have many authors and no single owner. And they change weekly, so a one-off audit is out of date before it is filed.
A realistic order of work
- List what is public. Which spaces can be read without logging in? Most institutions have never written this down, and it is the set a complaint will concern.
- Measure all of it, not a sample. Ten pages tell you nothing about whether the problem is concentrated in one department or spread evenly.
- Group by failure, not by page. Four hundred missing alt texts is one instruction repeated, not four hundred separate tasks.
- Route the work to the authors. A central team cannot write alt text for screenshots it has never seen.
- Re-measure monthly and keep the dated reports. What you want on 26 April 2027 is not a perfect estate — nobody will have one — but evidence of a managed process with numbers attached.
On procurement
Universities also buy heavily, and their contracts increasingly carry accessibility conditions. If you sell to one, expect to be asked for a conformance report about your own documentation. Our guide to VPATs and procurement questionnaires covers what a defensible answer looks like.