ADA Title II Web Accessibility: Scope, Dates and University Planning

The ADA Title II web rule gives covered public entities a specific technical standard for web content and mobile apps. University planning needs to distinguish that rule from other disability-law obligations and from predictions about enforcement.

Scope and compliance dates

The DOJ's Title II web rule applies to state and local government entities, including public universities. The April 2026 Interim Final Rule extended compliance dates to April 26, 2027 for public entities with populations of 50,000 or more, and April 26, 2028 for smaller entities and special district governments. These are population cohorts under the rule, not student-enrollment thresholds. Federal funding alone does not make a private university a Title II public entity; other disability laws may apply.

The rule specifies WCAG 2.1 Level AA, subject to its provisions and exceptions. Existing duties for effective communication, reasonable modifications and equal opportunity remain. The additional time for the technical standard does not remove those duties.

Map covered content carefully

Identify the web content and mobile apps the institution provides or makes available, including arrangements with others. Evaluate active course documents, LMS tasks and public services. Apply exceptions only when their actual conditions are satisfied. An archive label or a password-protected course is not, by itself, a general exemption.

Responsibility for a barrier depends on the applicable facts and law. Do not assume that every reported barrier leads to federal funding loss, a particular settlement amount or a predetermined enforcement timetable.

Use primary enforcement sources

DOJ and the Department of Education Office for Civil Rights have distinct roles and authorities. When using a resolution agreement as a planning example, identify the institution, source agreement, findings and specific remedies. An anonymous anecdote or an invented complaint count cannot support an enforcement trend.

Policies, training, ownership, prompt responses to student concerns and retained remediation evidence can support a programme. They do not create a general good-faith safe harbor or prove conformance.

Build a measured rollout

An illustrative inventory could include 15,000 PDFs, 8,000 slide decks, 3,000 videos and 2,500 LaTeX files. These are hypothetical planning inputs. Sample the different formats and complexities, measure total remediation and review work, and keep unresolved cases visible before extrapolating to the inventory.

Aelira Core v0.9.11 is beta. Supported workflows can detect issues, suggest changes and apply eligible partial fixes. Other findings need manual work, and some inputs may not produce a downloadable remediated artifact. Review the actual saved file, its recorded fixes and its unresolved findings. An automated score does not establish WCAG conformance.

Inspect the actual saved artifacts and perform the necessary manual and assistive-technology checks. Assign a responsible owner and route unsupported material to specialists or appropriate alternative access.

Maintain evidence and capacity

Record file versions, tools, findings, reviewer decisions and verification results. Agree retention and reporting with institutional policy and applicable requirements. Determine staffing and budgets from measured workloads and current quotes rather than a universal cost or completion rate.

The self-hosted software is free and open source. Paid services cover support or managed hosting. Operational allowances, provider charges and service commitments depend on the chosen deployment and written terms; free software does not mean unlimited processing or zero operating cost. Use current US pricing or current Australian pricing, and obtain a written pilot quote covering continuation terms.

Further reading

These links provide additional context; each source should be assessed for its own scope.

The April 2026 ADA Deadline Was Extended — What Universities Should Do Now