Skip to main content
Accessibility.com, LLC
Category: Document Accessibility

Tag Tree

Also known as: Tag Structure, PDF Tag Tree
Simply put

A tag tree is the organized, hierarchical map of tags in a PDF document that defines the structure of its content, such as headings, paragraphs, lists, and tables. This structure helps assistive technologies like screen readers understand and present content in a logical order. Reviewing and correcting the tag tree is a common step in making a PDF more accessible.

Formal definition

The tag tree is the hierarchical arrangement of structure tags within a tagged PDF, in which each piece of content maps to a corresponding tag that conveys its role and relationships. Tags are organized into a parent-child hierarchy with a defined logical reading order, so that a tag may have parent (superior) and child elements. Tools such as Adobe Acrobat Pro expose the tag tree for inspection and editing, allowing practitioners to verify and correct structural semantics that determine how the document is exposed to assistive technologies. Note that a well-formed tag tree supports, but does not by itself guarantee, an accessible experience; manual and assistive-technology testing are generally required to confirm usability.

Why it matters

The tag tree is the structural foundation of an accessible PDF. Assistive technologies such as screen readers rely on the tags and their hierarchy to interpret content, so a document that looks visually organized may still be inaccessible if the underlying tag tree is missing, incomplete, or incorrectly ordered. When headings, paragraphs, lists, and tables are properly tagged and arranged, a screen reader can present the content in a logical reading order and allow users to navigate efficiently.

Because PDFs are widely used to distribute forms, reports, policies, and public information, the state of the tag tree often determines whether a document meets accessibility expectations commonly associated with WCAG success criteria for structure and reading order. Reviewing and correcting the tag tree is therefore a common step in PDF remediation workflows. It is worth emphasizing, however, that a well-formed tag tree supports but does not by itself guarantee an accessible experience; automated checks detect only a portion of potential issues, and manual review with assistive technology is generally required to confirm usability.

This entry is informational and not legal advice. Whether a given document meets a specific legal or contractual requirement depends on the applicable authority and evolving regulation and case law, and organizations should consult qualified legal counsel and current agency guidance where obligations are in question.

Who it's relevant to

Document remediation specialists
Practitioners who make PDFs accessible work directly in the tag tree to add missing tags, fix reading order, and correct structural semantics. Inspecting and editing the tag tree in tools like Adobe Acrobat Pro is a core part of their workflow, alongside manual and assistive-technology testing.
Accessibility engineers and QA testers
Those responsible for verifying accessibility use the tag tree to confirm that headings, lists, tables, and other content are tagged and ordered correctly. Because automated checks catch only a portion of issues, they pair tag tree review with hands-on testing to validate the actual user experience.
Content authors and form designers
People building documents and interactive forms in tools such as Adobe Acrobat Pro can use the tag tree to help ensure their content is structured for screen reader users. Attention to structure during authoring can reduce the amount of remediation needed later.
Compliance officers and program managers
Those overseeing digital accessibility programs benefit from understanding that the tag tree underpins whether PDFs can be interpreted by assistive technologies. This context supports decisions about remediation scope and testing, though determinations about specific legal obligations should involve qualified legal counsel and current agency guidance.

Inside Tag Tree

Structure Elements
The hierarchical nodes in a tagged PDF that represent logical document structures such as headings, paragraphs, lists, tables, and figures, organized in a parent-child arrangement that assistive technology can traverse.
Root (StructTreeRoot)
The top-level container from which the entire tag tree descends. It anchors the logical structure hierarchy of a tagged PDF and is referenced by the document catalog.
Standard Structure Types
Named tag types (for example, H1 through H6 for headings, P for paragraphs, L/LI for lists, and Table/TR/TH/TD for tables) that map content to recognizable semantic roles so screen readers can convey meaning and relationships.
Reading Order
The sequence in which tagged content is exposed to assistive technology, determined by the order of elements within the tree rather than the visual placement of content on the page.
Alternative Text and Metadata
Descriptive attributes attached to structure elements, such as alternate text for figures or scope and headers associations for table cells, that provide accessible names and relationships.
Artifacts
Content marked as decorative or non-informational (such as page numbers or background graphics) that is generally excluded from the logical structure so it is not announced to assistive technology users.

Common questions

Answers to the questions practitioners most commonly ask about Tag Tree.

