What Is a Tagged PDF?

A tagged PDF includes a logical structure tree describing roles and relationships in its content. Headings, paragraphs, lists, tables and figures can use that structure to support navigation and interpretation.

Presence is only the beginning

A file can contain tags that are incomplete or wrong. A heading may be a paragraph, text may appear in the wrong order or a table may lack correct header associations. Content can also be omitted from the structure. A checker identifying tags is not proof of usable reading order or meaning.

Build useful structure

Prefer semantic authoring in the editable source and a supported export. For an existing PDF, use an appropriate editor and verify associations with the actual content. Treat decorative material and informative figures differently. Confirm descriptions, document language and text accuracy.

Automatic tagging can provide a starting point where supported. Complex layouts and subject-specific material can need significant manual correction. No generic accuracy percentage describes every document.

Evaluate the saved file

Run a validator supporting the chosen target and investigate findings. Complete manual checks and test important tasks with the intended reader and assistive technology. A PDF/UA identifier is a claim to assess rather than a substitute for evaluation.

Keep the original and inspect the actual saved output. Combine relevant automated checks with manual review of meaning, reading order, navigation and content preservation. Test important student tasks with the intended reader and assistive technologies. A clean checker report alone does not establish conformance.

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.