Product readiness reviewed 5 October 2026
Evaluate Aelira with the evidence in view.
Current published release: v0.9.11. Product maturity: beta.
Aelira Core is beta software. Supported workflows can apply partial fixes and produce review artifacts. Human review remains necessary; automated scores do not establish accessibility conformance. Some documents require manual work and cannot produce a downloadable remediated file. Review the actual saved output before publishing it.
GitHub's release flag identifies a published tag; it does not establish institutional acceptance. Changes on the main branch may be newer than the published release. Pin the source or image version when evaluating results.
What you can inspect
Current scope and maturity
Beta status, supported formats, deployment choices and connector limitations.
Released workflow evidence
The v0.9.11 maintenance release describes synthetic API, queue, worker, download and rescan checks, with their limits.
Format-by-format boundaries
What each processor can inspect or change, dependencies, refusal cases and review requirements.
Reproducible acceptance matrix
Maintainer test coverage and how to evaluate the applicable workflow.
Public CI and open issues
Inspect the run and source commit you are evaluating. Passing CI is evidence for those checks, rather than a general conformance assessment.
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.
| Connector | Status | Evidence boundary |
|---|---|---|
| Canvas | Integration verified | The maintainer reports production integration testing. Validate your own institution's permissions, policy, and full user journey before rollout. |
| Brightspace | Beta | Tested against a developer instance; not recently re-verified. A deployment-specific acceptance check is required. |
| Blackboard | Experimental | Implemented; a complete institutional user journey has not been verified. |
| Moodle | Experimental | Implemented; a complete institutional user journey has not been verified. |
| Google Workspace | Evaluate before rollout | Connector code is available. The public LMS readiness table does not establish current acceptance evidence for Google Workspace. |
| Microsoft 365 | Evaluate before rollout | Connector code is available. The public LMS readiness table does not establish current acceptance evidence for Microsoft 365. |
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.
- Record the version, configuration, file formats, corpus size and document complexity. Define which formats and connector operations are in scope.
- Report delivered fixes, unresolved findings, refused or unavailable outputs, and failures separately. Include the denominator; a successful example cannot establish a general success rate.
- Compare source and saved-file meaning, layout, mathematics, tables and generated descriptions. Have an accessibility specialist review the applicable assistive-technology journeys.
- Measure total staff time, including review, corrections and failures, against an agreed baseline. Publish savings only with the method and limits of that measurement.
- Test permissions, tenant boundaries, provider egress, retention, upgrades, recovery and authorized writeback. Obtain permission before publishing an institution's name or findings.
Regional planning
DOJ lists April 26, 2027 for state or local governments with a population of at least 50,000, and April 26, 2028 for smaller public entities and special district governments. Student enrolment does not determine the cohort. Check applicability, exceptions and continuing obligations with your institution's accessibility and legal teams. Read the DOJ guidance.