Can AI-Generated Accessibility Fixes Be Trusted?
Evaluate AI-assisted accessibility fixes against the original content and saved output. Learn what to review, what a scanner can establish, and how to retain evidence.
AI-assisted accessibility changes need evidence from the actual output. A detailed description, a plausible tag tree, or a higher scanner score can still conceal a changed equation, an incorrect reading order, or a misleading chart description.
What can be trusted?
Trust a recorded result within the checks that established it. A tool may detect a missing language value or a low-contrast color pair reliably, while deciding the intended meaning of a figure requires context. Detection, applying a change, saving a usable file, and establishing accessibility are separate tasks.
Aelira Core is beta. Supported processors can apply eligible changes and return saved candidates with recorded outcomes. Some inputs require manual work; unsupported or ambiguous cases may not produce a downloadable remediated file. We have not published a general accuracy percentage or a representative time-saving benchmark for these workflows.
Review structure as well as descriptions
- Reading order: follow the saved content in sequence, including columns, sidebars, footnotes and captions.
- Headings: confirm that semantic levels reflect the intended hierarchy. Visual size alone does not establish a heading's role.
- Tables: check the associations between headers and data, especially merged cells and multiple header levels.
- Mathematics: compare symbols, operators, grouping and meaning against the source, and test the actual exported representation.
- Contrast: verify the resulting appearance and whether a color change removes information or obscures another element.
Use an accessibility specialist for checks outside your expertise. Passing automated checks does not establish conformance for every applicable criterion or assistive-technology journey.
Check image descriptions against the teaching purpose
An illustrative biology diagram might receive the description “diagram with arrows and labels.” A useful description must convey the relevant relationships shown in the actual image. A reviewer cannot safely add a process name, value or trend that the source does not establish.
Decide whether an image is informative or decorative in its particular context. A photograph used to explain an architectural feature needs different treatment from the same photograph used as decoration. Generated text must be checked for unsupported details as well as omissions.
A practical acceptance workflow
- Retain the original and record the processor version and configuration.
- Read the recorded fixes, unresolved findings and unavailable-output status.
- Open the actual saved candidate. Compare content and structure with the original.
- Run applicable automated checks and the necessary manual or assistive-technology checks.
- Correct, reject or escalate uncertain results. Publish only after the responsible reviewer accepts the output.
A rescan provides evidence about the scanner's checks. It cannot determine whether a description conveys the right teaching point or whether every student can use the resulting material.
Measure the benefit rather than assuming it
For a pilot, use representative authorized files and record processing, review, correction and manual-remediation time. Include failures and refused outputs in the denominator. Compare that total with a documented baseline before publishing an accuracy or savings claim.
Inspect Aelira's current scope and evidence, or try a supported document in the demo.
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
When Human Review Matters in Accessibility Remediation
Human review covers saved-file structure as well as educational meaning. Build a review workflow around content risk, supported formats and unresolved findings.
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.