How Aelira Applies Supported PDF Fixes — and Where Review Remains
Follow a PDF from scan to eligible partial changes, saved-file checks and review. Some inputs require manual work or cannot produce a downloadable candidate.
A PDF scan and a delivered remediation result are separate outcomes. A scan can finish while remediation is queued, requires manual work or cannot provide a saved candidate. Aelira Core's beta workflow needs to preserve those distinctions.
Start with findings from the source
The scanner records the checks it implements and their findings. Missing metadata, unsupported content and ambiguous structures are different cases. Scan coverage is not a full evaluation of every PDF/UA or WCAG requirement.
Apply eligible changes
Supported processors can apply partial fixes. The available path depends on the actual structure and input. For example, metadata changes differ from reconstructing reading order or associating table headers. Ambiguous or unsupported cases remain manual or review-required; adding a PDF/UA identifier does not establish PDF/UA conformance.
Follow the saved file
Current releases tie supported measurements to source and output identities and preserve unavailable-result reasons. A job that attempted a change must not present it as a fix delivered in a withheld file. Historical estimated scores are not retroactively verified.
For supported PDFs, the v0.9.11 Review comparison shows source-backed page images and tagged text from original and saved bytes. It has explicit parsing and coverage limits and does not simulate every screen reader. Inspect the v0.9.11 release for the exact boundary.
Review before publishing
Compare the actual saved file with the original. Check content preservation, reading order, heading roles, table relationships and generated descriptions. Run applicable validators and necessary manual or assistive-technology checks. A score describes implemented checks rather than conformance.
Provider and licensing choices
Core supports explicit provider configuration and deterministic scanning without a model. Verify the actual configured provider and outbound data flow; self-hosting the application does not automatically keep inference local. Core is AGPL-3.0 and the CLI is separately MIT-licensed. Consult the public repository for current source, release and deployment instructions.
Try a bounded authorized sample and record delivered outcomes, manual work and failures. We have not published a general per-file processing-time, accuracy or savings benchmark.
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
Aelira Core progress toward v1.0
Aelira Core adds stronger checks on saved LaTeX exports and updates its dependency baseline as work continues toward the v1.0 alpha and later releases.
Aelira Core: testing the installation behind the next release
Our latest Aelira Core work follows the self-hosted installation from a fresh checkout through upgrade and recovery, with clearer evidence for the next release.
Aelira Core v0.9.11: following the result through to the file
Aelira Core v0.9.11 adds source-backed PDF review, corrects remediation status and strengthens tests from document upload through download and rescan.