On 20 April 2026, four days before the first deadline was due to bite, the Department of Justice issued an interim final rule extending the Title II web accessibility compliance dates by one year.
- Public entities with a total population of 50,000 or more: 26 April 2027.
- Public entities under 50,000, and special district governments: 26 April 2028.
- The technical standard is unchanged: WCAG 2.1 Level AA.
- The scope of covered content is unchanged.
The Department stated that it fully anticipates implementing the regulation at the new dates.Interim final rule, 20 April 2026
Which date applies to you
Population is calculated at the level of the jurisdiction the entity belongs to, not by enrollment. The Department’s January 2025 guidance addresses this directly, using a state university with 40,000 students in a state of six million people, and stating that the number of students attending does not determine the university’s population for the rule. The relevant figure is the state’s Census population.DOJ, First Steps, January 2025
The practical effect is that effectively every public university sits in the 2027 group, because no state has a population under 50,000. Community colleges and school districts take the population of the city or county they belong to, and special district governments have their own date in 2028. If you assumed enrollment put you in the later group, that assumption is wrong and the difference is a year.
What has not changed
Two things, and they are the two that matter.
The underlying obligation to provide accessible programs and services has been in force since 1990 and did not pause. An institution with an inaccessible course platform today is not compliant today; it simply has a different date attached to one specific rule.
And the standard is still WCAG 2.1 AA. Remediation work already mapped to it still counts. If an audit is under way, finish it.
The extension moved a deadline. It did not move the obligation.
What the extra year is actually for
For institutions that had started, it is time to validate fixes, document decisions, and work through a remediation queue properly rather than at speed.
For institutions that had not started, it is the difference between building a program and staging a panic. Twelve months is enough to audit, prioritize by user impact, fix, and put procurement controls in place so the problem stops being recreated. It is not enough to do all of that starting in month ten.
The part most institutions are still missing
Third-party content. Learning platforms, library databases, video hosting, forms, payment portals, and everything a department bought without telling anyone.
An institution is responsible for the accessibility of the services it provides, including through third parties. That makes this a procurement problem as much as a web problem, and procurement is where most institutions have no accessibility control at all.
- Does every contract require conformance, and name the standard?
- Do you request accessibility conformance documentation before purchase, and read it?
- Who signs off when a department buys a platform independently?
- What happens at renewal when a vendor has not remediated?
If you also take HHS funding, you have a second date
Health and Human Services moved in parallel. On 7 May 2026, its Office for Civil Rights issued an interim final rule extending the Section 504 web and mobile accessibility dates by one year.HHS OCR, 7 May 2026
- Recipients with 15 or more employees: 11 May 2027.
- Recipients with fewer than 15 employees: 10 May 2028.
- Same standard, WCAG 2.1 Level AA. Same scope.91 FR, doc 2026-09266
Note the threshold. The Title II date turns on the population of your jurisdiction; the Section 504 date turns on employee count at the recipient. They are different tests producing different dates, and an institution subject to both is subject to both.
For a university with a medical center, a dental clinic, a counseling service, or any program drawing HHS funds, that means two deadlines about two weeks apart in the spring of 2027, and a real question about which entity each attaches to. Section 504 reaches most hospitals, physician practices, health centers, long-term care facilities, research institutions, and medical schools.
Resolve on paper now which of your entities sits under which rule. It is a one-page exercise in August and an emergency in April.
What the work actually consists of
"Twelve months is enough" is worth grounding in what has to be done.
WCAG 2.1 sets 50 success criteria across Levels A and AA, and conformance means meeting every one of them on every covered page, document, and screen. Not a majority. Every one.
The rule does carve out narrow exceptions, and knowing them changes the size of the job considerably.
- Archived web content, kept only for reference and not altered since being archived.
- Preexisting conventional electronic documents, unless still used to apply for or participate in a program.
- Content posted by a third party, where the third party is not acting for the entity.
- Individualized password-protected documents, such as a single student’s billing statement.
- Preexisting social media posts.
Read those carefully before relying on them. The document exception does not cover anything a person still needs in order to apply, enroll, pay, or participate, which is most of what an institution actually publishes.
What remains is typically larger than institutions expect: the main site and every subdomain, the student portal, the learning platform and the course materials inside it, forms, payment systems, library databases, mobile apps, and video. A single department’s untagged PDFs can be thousands of documents on their own.
Against that, twelve months is a working timetable if you start now and a fiction if you start in month ten.
A defensible twelve months
Months one and two: inventory
Find out what you actually have. Every domain, platform, and application, with an owner named against each. Most institutions discover systems nobody in IT knew were live.
Months two to four: audit and triage
Automated scanning finds a portion of the issues; manual and assistive technology testing finds the rest. Prioritize by user impact and traffic, not by ease of fixing.
Months three to ten: remediate, and stop the inflow
Fix in priority order while putting authoring standards and procurement controls in place, or you will remediate into a queue that keeps refilling behind you.
Months ten to twelve: validate and document
Retest what was fixed. Record what was done, what remains, and why. That record is what demonstrates good faith if a complaint arrives before the work is complete.
The last point deserves emphasis. Nothing in either extension stops a person filing a complaint or a suit today. The nondiscrimination duty has been in force since 1990 under the ADA and since 1973 under Section 504, and the extension changed a technical deadline, not the obligation.
An institution that can show an inventory, an audit, a prioritized plan, and evidence of progress is in a materially different position from one that can show nothing, whatever the date says.
— Albert Roberson, Fractional Coordinator