PDF Accessibility Tags Missing After Editing: Causes and Fixes

PDF accessibility is built on the logical structure tree — a hierarchical set of tags that describe the document's semantic structure. This tree is separate from the page content stream. When editing tools modify a PDF, they often interact with the page content but don't update or preserve the structure tree. **Operations that commonly destroy tags**: **Merging PDFs**: When two PDFs are merged, the structure trees of both documents need to be merged as well. Most merge tools don't attempt this — they just combine page content, discard both structure trees, and produce an untagged document. **Splitting PDFs**: Splitting extracts a range of pages. The extracted pages' subtree from the structure tree usually isn't carried over, producing untagged split documents. **Compressing PDFs**: Compression tools re-process the PDF structure. Tools that don't specifically preserve the tag structure will drop it during recompression. **Printing to PDF**: Printing renders the visual appearance to a new PDF, discarding all non-visual content including the structure tree, metadata, and form fields. **Ghostscript reprocessing**: Ghostscript's pdfwrite device, by default, discards the PDF's logical structure when processing. Ghostscript can be configured to preserve tags, but this is not the default. **Adobe Acrobat as exception**: Acrobat Pro's editing operations (page organization, combining files) make a best-effort attempt to preserve tags, though it's not always perfect.

1. 1Open the edited PDF in Adobe Acrobat and go to Tools > Accessibility > Full Check to verify tags are missing.
2. 2Check File > Properties > Description — if 'Tagged PDF' shows 'No', tags were stripped.
3. 3Determine which operation removed the tags (merge, split, compress, etc.).
4. 4If you have the original tagged PDF, use it as the starting point for re-editing with tag-aware tools.
5. 5If the edited content must be preserved, re-tag the document in Acrobat Pro using the Reading Order tool.
6. 6For recurring workflows, implement tag-preserving alternatives for each editing operation.

If tags were stripped and you need to restore accessibility to the edited PDF, Adobe Acrobat Pro provides tools for re-tagging. **Auto-tag the document**: 1. Open the PDF in Acrobat Pro 2. Go to Tools > Accessibility > Autotag Document 3. Acrobat analyzes the page content and generates tags automatically 4. The quality of auto-tagging depends on how well-structured the content is 5. Simple documents with clear headings and paragraphs auto-tag reasonably well; complex multi-column layouts may need manual correction **After auto-tagging, review and correct**: - Run Tools > Accessibility > Full Check to identify remaining issues - Use the Reading Order tool to verify and correct reading order - Check that all images have alt text - Verify table headers are properly marked - Ensure the document title is set in File > Properties **Manual tag repair with the Tags panel**: - View > Show/Hide > Navigation Panes > Tags - The Tags panel shows the complete structure tree - Drag tags to reorder, right-click to change type or add alt text - Add missing tags by right-clicking content in the document **Set language**: File > Properties > Advanced > Reading Options > Language — set to the document's primary language.

1. 1Open the PDF in Adobe Acrobat Pro.
2. 2Go to Tools > Accessibility > Autotag Document.
3. 3Review the auto-tagging result by opening the Tags panel: View > Show/Hide > Navigation Panes > Tags.
4. 4Use Tools > Accessibility > Reading Order to verify and fix reading sequence.
5. 5Add alt text to all images: in the Tags panel, right-click Figure tags > Properties > Tag > Alternative Text.
6. 6Run Full Check again and address all remaining failures and warnings.

Rather than restoring tags after they're stripped, the better approach is to use tag-preserving methods for common editing operations. **Merging tagged PDFs**: - Use Adobe Acrobat Pro's Combine Files (Tools > Combine Files) — it makes a best effort to merge structure trees - Inspect the merged result and repair any tag issues manually - For merging tagged PDFs programmatically, PDFBox (Java) and pdfcpu (Go) have some tag-merging capability **Splitting tagged PDFs**: - Adobe Acrobat Pro's Organize Pages > Extract Pages preserves tags for extracted pages - For splits using other tools, plan to re-tag the split sections in Acrobat afterward **Compressing while preserving tags**: - Ghostscript can preserve tags with the right settings: add `-dPreserveStructure` to the command - Note: Ghostscript's tag preservation is not perfect and should be verified after compression - Adobe Acrobat's Save As Other > Optimized PDF option compresses while preserving accessibility better than Ghostscript **When using LazyPDF operations**: - Compress, merge, and split operations may strip accessibility tags (as is common with most browser-based tools) - For PDF workflows requiring accessibility compliance, use Acrobat Pro for tag-sensitive operations - Use LazyPDF for operations where the document isn't required to be tagged (non-public documents, internal workflow PDFs)

1. 1For merging: use Adobe Acrobat Pro's Combine Files instead of browser-based tools.
2. 2For splitting: use Acrobat Pro's Organize Pages > Extract Pages.
3. 3For compressing: use Acrobat Pro's Save As Other > Optimized PDF instead of Ghostscript-based tools.
4. 4After any editing, always run Acrobat's Accessibility Checker (Tools > Accessibility > Full Check).
5. 5Before distributing any public-facing PDF, verify it passes accessibility check with zero critical failures.
6. 6Consider using PAC (PDF Accessibility Checker) for more thorough PDF/UA compliance verification.

Long-term, the most efficient approach is to create PDFs in ways that make accessibility easier to maintain through editing. **Maintain source documents**: Keep the original Word, InDesign, or HTML source files with proper heading styles and accessibility features. Whenever a PDF needs updating, regenerate it from the source rather than editing the PDF directly. Regenerating from a well-structured source consistently produces well-tagged PDFs. **Use Acrobat Pro for all PDF editing**: If PDFs must be edited at the PDF level, do all editing in Acrobat Pro, which attempts to maintain accessibility throughout. **Separate content from accessibility work**: In some workflows, the practical approach is to create the PDF content using standard tools, then apply full accessibility remediation as a final step using Acrobat Pro, just before distribution. This way, editing never touches the accessibility layer — accessibility is always applied last. **Document your accessibility additions**: Keep a record of what alt text you added, what heading structure you created, and what accessibility issues you fixed. When the PDF needs to be re-edited, this record helps you re-apply the same accessibility work efficiently. **Consider HTML as the primary accessible format**: For web-facing content, maintaining an HTML version is often more maintainable for accessibility than a PDF. HTML5 with semantic markup is natively accessible and survives editing without losing structural information.