The Acquia Web Governance PDF accessibility scan may throw a tag error. This document explains the error and gives some troubleshooting solutions.

"Document is not tagged" error¶

Tagged PDF files have an underlying tag tree that defines the structure of the document. Use PDF tags to identify content as headings, lists, tables, and so on, and to add alt-text to your images. PDF files that are not tagged are not accessible.

Usually, you create tagged PDFs from within an authoring application, such as Adobe FrameMaker®, Adobe InDesign, or Microsoft Word. This method allows tags to be added more effectively than with Acrobat.

PDFMaker provides conversion settings that let you create tagged PDFs in Microsoft Excel, PowerPoint, and Word.

Solution¶

This section provides instructions for the following ways to put tags on PDF files:

• Autotagging

• Reading order tool

Use Autotagging¶

To add tags to an untagged document with Adobe Acrobat Pro DC:

1. Open the Accessibility Panel on the Tools tab.

2. Select Autotag Document.

3. Inspect the tag tree:

   • In the View menu, select Show/Hide > Navigation Panes > Tags. The tags are displayed in descending order.

   • Review the tag tree to make sure that it has proper semantic structure and reading order. Tags may be modified manually, but when you make changes to the tag tree it can become unpredictable.

   • Remember to save often.

Use the Reading Order tool¶

Use the Reading Order tool during the manual tagging or remediation process. For more information, visit Reading Order tool for PDFs. To add tags with the Reading Order Tool:

1. Select the Reading Order tool.

2. Select the heading text in the PDF.

3. In the Reading Order dialog, select the button for the appropriate heading tag (for example, Heading 1, Heading 2, and so on).

Additional resources¶

For more information, visit:

• Tagging an existing PDF in Adobe Acrobat Pro DC

• www.adobe.com/accessibility

• Documentation for your authoring application