What does it mean for a PDF to be "tagged"?

A tagged PDF includes structural metadata describing the document hierarchy — headings, paragraphs, lists, tables, images — separately from the visual layout. The tags form a tree (defined in ISO 32000-1 §14.8) that screen readers and reflow tools traverse to present content correctly. Without tags, screen readers fall back to top-to-bottom raw text extraction which often produces scrambled reading order for multi-column or complex layouts. Tags are what make PDFs genuinely accessible rather than visually-similar-to-a-document.

How do I check if a PDF is tagged?

Acrobat Pro: File → Properties → Description tab; look for "Tagged PDF: Yes" near the bottom. Alternatively, View → Show/Hide → Navigation Panes → Tags opens the tag tree — a populated tree means tagged; "No Tags Available" means untagged. Free verification: pdfinfo command line (`pdfinfo file.pdf | grep Tagged`) shows tagging status. For accessibility compliance, also verify the tag tree makes sense — autogenerated tags can be present but wrong (every paragraph tagged as <P> but headings missed).

How do I produce a tagged PDF at export?

Per authoring tool. Microsoft Word: File → Save As → PDF → Options → "Document structure tags for accessibility" enabled. Google Docs: tagged by default in File → Download → PDF Document. InDesign: File → Export → PDF → Advanced → Create Tagged PDF. LibreOffice: File → Export as PDF → check "Tagged PDF". Pages (macOS): File → Export → PDF → tagged by default in newer versions. For all of these, the source document needs proper heading styles, lists, and table structure for the export to produce meaningful tags — applying Heading 1 / Heading 2 / Bullet List in Word is what gives the exported tags semantic content.

My PDF arrived untagged. How do I add tags retroactively?

Acrobat Pro: Tools → Accessibility → Autotag Document. Acrobat infers tags from font sizes, layout, and content patterns. Result is usable for simple documents but needs review and cleanup for complex ones — open the tag tree, walk through each tag, fix misclassifications (a caption tagged as a heading, a table tagged as a list). For high-stakes accessibility compliance, manual remediation by an accessibility specialist is the gold standard; for ordinary documents, autotag + spot review is usually sufficient.

How do tags interact with reflow mode for low-vision readers?

Reflow uses the tag tree to determine reading order when re-flowing text into a single column at chosen font size. Without tags, reflow guesses based on visual position which often produces scrambled output for multi-column layouts. With proper tags, reflow respects the document structure — headings stay as headings, lists stay as lists, sidebars and footnotes stay in their logical reading position rather than interleaved into body text. For low-vision accessibility, tags and reflow are complementary; both matter.

5 min read

PDF accessibility tags — what they are and how to add them

By ScoutMyTool Editorial Team · Last updated: 2026-05-20

PDFs look identical to readers whether tagged or untagged, but they read entirely differently to screen readers and reflow tools. A properly tagged PDF presents its structure (headings, paragraphs, lists, tables, images) to assistive technology cleanly; an untagged PDF fed through a screen reader often produces scrambled reading order, mis-announced headings, and inaccessible images. ADA Title III, EU Accessibility Directive, and Section 508 all converge on tagged PDFs as the baseline. This article maps the tag structure, the authoring workflow that produces tagged exports, and the remediation path for PDFs that arrive untagged.

Core PDF accessibility tags

Tag	Purpose
<Document>	Root container of all document content
<H1> – <H6>	Heading levels — screen readers announce as navigation landmarks
<P>	Paragraph — body text block
<L> / <LI>	List / list item — read as a list, not as separate paragraphs
<Table>	Table structure with row / column relationships preserved
<Figure>	Image or graphic; alt text in /Alt attribute
<Link>	Hyperlink — screen readers announce as activatable link
<Span>	Inline structure for language tags, emphasis, etc.

Step by step — produce a tagged PDF from Word

Apply heading styles in the source. Use Heading 1, Heading 2, Heading 3 paragraph styles for section titles — not just bolded body text. Lists via the bullet/numbered list buttons. Tables via Insert Table (not tab-aligned text).
Add alt text to images. Right-click image → Edit Alt Text. Write a concise description of what the image conveys (not just "photo").
Set document language. File → Info → Properties → Language. Screen readers use this to pick pronunciation engine.
Export with accessibility tags. Save As → PDF → Options → "Document structure tags for accessibility" checked.
Verify in Acrobat Pro. Open the PDF; Tools → Accessibility → Accessibility Check. Address any flagged issues; re-export from source rather than fixing in PDF where possible.

Remediating untagged PDFs

When you receive an untagged PDF that needs accessibility compliance, three paths. First, request a tagged version from the source — fastest if the sender has the source document. Second, Acrobat Pro autotag with manual review — Tools → Accessibility → Autotag Document, then walk through the tag tree fixing misclassifications. Third, professional remediation — services like Allyant or CommonLook produce WCAG-compliant tagged PDFs from any source, typically $50–$300 per document depending on length and complexity.