Does a properly structured tag tree automatically make a PDF fully accessible?
No. A tag tree provides the underlying structure that assistive technologies rely on to interpret a PDF's content and reading order, but structure alone does not guarantee an accessible experience. Tags can be present yet incorrect, mislabeled, or in the wrong order, and other factors such as meaningful alternative text, correct reading order, adequate color contrast, and properly labeled form fields also affect accessibility. Automated checks can detect only a portion of potential issues, so manual review and testing with assistive technology are generally needed to confirm that a tagged PDF is usable.
Is having a tag tree the same as conforming to WCAG or complying with the ADA?
No. A tag tree is a technical component of an accessible document, not a conformance or legal status. WCAG is a set of technical guidelines published by the W3C, and conformance depends on meeting applicable success criteria across the whole document, not on the presence of tags alone. The ADA is a US civil rights law that does not itself specify PDF tagging requirements, though WCAG is often cited as a benchmark in guidance and settlements. A correct tag tree can support conformance and compliance efforts, but it does not by itself establish either. Consult qualified legal counsel for advice on specific obligations.
How can I view and inspect the tag tree in a PDF?
Many PDF authoring and remediation tools provide a panel or view that displays the tag tree as a hierarchical structure, allowing you to expand elements and see how content is organized and labeled. Reviewing the tag tree lets you confirm that headings, lists, tables, figures, and other elements are represented with appropriate tags. Inspecting the tags visually should be paired with testing using assistive technology, since the way the structure is announced to a user can reveal issues that a static view of the tree may not surface.
What is the relationship between the tag tree and the document's reading order?
The tag tree defines the logical sequence in which tagged content is presented to assistive technologies, which is what determines the reading order a screen reader user typically experiences. This logical order can differ from the visual layout on the page, so content that looks correct visually may still be read in an unexpected sequence if the tags are arranged improperly. Reviewing and correcting the order of elements within the tag tree is a common part of remediation, and testing with a screen reader helps verify that the resulting order is meaningful.
How are tables and lists represented in a tag tree?
Tables and lists are generally represented through nested tag structures that reflect their organization. A list is commonly tagged so that the list, its individual items, and item content are distinguished, while a table is typically tagged with elements identifying rows, cells, and header cells so that relationships between data and headers can be conveyed. When these structures are tagged correctly, assistive technologies can help users navigate and understand the relationships; when they are flattened or mislabeled, the meaning may be lost even if the content appears correct visually.
When should the tag tree be created or reviewed during document production?
Addressing tagging as part of the authoring process is often more efficient than remediating a finished file, because many authoring tools can generate tags from correctly structured source content such as styled headings and defined table headers. Whether tags are produced during authoring or added later, reviewing the tag tree before publication helps confirm that the structure, labeling, and order are correct. Because tagging is only one part of accessibility, this review should be combined with broader manual and assistive technology testing.

Common misconceptions

A PDF that looks correctly formatted visually will have a correct tag tree.
Visual layout and the underlying tag tree are independent. A document can appear well organized on screen while having a missing, incomplete, or incorrectly ordered tag tree, which can produce a confusing or inaccessible experience for assistive technology users. The tag tree generally must be reviewed separately from visual appearance.
Running an automated PDF accessibility check confirms the tag tree is fully accessible.
Automated tools detect only a portion of potential issues. They may confirm that tags exist but cannot reliably verify that reading order is logical, that alternative text is meaningful, or that structure accurately reflects content. Manual review and testing with assistive technology are generally required.
Simply adding tags to a PDF makes it compliant with accessibility standards.
The presence of tags is not the same as a correct, complete, and logically ordered tag tree. Conformance with recognized guidance depends on accurate semantics, proper reading order, and meaningful descriptions, and meeting technical criteria does not by itself guarantee an accessible experience or legal compliance.

Best practices

Build structure from the source document by using proper heading, list, and table styles before exporting to PDF, which generally produces a more reliable tag tree than tagging after the fact.
Review the tag tree manually to confirm that reading order is logical and that each element uses the appropriate standard structure type for its content.
Provide meaningful alternative text for figures and establish header and scope associations for tables so relationships are conveyed to assistive technology.
Mark purely decorative or repetitive page content as artifacts so it is not announced to assistive technology users.
Combine automated checks with manual inspection and testing using a screen reader, since automated testing alone detects only a portion of issues.
Treat tag tree correctness as one component of accessibility rather than a guarantee of conformance or legal compliance, and consult qualified legal counsel and current standards where obligations are in question.