Evaluate Aelira with the evidence in view.

What you can inspect

These are first-party implementation and test records. We have not published an independent accessibility conformance assessment or named institutional pilot outcomes on this page. Synthetic fixture results do not establish usability for every document, course or assistive-technology combination.

Connector readiness

Based on the public core status reference. Connection, scanning, remediation, approval and writeback are separate operations.

Establish evidence for your institution

Agree the acceptance criteria before a pilot. Use authorized, representative files, including cases expected to need manual work, and retain the original alongside each saved candidate.

1. Record the version, configuration, file formats, corpus size and document complexity. Define which formats and connector operations are in scope.
2. Report delivered fixes, unresolved findings, refused or unavailable outputs, and failures separately. Include the denominator; a successful example cannot establish a general success rate.
3. Compare source and saved-file meaning, layout, mathematics, tables and generated descriptions. Have an accessibility specialist review the applicable assistive-technology journeys.
4. Measure total staff time, including review, corrections and failures, against an agreed baseline. Publish savings only with the method and limits of that measurement.
5. Test permissions, tenant boundaries, provider egress, retention, upgrades, recovery and authorized writeback. Obtain permission before publishing an institution's name or findings.

Regional planning

Australian education accessibility obligations arise under the DDA 1992 and DSE 2005. There is no single federal website deadline equivalent to the US Title II dates. Check the applicable obligations and procurement standards with your institution. Read the Australian Government guidance.