Category: Document Accessibility

PDF Tags

Also known as: Tagged PDF, PDF Structure Tags

Simply put

PDF tags are hidden labels within a PDF that describe the structure of its content, such as which text is a heading, a list, or a paragraph. These tags allow assistive technologies, like screen readers, to present the document's content in a logical, meaningful order to people with disabilities. A PDF that contains these labels is commonly called a 'tagged PDF.'

Formal definition

PDF tags form a set of standard structure types and attributes that define a logical structure tree for a PDF document, enabling page content (text, graphics, and images) to be extracted, reordered, and reused by assistive technology. Tags convey semantic roles and reading order, for example marking list content with list tags rather than relying on visual formatting alone. Applying correct, semantic tags is generally most reliable when done in the source authoring tool (such as Microsoft Word or OpenOffice) before export. Recognized references, including the Section 508 program guidance and the PDF 1.7 standard tag set, catalog common tags and their intended usage. Note that the presence of tags supports, but does not by itself guarantee, an accessible document; manual review and assistive technology testing are generally needed to confirm correct structure and reading order. This entry is informational and not legal advice.

Why it matters

PDF documents are widely used to distribute information, but a PDF that lacks proper tags can be difficult or impossible for assistive technology users to navigate. Without a logical structure tree, a screen reader may present content in an illogical order, fail to distinguish headings from body text, or read a list as an undifferentiated block of text. PDF tags supply the semantic roles and reading order that allow assistive technologies to extract and present content in a meaningful sequence, which is often what determines whether a document is usable for people with disabilities.

Because tags describe structure rather than appearance, they address problems that visual formatting alone cannot solve. A heading that merely looks large and bold conveys no structural meaning to a screen reader unless it is tagged as a heading. Similarly, list content marked only through visual indentation may not be announced as a list. Applying correct, semantic tags supports a more predictable and navigable experience, and it is generally most reliable when tags are created in the source authoring tool before the document is exported to PDF.

It is important to recognize that the presence of tags supports accessibility but does not by itself guarantee an accessible document. Tags can be incorrect, incomplete, or applied to the wrong content, and reading order can still be flawed. For this reason, manual review and testing with assistive technology are generally needed to confirm that structure and reading order are correct. This entry is informational and not legal advice; requirements can vary by context and evolve through regulation and case law.

Who it's relevant to

Document authors and content creators

People who produce PDFs from tools like Microsoft Word or OpenOffice benefit from understanding that using built-in structural markup, such as heading and list styles, in the source document generally produces more reliable tags on export. Creating structure at the authoring stage is often easier and more accurate than adding or correcting tags after the PDF is generated.

Accessibility specialists and testers

Those responsible for evaluating documents need to confirm that tags are present, semantically correct, and produce a logical reading order. Because the presence of tags does not by itself guarantee accessibility, manual review and testing with assistive technology such as screen readers are generally required to verify that the structure works as intended.

Assistive technology users

People who rely on screen readers and similar tools depend on tags to navigate a PDF's content in a meaningful order, distinguish headings from body text, and correctly interpret lists and other structures. A tagged PDF is often what makes the difference between a document that is navigable and one that is not.

Compliance officers and organizational decision-makers

Those overseeing document accessibility programs should understand that tagging is a foundational practice for accessible PDFs but is one part of a broader process that includes review and testing. This entry is informational and not legal advice; organizations with questions about specific legal obligations should consult qualified legal counsel and current agency guidance.

Inside PDF Tags

Structure Tags

Elements that define the logical structure of a PDF, such as headings, paragraphs, lists, and tables, allowing assistive technology to interpret and convey the document's organization.

Reading Order

The sequence in which tagged content is presented to assistive technology, which may differ from the visual layout and should reflect the intended logical flow of the document.

Alternative Text

Text descriptions associated with images and non-text elements within tags, enabling screen reader users to understand content that is otherwise inaccessible.

Table Structure Tags

Tags identifying table headers, rows, and data cells so that relationships between cells can be conveyed programmatically to assistive technology users.

