Maintaining Accessibility at Australian Universities After Initial Remediation
Maintain an ongoing DDA and DSE program with ownership, student feedback, reviewed outputs and local evidence. No complaint-prevention or legal-outcome guarantee applies.
An initial remediation project does not end an institution's accessibility work. New material, updated systems and individual student needs require continuing attention. The Disability Standards for Education 2005 operate within Australia's DDA framework and address education on the same basis, consultation and reasonable adjustments.
Establish an ongoing workflow
Assign owners for source creation, remediation, specialist review and student support. Provide an accessible reporting route and coordinate timely interim access with disability services where required. Record unresolved barriers and follow-up dates.
Review changed material
Use accessible templates and checks when content is created. Reassess changed documents, course pages, media and assessments. Automated findings can support triage, but meaningful descriptions, structure and actual student tasks require appropriate manual and assistive-technology checks.
Keep useful records
Retain policy, responsibilities, training, source/output identities, findings, changes, reviews and remaining work under institutional retention and privacy controls. Records can support a response to an inquiry; they do not guarantee an AHRC outcome or prevent every complaint.
Set local measures and resources
Measure accepted outputs, unresolved work, response time and recurrence. A percentage of automated checks passed is not a percentage of legal compliance. Agree staffing and budgets from the inventory, observed workload and actual quotes; there is no verified universal annual program budget or average complaint cost in this article.
Unjustifiable hardship and reasonable adjustment require the applicable legal assessment. The existence of an AI tool does not eliminate a defense or establish what is affordable in every case.
Aelira Core is beta software. Supported workflows can apply eligible partial fixes and record outcomes, but some inputs need manual work or cannot produce a downloadable remediated file. Review the actual saved output, unresolved findings and content preservation before publication. Automated scores describe implemented checks rather than accessibility conformance. Inspect the public source and release documentation and evaluate a representative authorized sample before planning a rollout.
Australian obligations should not be assigned the US Title II compliance dates. Refer to current AU pricing and a written service scope if evaluating Aelira, and involve the institution's legal and accessibility teams in the program.
Aelira Team
•Accessibility EngineersThe Aelira team is building beta accessibility tools for higher education. Institutions can evaluate selected checks and partial fixes on their own files, with human review required before publication.
Related Articles
DDA 1992 and DSE 2005: Accessibility Planning for Australian Universities
Distinguish Australian disability-law obligations from technical standards and US deadlines. Plan consultation, accessible teaching material, verification and unresolved work.
Aelira Core v0.9.12: publishing the security record with the release
Aelira Core v0.9.12 fixes a LaTeX file-access vulnerability, publishes three security advisories, discloses every unfixed image advisory and adds reviewed PDF working files.
I applied for GitHub's security fund. Then CodeQL found 42 alerts.
We applied for GitHub's security fund, then CodeQL raised 42 alerts. Here's what we changed, deployed and still need to review.