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

Tagged PDF

Simply put

A tagged PDF is a PDF document that contains an underlying set of tags describing how its content is organized, such as headings, paragraphs, lists, and images. These tags help assistive technologies, like screen readers, present the document's content in a logical, understandable order. Tagging is commonly used to support PDF accessibility, though tags alone do not guarantee that a document is fully accessible.

Formal definition

A Tagged PDF is a PDF that includes a structured tag tree, analogous in concept to HTML structure, defining the logical reading order and semantic roles of page content (text, graphics, and images) so that content can be extracted and reused by assistive technology. Tags apply standard structure types and attributes to page elements, enabling reliable navigation and interpretation. Tagged PDF is generally cited as a foundational technique for meeting PDF accessibility requirements associated with Section 508 and PDF/UA (PDF Universal Accessibility), but the presence of tags does not by itself ensure conformance; proper tag semantics, reading order, and manual and assistive-technology verification are typically required.

Why it matters

PDFs are one of the most widely distributed document formats for forms, reports, policies, and public information, yet an untagged PDF is often little more than a visual image of text to a screen reader. Without an underlying tag tree, assistive technology may present content in an illogical order, skip images entirely, or fail to convey headings, lists, and tables in a way users can navigate. Tagging is generally cited as a foundational technique for making PDF content perceivable and operable for people who rely on assistive technology.

Tagged PDF is commonly associated with meeting PDF accessibility requirements under Section 508, which applies to federal agencies and covered federal contexts, and with PDF/UA (PDF Universal Accessibility), a technical standard for accessible PDFs. Organizations that publish documents to the public or to employees may need to consider these expectations, though the specific authority that applies depends on the entity and context. Nothing here is legal advice, and readers should consult qualified counsel and current agency guidance for their situation.

It is important to understand that the presence of tags does not by itself guarantee an accessible document. Tags can be incorrect, incomplete, or applied in a way that produces a misleading reading order. Proper tag semantics, a logical reading order, and manual and assistive-technology verification are typically required to confirm that a tagged PDF actually works for users. Automated tagging or automated checks detect only a portion of potential issues.

Who it's relevant to

Document authors and content creators
People who produce PDFs from word processors, design tools, or authoring software are responsible for how content is structured. Understanding tags, headings, lists, images, and reading order, helps them create documents that can be interpreted correctly by assistive technology rather than presented as an unstructured or out-of-order block of content.
Accessibility and compliance teams
Teams evaluating documents against Section 508 or PDF/UA expectations rely on tagged PDF as a foundational technique, while recognizing that tags alone do not ensure conformance. They typically confirm proper tag semantics and reading order through manual and assistive-technology testing rather than automated checks alone.
Federal agencies and covered contractors
Because Section 508 applies to federal agencies and covered federal contexts, entities operating in these settings often treat tagged PDF as part of meeting their document accessibility obligations. The specific requirements that apply depend on the context, and current agency guidance should be consulted.
Assistive technology users
People who use screen readers and similar tools depend on a document's tag tree to access its content in a logical, navigable order. A well-tagged PDF supports reliable navigation and interpretation, while an untagged or poorly tagged PDF can make information difficult or impossible to use.
Legal counsel and business leaders
Decision-makers assessing document accessibility should understand that tagging is a technical technique that supports accessibility but does not by itself guarantee accessibility or immunity from legal claims. Requirements evolve through regulation and case law, and qualified legal counsel should be consulted for specific obligations.

Inside Tagged PDF

Tag tree (structure tree)
A hierarchical set of tags embedded in the PDF that describes the logical reading order and semantic structure of the content, allowing assistive technologies to interpret the document as more than a visual layout.
Structural element tags
Semantic tags such as headings (H1 through H6), paragraphs (P), lists (L, LI), tables (Table, TR, TH, TD), and links that convey the role of each piece of content, similar in concept to structural markup in HTML.
Reading order
The defined sequence in which content is presented to screen readers, which can differ from the visual arrangement on the page and must reflect the intended logical flow.
Alternative text for non-text content
Text descriptions associated with images, figures, and other graphics so that users of assistive technology can access equivalent information.
Artifact designation
A mechanism for marking decorative or repeating elements, such as background graphics, page numbers, or running headers, so that assistive technology can skip content that is not part of the meaningful reading flow.
Document metadata and language
Information such as the document title and the specified natural language of the content, which helps assistive technology present the document correctly.

Common questions

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

