From Accessibility Scan Findings to Verified Repairs

A scan can identify accessibility findings, but a report alone does not repair the content. Institutions need a route from a finding to a responsible owner, a supported change and a verified accessible result.

Use scanning for what it can establish

Automated checks help locate some missing attributes, structural issues and contrast failures. The findings still need interpretation and prioritization. A scanner cannot determine every educational purpose, verify all descriptions or certify an entire course from a score.

Scanning tools can be valuable within a wider programme. Vendors and products vary in their supported repair features, integrations and verification. Compare current documented capabilities rather than assigning a universal limitation or advantage to a category.

Close the gap between a report and a repair

For each issue, determine the editable source, owner and appropriate corrective action. Some work belongs in the authoring tool; some needs a document specialist; some can use an assisted workflow. Generated changes require checks for correctness and preservation of the original content.

Faculty subject expertise helps establish meaning. Accessibility expertise helps establish usable structure and interaction. Approval is useful only when the reviewer has suitable context and checks for the task; a one-click interface does not replace that work.

Evaluate delivered outputs

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.

Keep detection, suggestion, application and verified output as distinct recorded outcomes. Inspect the saved file for reading sequence, headings, tables, descriptions and mathematical content. Use the required manual and assistive-technology checks. If no artifact is delivered, retain the findings as unresolved.

Compare complete workflow costs

An illustrative institution might have 15,000 PDFs. That inventory is a planning input, not a customer result. Sample the formats and complexities, measure accepted-output yield and include intake, correction, review, infrastructure and rework in the cost comparison.

There is no published Aelira benchmark establishing that automation does 80% of the work, that review needs no accessibility expertise, or that assisted remediation is always several times cheaper. Those are questions for a representative evaluation.

Questions for a vendor evaluation

• Which formats and issue types are supported for detection, suggestions and saved repairs?
• What happens to unsupported inputs and findings without a verified outcome?
• Can reviewers inspect the original and actual saved candidate and retain decisions?
• Which integration and monitoring features work in the institution's actual environment?
• What data flows to external providers, and what are the operating allowances and costs?

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.

Judge the workflow by verified outcomes and unresolved barriers, alongside its measured cost and capacity.