Semantic Roles

Tags that assign meaning to content, distinguishing, for example, a heading from body text, so that navigation and comprehension are supported for users of assistive technology.

Common questions

Answers to the questions practitioners most commonly ask about PDF Tags.

Does adding tags to a PDF automatically make it accessible?

No. Adding tags is a necessary step but not sufficient on its own. Tags provide the underlying structure that assistive technologies rely on, but a tagged PDF can still have problems such as an incorrect reading order, missing or inaccurate alternative text, tags that do not match the visual content, or poorly structured tables. Tagging should generally be paired with manual review and testing with assistive technology to confirm the document is usable.

Is running a PDF through an automated accessibility checker enough to confirm the tags are correct?

Automated checkers detect only a portion of potential issues. They can flag missing tags, absent alternative text, or the absence of a document language, but they generally cannot reliably confirm that the reading order is logical, that alternative text is meaningful, or that headings and tables have been tagged in a way that reflects the content's actual structure. Manual review and testing with a screen reader are commonly needed to evaluate these aspects.

How do PDF tags relate to WCAG conformance?

PDF tags support conformance with WCAG success criteria that address structure, reading order, text alternatives, and programmatic determination of content. AA is the conformance level most commonly cited as a target. Properly applied tags help satisfy relevant criteria, but conformance is evaluated against the applicable success criteria as a whole rather than by the presence of tags alone. This guidance is not legal advice, and applicable requirements can vary by jurisdiction and context.

What structural elements should PDF tags typically capture?

Tags generally identify the semantic role of content, such as headings and their levels, paragraphs, lists, tables with their header cells, links, and figures with associated alternative text. The tag structure also establishes the reading order that assistive technologies follow. The goal is for the tagged structure to accurately reflect the document's intended organization and visual presentation.

How can PDF tags be added to a document?

Tags can often be generated during export from an authoring tool when the source document is created with proper structure, such as using built-in heading and list styles. Tags can also be added or corrected within PDF editing software that supports reviewing and adjusting the tag tree, reading order, and alternative text. Starting from a well-structured source document generally reduces the amount of manual remediation needed later.

How should the reading order of a tagged PDF be verified?

Because visual layout does not always match the order in which content is presented to assistive technology, the reading order should be reviewed separately from the tag structure. This is commonly done using tools that expose the reading order and by testing the document with a screen reader to confirm that content is announced in a logical sequence that matches the intended flow.

Common misconceptions

A PDF that looks accessible visually is automatically accessible to assistive technology.

Visual appearance does not determine accessibility. Without proper tags, a screen reader may be unable to interpret structure, reading order, or non-text content, regardless of how the document appears on screen.

Automatically generating tags when exporting a PDF guarantees an accessible, conforming document.

Automated tagging often produces incomplete or incorrect results. Automated processes detect only a portion of potential issues, and manual review and testing with assistive technology are generally needed to confirm accurate structure, reading order, and alternative text.

Adding PDF tags ensures compliance with the ADA or other legal requirements.

Tagging supports accessibility and can help address success criteria commonly cited under WCAG, but conformance with technical guidelines does not itself guarantee legal compliance or immunity from claims. Legal requirements evolve through regulation and case law, and qualified legal counsel should be consulted.

Best practices

Verify and correct the logical reading order after tagging, since it may not match the visual layout and can affect how assistive technology conveys content.

Provide meaningful alternative text for images and non-text elements, and mark purely decorative elements so they are ignored by assistive technology.

Use proper table tags to identify header and data cells, ensuring relationships between cells are conveyed programmatically.

Apply semantic tags such as headings, lists, and paragraphs rather than relying on visual formatting alone to imply structure.

Test tagged PDFs with screen readers and other assistive technology in addition to automated checks, recognizing that automated tools detect only a portion of issues.

Treat WCAG success criteria as a benchmark target, commonly the AA level, while consulting qualified legal counsel regarding applicable legal obligations, which vary by jurisdiction and evolve over time.