For organisations producing many PDFs at scale (government agencies, publishers, educators), invest upstream in tagged-PDF authoring habits and templates rather than retroactive remediation. A correctly-styled Word template exports to a tagged PDF in one click; the same work done post-hoc in Acrobat Pro takes 30–90 minutes per document. The upfront investment in template design pays back hundreds of hours over time and produces better accessibility than autotag remediation.

Validation tools and standards

Three tools verify tagged-PDF compliance. PAC (PDF Accessibility Checker) from access-for-all.ch is the open-source standard, free download for Windows; runs against ISO 14289 / PDF/UA-1 rules and produces detailed reports. Acrobat Pro's Accessibility Check (Tools → Accessibility → Full Check) covers most of the same checks within Acrobat's UI; result is good for ordinary documents, less thorough than PAC for edge cases. CommonLook PDF Validator (commercial) and Allyant scanners are the enterprise-grade options used by accessibility-compliance firms.

Compliance standards worth knowing: ISO 14289 (PDF/UA) is the universal accessibility standard; ADA Title III is the US-federal-regulated accessibility law for public-facing documents; EN 301 549 is the EU equivalent; Section 508 applies to US federal agencies. For most organisations, conforming to PDF/UA produces compliance with all four simultaneously — the underlying technical requirements overlap heavily. Build PDF/UA conformance into your authoring template and validate every outbound public PDF against PAC.

FAQ

What does it mean for a PDF to be "tagged"?: A tagged PDF includes structural metadata describing the document hierarchy — headings, paragraphs, lists, tables, images — separately from the visual layout. The tags form a tree (defined in ISO 32000-1 §14.8) that screen readers and reflow tools traverse to present content correctly. Without tags, screen readers fall back to top-to-bottom raw text extraction which often produces scrambled reading order for multi-column or complex layouts. Tags are what make PDFs genuinely accessible rather than visually-similar-to-a-document.
How do I check if a PDF is tagged?: Acrobat Pro: File → Properties → Description tab; look for "Tagged PDF: Yes" near the bottom. Alternatively, View → Show/Hide → Navigation Panes → Tags opens the tag tree — a populated tree means tagged; "No Tags Available" means untagged. Free verification: pdfinfo command line (`pdfinfo file.pdf | grep Tagged`) shows tagging status. For accessibility compliance, also verify the tag tree makes sense — autogenerated tags can be present but wrong (every paragraph tagged as <P> but headings missed).
How do I produce a tagged PDF at export?: Per authoring tool. Microsoft Word: File → Save As → PDF → Options → "Document structure tags for accessibility" enabled. Google Docs: tagged by default in File → Download → PDF Document. InDesign: File → Export → PDF → Advanced → Create Tagged PDF. LibreOffice: File → Export as PDF → check "Tagged PDF". Pages (macOS): File → Export → PDF → tagged by default in newer versions. For all of these, the source document needs proper heading styles, lists, and table structure for the export to produce meaningful tags — applying Heading 1 / Heading 2 / Bullet List in Word is what gives the exported tags semantic content.
My PDF arrived untagged. How do I add tags retroactively?: Acrobat Pro: Tools → Accessibility → Autotag Document. Acrobat infers tags from font sizes, layout, and content patterns. Result is usable for simple documents but needs review and cleanup for complex ones — open the tag tree, walk through each tag, fix misclassifications (a caption tagged as a heading, a table tagged as a list). For high-stakes accessibility compliance, manual remediation by an accessibility specialist is the gold standard; for ordinary documents, autotag + spot review is usually sufficient.
How do tags interact with reflow mode for low-vision readers?: Reflow uses the tag tree to determine reading order when re-flowing text into a single column at chosen font size. Without tags, reflow guesses based on visual position which often produces scrambled output for multi-column layouts. With proper tags, reflow respects the document structure — headings stay as headings, lists stay as lists, sidebars and footnotes stay in their logical reading position rather than interleaved into body text. For low-vision accessibility, tags and reflow are complementary; both matter.

Citations

ISO 32000-1:2008 — "Document management — Portable document format" — §14.8 (Tagged PDF).
ISO 14289 — PDF/UA (Universal Accessibility) standard.
WCAG 2.1 — Web Content Accessibility Guidelines.
US Section 508 — federal accessibility requirements for electronic documents.
Adobe Acrobat — Accessibility documentation including tag tree and autotag.

Verify PDF tagging status in your browser

ScoutMyTool PDF Metadata Editor surfaces tag status alongside other PDF metadata. Quick check before distributing.

Open Metadata Editor →