Path Object not tagged | PDF / UA

Welcome to the world of document accessibility! Today, we’ll demystify a common issue that plagues many users – the ‘Path Object Not Tagged’ error – especially when working with Adobe Acrobat and files exported from InDesign.

Video Overview

Understanding the ‘Path Object Not Tagged’ Error

This error is frequently reported by the PAC 2021 checker, a tool that checks the accessibility of PDF files. During a check, you might come across a list of issues under the WCAG (Web Content Accessibility Guidelines) criteria. One of these is likely the ‘Path Object Not Tagged’ error.

So, what’s happening here? In this context, path objects typically refer to specific lines within a table exported from InDesign. They are recognized as objects that require tagging, but this process can be quite cumbersome and, unfortunately, it often gets overlooked, resulting in the aforementioned error.

Tackling the Issue Head-On

To address this issue, let’s look at a step-by-step process using an example document exported from InDesign and now open in Adobe Acrobat:

1. Open the ‘Content’ panel located on the far left side of Adobe Acrobat. This allows you to review all the content present on each page.
2. As you inspect each page, you’ll likely notice a plethora of ‘Path’ tags.
3. Begin by selecting all these ‘Path’ tags.
4. With the path objects selected, right-click and choose ‘Create Artifacts’.
5. Confirm by selecting ‘OK’.

Checking the Results and Final Thoughts

Having made these changes, save and close your file. On retesting with the PAC 2021 checker, you’ll notice the previous ‘Path Object Not Tagged’ errors are now resolved, and any new issues can be addressed separately.

The ‘Path Object Not Tagged’ error often crops up when exporting files from InDesign or other similar software. Remember, it’s crucial to ‘artifact’ these paths to make your document as accessible as possible. It’s not just about fixing an error – it’s about making your content reachable and usable for everyone.