From PDF Findings to Reviewed Remediation

A scanner identifies certain accessibility problems. Remediation changes content or structure to address them. Validation and review then assess the saved result. Products can combine these functions, and their scope should be tested rather than inferred from a category label.

Detection has limits

Software can check for a missing title or language value and inspect supported structures. It cannot establish every intended relationship, image purpose or user journey. Presence of an alternative-text attribute is different from an accurate explanation of a chart. Detection is not a solved universal problem.

Changes need source context

Reading-order correction must retain the intended sequence. Table remediation must associate the correct headers with data. Headings must reflect the document's hierarchy, and generated descriptions must preserve meaning. A seemingly mechanical change can still be wrong.

Manual editors, outsourced services and automated tools can all assist. Their capacity, costs and error rates vary with the content and acceptance criteria. There is no evidence here for a universal claim that competitors only report issues or that manual work cannot scale.

Check the actual saved output

Retain the source and exact output identities. Inspect recorded changes and unresolved findings, compare content, run the applicable validator and perform necessary manual and assistive-technology checks. The Matterhorn Protocol includes conditions requiring human judgment; passing an automated subset is not a blanket conformance verdict.

Evaluate on representative files

Ask which inputs are supported, when output is withheld, what checks are untested, how review decisions are recorded, and whether source and output can be inspected. Measure accepted-output effort, including errors and fallback, rather than assuming a fixed percentage can be automated.

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.