Popup annotations must stay out of the tag tree

PDF/UA check POPUP_IN_STRUCTURE · Annotations · severity Medium · PDF/UA 8.9.2.4.9 Popup annotations

↩ Back to the rules index · WCAG cross-reference

Why it matters#

Popup annotations have no semantic meaning and should not appear in the document structure. Their presence in the structure tree adds unnecessary noise for screen reader users.

What you will see#

Popup annotations have been placed in the structure tree, where they add noise with no meaning.

How to fix#

Remove the Popup annotation's object reference (OBJR) from the structure tree. Keep the popup on the page and referenced from its parent markup annotation's /Popup entry; only the parent markup annotation belongs in the structure tree.

Step-by-step guide#

1. Open the Accessibility tags panel (View > Show/Hide > Side panels > Accessibility tags), choose Options > Find, set the search to Annotations, and step through until the Popup annotation reported by EQChecker is highlighted on the page.
2. Delete only the tag-tree entry: right-click the OBJR node referencing the Popup annotation and delete it, along with its wrapping structure element if that wrapper contains nothing else.
3. If the check still fails after removing the tag, the Popup dictionary retains a stale StructParent entry that Acrobat does not delete; EQChecker keys off that entry. Acrobat cannot remove the key, so clear it by regenerating the file from a source export that does not tag Popup annotations in the structure tree.
4. Do not delete the Popup annotation from the page itself - it must stay referenced from the parent markup annotation's Popup entry so sighted users keep the popup note behaviour.
5. Confirm the parent markup annotation is still tagged in an Annot element (MARKUP_ANNOT_TAGGED) and carries its note text in the Contents entry - that is where assistive technology reads it.

Verify: Re-run the EQChecker scan; POPUP_IN_STRUCTURE should report zero errors.

Note: Popup annotations define no semantics of their own; they exist solely in the context of their parent markup annotation (8.9.2.4.9 NOTE), so removing them from the structure tree loses nothing for AT users. The prohibition is PDF/UA-2 specific - PDF/UA-1 merely exempts popups from tagging requirements, and EQChecker applies this check only when scanning against UA-2.

WCAG success criteria#

No WCAG success criterion maps cleanly to this check — it is a PDF/UA structural requirement. The PDF/UA clause above is the normative reference.

Standards#

This check contributes to the following standards:

PDF/UA