Does tagging a PDF automatically make it accessible?
No. Adding tags is a necessary foundation, but a tagged PDF is not automatically accessible. Tags must be correct, complete, and logically ordered to convey structure and meaning; poorly applied or inaccurate tags can still produce a document that is difficult or impossible for assistive technology users to navigate. Beyond tags, factors such as meaningful alternative text, correct reading order, properly identified headings and tables, and language settings all contribute to accessibility. As with other formats, automated checks detect only a portion of potential issues, so manual review and testing with assistive technology are generally needed to confirm the experience works for users.
Does having a tagged PDF guarantee legal compliance?
No. Producing a tagged PDF may support conformance goals, but it does not by itself guarantee compliance with any particular law or immunity from legal claims. Applicable obligations depend on the authority involved, for example, Section 508 in covered federal contexts, or Title II or Title III of the ADA, and on how accessibility is evaluated under current regulation, agency guidance, and case law. Conformance to a technical benchmark and legal compliance are distinct considerations, and requirements evolve over time. This entry is not legal advice; organizations should consult qualified legal counsel and current agency rulemaking for their specific circumstances.
How do you create a tagged PDF?
Tagged PDFs are commonly created by exporting from an authoring application that supports accessibility, such as a word processor or layout program, using its accessibility or tagged-export options. Applying proper structure in the source document, true headings, lists, tables, and alternative text, generally carries that structure into the resulting tags. Tags can also be added or corrected directly in a PDF editor that exposes the tag tree. Whichever method is used, the resulting tags should be reviewed to confirm they reflect the intended structure rather than assuming the export produced correct results.
How can you check whether a PDF is properly tagged?
Reviewing a tagged PDF generally combines automated checks with manual inspection. Automated accessibility checkers can flag missing tags, absent alternative text, or missing language settings, but they detect only a portion of possible issues. Manual review of the tag tree helps confirm that headings, lists, tables, and reading order are represented accurately. Testing with assistive technology, such as a screen reader, is often used to verify that the document is navigable and that content is announced in a logical order. These methods are complementary rather than interchangeable.
What elements should be addressed when tagging a PDF?
Commonly addressed elements include a logical reading order, headings that reflect document hierarchy, lists and tables marked with appropriate structural tags, alternative text for meaningful images, identification of decorative content so it can be ignored by assistive technology, correct document language, and descriptive information such as a document title. Form fields, where present, generally need accessible labels and a sensible tab order. Addressing these elements helps assistive technology convey structure and meaning, though correct application still requires review.
What should you do with a scanned PDF that has no tags?
A scanned PDF is typically an image of a page and contains no underlying text or tags, so it is generally inaccessible to assistive technology until it is processed. Applying optical character recognition (OCR) can convert the image into recognizable text, but OCR output may contain errors and does not by itself produce a correct tag structure. After OCR, the recognized text usually needs review for accuracy, and structural tagging, reading order, and alternative text still need to be applied and verified.

Common misconceptions

A PDF that looks correct on screen is automatically accessible.
Visual appearance is independent of the underlying tag structure. A visually polished PDF may have no tags, an incorrect reading order, or missing alternative text, making it inaccessible to assistive technology even though it renders normally.
Automatically tagging a PDF through an export or conversion tool produces a fully accessible document.
Automated tagging often generates incomplete or inaccurate structures, such as missing alternative text, incorrect heading levels, or improper table tagging. Manual review and remediation with assistive technology testing are generally needed to confirm the document is usable.
Creating a tagged PDF guarantees WCAG conformance or legal compliance.
Tagging is one component that supports accessibility, but conformance depends on meeting applicable success criteria, and passing structural checks does not by itself guarantee an accessible experience for all users or immunity from legal claims. Requirements and expectations may vary by jurisdiction and evolve through regulation and case law.

Best practices

Define and verify a logical reading order that reflects the intended flow of content rather than relying solely on the visual layout.
Apply semantic tags accurately, using proper heading levels, list structures, and table tags (including header cells) to convey document structure.
Provide meaningful alternative text for images and other non-text content, and mark decorative or repeating elements as artifacts so they are skipped by assistive technology.
Treat automated tagging output as a starting point only, and manually review and remediate the tag tree to correct errors.
Test the document with screen readers and other assistive technologies, since automated checks detect only a portion of potential issues.
Set the document title and specify the natural language of the content so assistive technology can present it correctly.
Consult qualified legal counsel and current agency guidance regarding applicable requirements, as this guidance is not legal advice and obligations evolve through regulation and case law.