ADA Title II Compliance for Universities: Deadlines, Scope and a Plan

ADA Title II Compliance for Universities: Deadlines, Scope and a Plan

Last updated: November 10, 2026

Public universities must meet WCAG 2.1 Level AA for their web content and mobile apps under ADA Title II. The compliance date is April 26, 2027 for entities serving a population of 50,000 or more, and April 26, 2028 for smaller entities and special district governments. The U.S. Department of Justice moved both dates by one year in an interim final rule published April 20, 2026. The standard did not change.

Older pages still list April 24, 2026. That date is no longer the deadline. This guide covers who must comply, what the rule requires, what is exempt, and how to use the time you have.

What are the ADA Title II deadlines for universities?

• Population of 50,000 or more: April 26, 2027 (moved from April 24, 2026).
• Population under 50,000, and special district governments: April 26, 2028 (moved from April 26, 2027).

The population count belongs to the state or local government the institution is part of. It is not the number of students enrolled. A public university that is part of a state system usually follows the state's population. Confirm your category with counsel before you plan around the later date.

For the full timeline and the reasons DOJ gave, read ADA Title II deadline: what we know.

Does ADA Title II apply to your university?

Title II covers state and local government entities. That includes public universities, community colleges and public K-12 systems. Private universities fall under Title III of the ADA and the Section 504 rules for funding recipients, not this rule. Private schools still face accessibility lawsuits, so many follow the same standard.

Read how WebAbility supports accessibility for education, then test a campus page with the free ADA Title II compliance checker.

What does the rule require?

The standard is WCAG 2.1 Level AA for web content and mobile apps that the institution provides or makes available through a contract or other arrangement. The rule is part of 28 CFR Part 35. It builds on the ADA duty to give equal access to programs and services.

On a campus, this reaches more than the main website:

• Admissions, financial aid and course catalog pages
• Student portals and other login-protected systems
• Learning platforms such as Canvas, Blackboard and Moodle, including course content
• Videos (captions) and audio (transcripts)
• Mobile apps
• Documents that students and staff use, such as PDFs, Word files and slides

A vendor-run platform does not remove the duty. If the university offers it to students, the university is responsible for it.

What content is exempt?

The rule lists five narrow exceptions:

1. Archived web content that is kept only for reference, labeled as archived and not changed after it was archived.
2. Pre-existing conventional electronic documents (such as PDFs) that are not currently used to apply for, access or take part in a service.
3. Content posted by a third party that the university does not control through a contract, license or other arrangement.
4. Individualized, password-protected documents about a specific person or account.
5. Pre-existing social media posts.

Most active course and admissions content does not qualify. A PDF a student needs this term is not archived. Any exempt item that you update loses the exemption.

Where do universities fail most often?

Four gaps appear again and again in campus audits:

• Documents. Syllabi, forms and financial aid guides sit in PDFs with no tags or reading order. See what makes a PDF accessible.
• Course platforms. Instructors upload content the central team never reviews.
• Forms and portals. Missing labels and keyboard traps block students at registration.
• One-time fixes. A site passes in spring and fails again after new content goes live.

How should a university use the extra year?

The extension moves the date. It does not remove the duty to give students equal access today, and it does not stop complaints or lawsuits that rely on the ADA itself. Treat the time as planning time.

Days 1 to 30: find out where you stand

• List every web property, app and platform the university provides.
• Run an accessibility audit on the highest-traffic pages and the registration, payment and course-access paths.
• Count the documents that are in active use.

Days 31 to 60: fix the paths students use

• Fix navigation, forms and login first.
• Add captions to lecture video that is still in use.
• Ask each vendor for its current conformance report (VPAT or ACR) and test its claims.

Days 61 to 90: make it routine

• Add an accessibility check to the publishing steps for web pages and documents.
• Set up monitoring so new content is tested after it goes live.
• Name an owner and a date for each open item.

Higher education has extra needs such as course content and web governance. Our guide to higher education website accessibility goes deeper on those.

Frequently asked questions

Is the April 24, 2026 deadline still in force?

No. DOJ's interim final rule of April 20, 2026 moved it to April 26, 2027 for entities serving 50,000 or more people.

Which WCAG version do universities need to meet?

WCAG 2.1 Level AA. The rule names that version.

Do private universities have to follow the Title II rule?

No. Title II covers public entities. Private universities fall under Title III of the ADA and, if they take federal funds, Section 504.

Does the rule cover login-protected content?

Yes. Student portals and course platforms are covered. Only individualized password-protected documents about one person or account are exempt.

Do we need to fix old PDFs?

Fix any PDF that students or staff use to apply for, access or take part in a service. Truly archived, unchanged files are exempt. When in doubt, fix it.

Check your campus today

The standard is WCAG 2.1 AA, and the work takes longer than most plans expect. Start with the free ADA Title II checker on one high-traffic page, then book a full audit.