Tagged Form XObjects must be referenced once

PDF/UA check FORM_XOBJECT_MCID_MULTIREF · Structure & other · severity High · PDF/UA 8.12 XObjects · advanced check

↩ Back to the rules index · WCAG cross-reference

Advanced check. This is a file-internals rule. It is hidden from the standard report view and generally indicates a problem with the tool that produced the PDF rather than something an author did.

Why it matters#

If a Form XObject containing MCIDs is referenced multiple times, the structural parent tree becomes ambiguous and screen readers cannot reliably resolve the tagged content.

What you will see#

A Form XObject containing tagged content is drawn more than once, making its structural parent ambiguous.

How to fix#

Ensure each Form XObject that contains marked content (MCIDs) is painted with the Do operator only once in the document. For repeated placements, create a separate copy of the XObject with its own MCIDs, or move the tagged content into the page content stream.

Step-by-step guide#

1. Identify the Form XObjects that contain marked-content MCIDs and are referenced from the XObject resources of more than one page (the EQChecker report gives the offender count; forms without MCIDs are never flagged, and EQChecker detects reuse across pages rather than counting individual Do operators).
2. Decide what the reused form actually is: repeated decoration (running header, footer, logo, letterhead) or repeated real content.
3. If it is decoration, remove the MCIDs and any structure elements pointing into the form, and mark its content as an Artifact. An artifact-only form may be reused on every page - that is the normal conformant pattern.
4. If it is real content that genuinely appears multiple times, create a separate copy of the Form XObject for each placement, each with its own MCIDs resolved through the structural parent tree, or move the tagged content out of the XObject and into each page content stream.
5. Acrobat cannot restructure XObject streams or their marked content - the file was assembled incorrectly by its producing pipeline (this pattern usually comes from imposition or merge steps rather than authoring applications), and the only reliable fix is regenerating the document from its source with a compliant export pipeline.

Verify: Re-run the EQChecker scan in advanced mode and confirm FORM_XOBJECT_MCID_MULTIREF passes with zero offenders.

Note: The structural parent tree maps each MCID within a content stream to exactly one structure element, so a multiply-painted form with MCIDs makes tag resolution ambiguous (ISO 32000-2 marked-content rules) - screen readers cannot tell which placement a tag refers to. Reusing forms that contain no MCIDs is fully conformant and is not flagged.

WCAG success criteria#

1.3.1 Info and Relationships — Level A#

Structure and relationships conveyed visually (headings, lists, tables, labels, groups) must also be available programmatically.

Understanding 1.3.1

Standards#

This check contributes to the following standards:

PDF/UA WCAG A EN 301 549