Table-of-contents entries need a target

PDF/UA check TOCI_REF_ENTRY · Structure & other · severity Medium · PDF/UA 8.2.5.8 Table of contents · 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#

Without Ref entries, table-of-contents items don't navigate to their targets via assistive technology. Users see a list of titles with no way to jump to them.

What you will see#

TOCI elements have no Ref entry, so contents entries do not resolve to the sections they name.

How to fix#

Add a Ref entry to each TOCI structure element pointing to the structure element of the section it lists. The Ref may instead be placed on a child element within the TOCI, such as a Reference element.

Step-by-step guide#

1. List the flagged TOCI elements from the EQChecker advanced report; per ISO 14289-2 8.2.5.8 each TOCI shall identify its target with a Ref entry, either on the TOCI itself or on a child structure element such as a Reference element - both placements pass.
2. For each TOCI, identify the structure element of the section it lists, typically the Sect or the heading element that opens that section.
3. Write the Ref entry - an array of indirect references to the target structure element(s) - into the TOCI's structure element dictionary, or onto a Reference child inside the TOCI. Acrobat has no UI for Ref entries, so in practice the entries must come from regenerating the table of contents at source (final step).
4. Leave the existing Link tags and link annotations inside each TOCI intact: Ref complements navigation metadata, it does not replace the interactive link.
5. Where feasible, regenerate the table of contents from source with a PDF/UA-2-aware exporter, which emits Ref entries automatically.

Verify: Re-run the EQChecker scan in advanced mode: TOCI_REF_ENTRY should pass.

Note: While editing the TOC, check the related 8.2.5.8 duties: dot leaders between an entry and its page number shall be identified as artifacts, and an Artifact structure element used for leaders must sit at the logically correct place in the tree.

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