What's in a Name? The Six Words Behind Aelira

Aelira is an acronym: Accessibility, Equity, Learning, Inclusion, Remediation and Automation. These six words describe the purpose of the project and the principles we use to make design decisions.

Accessibility

Students encounter websites, documents, presentations, spreadsheets and media. A barrier in any of those formats can interrupt a course task. Our aim is to help institutions identify barriers and evaluate supported changes in the actual material, while making untested areas visible.

Equity

A student should be able to obtain the information and participate in the activity a course requires. That means considering access when material is created, responding to reported barriers and coordinating appropriate support. A generated file or scanner score cannot tell the whole story of that student's experience.

Learning

Higher education brings complex figures, mathematics, tables and teaching context. The author or subject specialist can explain what a diagram is meant to teach. Accessibility expertise helps determine how a student reaches that information. Both kinds of context belong in a review workflow.

Inclusion

We design around tasks: finding a heading, following an explanation, understanding a chart or operating an interactive element. Meeting a technical criterion contributes to access, while individual needs and complete journeys also deserve attention. We do not treat an automated pass as proof that those journeys are usable.

Remediation

Detection, proposing a change, applying it and accepting the saved result are separate outcomes. 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.

Automation

Automation can assist with repeatable work when its inputs and checks support the operation. People still assess educational meaning, structural correctness and unresolved cases. We measure usefulness through reviewed outputs and total effort, including failures and rework, rather than promising one automation percentage for every institution.

Connections also have separate stages: authorization, retrieval, scanning, review and permitted writeback. Canvas has release-specific integration evidence; Brightspace remains beta/developer readiness, and Blackboard and Moodle are experimental. Evaluate Google and Microsoft routes against the installed release and permissions. No connection label establishes every student journey.

Six words, an ongoing commitment

These principles guide a product still under development. We have conducted extensive internal testing on an NVIDIA DGX Spark and a private university pilot. No named reference or publishable pilot outcome is offered here; internal evaluation is not a representative performance benchmark. Two research papers are in preparation and are not published evidence.

The practical next step is an authorized sample evaluation with explicit acceptance checks. Ask what was delivered, what remains open and whether the saved material preserves the teaching purpose.