Creating an accessible PDF is no longer optional for organizations that need to comply with accessibility regulations such as the Americans with Disabilities Act (ADA), Section 508, WCAG 2.2, and PDF/UA standards. Adobe Acrobat Pro’s Auto-Tag Document feature provides a fast starting point by automatically identifying headings, paragraphs, images, lists, and tables. However, Auto-Tag is not perfect. It frequently misidentifies document structure, skips decorative elements, creates incorrect reading orders, and fails to properly tag complex layouts.
Understanding how to use Adobe Acrobat Pro Auto-Tag feature and manually correct its output is essential for producing accessible PDFs that work reliably with screen readers such as JAWS, NVDA, and VoiceOver.
Quick Answer
Adobe Acrobat Pro’s Auto-Tag feature automatically generates accessibility tags for an untagged PDF. While it saves significant time, every document should be manually reviewed and corrected by checking the tag tree, reading order, headings, tables, lists, figures, alt text, and accessibility checker results before publication.
Definition Box
What Is Auto-Tag?
Auto-Tag is an Adobe Acrobat Pro accessibility tool that analyzes a PDF and automatically creates structural tags such as headings, paragraphs, lists, tables, and figures. It provides a starting point—not a finished accessible document—and always requires manual quality assurance.
Why Is PDF Tagging Important?
Tagged PDFs allow assistive technologies to interpret document structure correctly.
Without tags, screen readers often read content out of order, ignore headings, skip images, or make navigation difficult for users with disabilities.
Accessible PDFs also improve usability, document navigation, and long-term digital inclusion.
What Does Adobe Acrobat Pro Auto-Tag Actually Do?
The Auto-Tag feature scans a PDF and attempts to identify:
Document title
Paragraphs
Headings
Lists
Tables
Images
Figures
Reading order
Language metadata
Basic document structure
Its accuracy depends heavily on how the PDF was originally created. Files exported from Microsoft Word or Adobe InDesign typically produce better results than scanned documents or poorly formatted PDFs.
When Should You Use Auto-Tag?
Auto-Tag works best when:
The document already has consistent formatting.
Headings are used properly.
Lists are correctly created.
Tables contain logical structure.
Images are clearly distinguishable.
The PDF originated from Word, InDesign, or another structured authoring tool.
For scanned PDFs, OCR (Optical Character Recognition) should be completed before Auto-Tagging.
How to Use Adobe Acrobat Pro Auto-Tag Feature
Follow these steps to generate accessibility tags.
Step 1: Open the PDF
Launch Adobe Acrobat Pro.
Open the document you want to make accessible.
Step 2: Open Accessibility Tools
Navigate to:
Tools → Accessibility
If Accessibility isn’t visible, search for it using the Tool Finder.
Step 3: Run Auto-Tag Document
Select:
Auto-Tag Document
Acrobat analyzes the document and creates an initial tag structure.
Processing time depends on document size and complexity.
Step 4: Open the Tags Panel
Navigate to:
View → Show/Hide → Navigation Panes → Tags
Review the automatically generated hierarchy.
Look for:
Missing headings
Incorrect nesting
Empty tags
Duplicate tags
Untagged content
Step 5: Review Reading Order
Select:
Accessibility → Reading Order
Ensure the content flows logically from top to bottom and left to right.
Complex layouts often require manual adjustments.
Step 6: Run Accessibility Checker
Choose:
Accessibility → Full Check
Review warnings and errors.
Common issues include:
Missing alt text
Untagged annotations
Table structure errors
Missing document language
Title not specified
Why Auto-Tag Is Not Enough
Auto-Tag relies on algorithms, not human understanding.
It cannot always distinguish between:
Decorative images and meaningful figures
Data tables and layout tables
Heading hierarchy
Complex sidebars
Footnotes
Multi-column reading order
Every accessibility professional should manually inspect the final output.
How to Manually Correct Auto-Tag Errors
Fix Heading Structure
Verify headings follow a logical hierarchy.
Correct example:
H1
H2
H3
Incorrect example:
H1
H4
H2
Proper heading order improves navigation for screen reader users.
Correct Reading Order
Use the Reading Order Tool to rearrange content blocks.
Pay particular attention to:
Multi-column layouts
Sidebars
Floating images
Captions
Footnotes
Incorrect reading order is one of the most common accessibility failures.
Add Alternative Text
Every meaningful image requires descriptive alternative text.
Good example:
“Bar chart showing annual website traffic increasing from 2023 to 2025.”
Avoid:
“Image”
or
“Picture”
Decorative graphics should be marked as artifacts rather than assigned alt text.
Repair Tables
Tables require:
Table tag
Header row
Header cells (TH)
Data cells (TD)
Proper scope relationships
Merged cells and nested tables often require manual editing.
Fix Lists
Ensure lists use:
List (L)
List Item (LI)
Label (Lbl)
List Body (LBody)
Do not leave bullet points as plain paragraphs.
Remove Empty Tags
Auto-Tag sometimes creates empty structural elements.
Delete unnecessary tags to simplify navigation.
Mark Decorative Elements as Artifacts
Borders, background graphics, separators, and decorative icons should be artifacts rather than tagged content.
This reduces unnecessary announcements by screen readers.
Set Document Properties
Verify:
Document title
Language
Initial view
Tagged PDF option
These settings improve accessibility and search indexing.
Common Auto-Tag Errors and Manual Fixes
Auto-Tag Issue
Manual Correction
Incorrect heading level
Edit tag type to correct H1-H6
Wrong reading order
Reorder content in Reading Order panel
Missing alt text
Add descriptive alt text
Layout tables
Convert to artifacts if appropriate
Missing table headers
Assign TH tags
Empty tags
Remove unused tags
Decorative images tagged
Mark as artifacts
Untagged annotations
Tag or remove annotations
Best Practices for Accessible PDFs
Follow these recommendations before publishing:
Use properly styled headings in the source document.
Export tagged PDFs from Word or InDesign.
Run OCR on scanned documents.
Use Auto-Tag only as a starting point.
Review every tag manually.
Verify reading order.
Add meaningful alt text.
Check table structure.
Run Acrobat Accessibility Checker.
Test with a screen reader such as NVDA or JAWS.
Auto-Tag vs Manual Tagging
Feature
Auto-Tag
Manual Tagging
Speed
Very Fast
Time-Intensive
Accuracy
Moderate
High
Reading Order
Often Needs Review
Fully Controlled
Table Support
Basic
Excellent
Heading Accuracy
Variable
Precise
Complex Layouts
Limited
Strong
Accessibility Compliance
Partial
Comprehensive
Recommended Use
Initial Draft
Final Accessibility Review
Common Mistakes to Avoid
Publishing without reviewing Auto-Tag output
Ignoring reading order
Leaving images without alt text
Skipping accessibility checker warnings
Using visual formatting instead of structural headings
Does Adobe Acrobat Pro Auto-Tag create fully accessible PDFs?
No. Auto-Tag creates an initial tag structure, but manual review and correction are almost always required to meet accessibility standards such as WCAG and PDF/UA.
Why is my reading order incorrect after Auto-Tag?
Auto-Tag analyzes visual layout rather than human reading intent. Multi-column documents, sidebars, captions, and complex page designs frequently require manual adjustment using the Reading Order tool.
Can Auto-Tag add alt text automatically?
Adobe Acrobat Pro may identify figures, but it does not reliably generate accurate alternative text for meaningful images. Alt text should be reviewed and written manually to ensure it conveys the image’s purpose.
Should scanned PDFs be Auto-Tagged immediately?
No. Scanned PDFs should first undergo Optical Character Recognition (OCR) so Acrobat can recognize text before creating accessibility tags. Tagging a non-OCR document often produces poor results.
How do I know if my PDF meets accessibility standards?
Run Acrobat’s Accessibility Checker, review all warnings, manually inspect the tag tree, verify reading order, and test with assistive technologies such as NVDA or JAWS. Automated tools alone cannot guarantee compliance.
Is Auto-Tag enough for PDF/UA compliance?
No. PDF/UA compliance requires accurate structural tagging, logical reading order, proper table markup, meaningful alternative text, document metadata, and manual quality assurance. Auto-Tag provides only the initial framework.
Pingback: Step-by-Step: Setting Logical Reading Order in Scanned PDFs - AccessiComply
Pingback: How to Use Adobe Acrobat Pro Auto-Tag Feature (and Manual Correction Guide) - AccessiComply