Maintaining ADA Accessibility Work Beyond the Compliance Date

An accessibility deadline is one planning milestone. New content, revised courses, software changes and student reports create work after that date as well as before it.

Understand the applicable dates and continuing duties

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 technical standard for covered web content and mobile apps is WCAG 2.1 Level AA, subject to the rule's provisions. Existing effective-communication and equal-access duties continue before those dates. A documented programme is useful evidence of activity, but it is not a general safe harbor or proof that a particular barrier is resolved.

Make creation and publication part of the programme

Give authors semantic templates, training and access to specialist support. Check new or changed material before publication, including structure, descriptions, media alternatives and student tasks. Automated checks can find some issues; manual and assistive-technology checks remain necessary for the relevant scope.

Assign ownership for active material and for reported barriers. A course update should trigger appropriate review instead of relying on a scan from a previous semester.

Track repairs and unresolved cases

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.

Retain source files and recorded outcomes. Verify the actual delivered artifact and keep unsupported or refused repairs in the unresolved queue. Test a proposed integration, notification or monitoring feature before relying on it operationally. This article does not promise automatic coverage of all LMS uploads or a complete regulatory documentation package.

Respond to student concerns

Provide a clear reporting route and coordinate timely appropriate access with disability services. Record decisions, owners and follow-up. Resolve the barrier itself rather than treating a higher dashboard score as the response.

If an investigation or agreement applies, follow its actual requirements. Do not assume a universal audit schedule, remedy timetable, retention period or settlement cost from another institution's experience. Cite each public agreement used as an example.

Plan capacity sustainably

Measure incoming content and complete review effort. Fund authorship support, remediation, specialist checks and system operation. Choose programme targets that reflect applicable obligations and actual student access rather than an arbitrary acceptable percentage of inaccessible files.

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.

Regularly assess what the programme has verified, where evidence ends and which barriers remain. The responsible team needs that picture to allocate work and maintain access.

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