Documents
Inspect and Repair a PDF Tag Tree
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Review whether PDF tags represent the document's actual structure. Save a working copy before editing and identify whether a source-file repair would be more maintainable. Tag presence alone is not evidence that headings, lists and figures are correct.
A practical example
A report's tag tree contains a long sequence of paragraphs even though the visible document has sections, lists and figures.
How to check it
- Compare the tag tree with the document's intended outline. Identify missing content, incorrect element types and decorative material exposed as meaningful content.
- Repair a small section and verify the content associated with each tag. Preserve relationships such as list labels and bodies rather than treating every object as an isolated paragraph.
- Run a PDF accessibility check and read the repaired section with assistive technology. Save evidence of both the structure and the resulting reading experience.
What can be missed
Automatic tagging is a starting point for review. Re-tagging an already repaired file can undo deliberate structure, so keep a versioned source and repair record.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.