Standard tags must not be re-mapped

PDF/UA check STANDARD_TYPE_REMAPPED · Structure & other · severity High · PDF/UA 8.2.4 Structure types · 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#

Remapping standard tags (e.g. P → MyParagraph) breaks predictable assistive technology behavior.

What you will see#

A standard structure type has been role-mapped to a different type in the same namespace.

How to fix#

Remove the RoleMap entry that maps the standard structure type to another type. If the elements were meant to carry different semantics, retag them directly with the intended standard type instead of remapping.

Step-by-step guide#

1. Open the role map: Accessibility tags panel > Options menu > Edit Role Map, and find entries whose source key is a standard structure type (e.g. P, H1, Table).
2. Delete each such entry - ISO 14289-2 8.2.4 says structure types shall not be role-mapped to other types within the same namespace.
3. If the remap was meant to change the semantics of particular elements (e.g. P elements that are really headings), retag those elements directly instead via Tags panel > Properties > Type or the Reading Order tool.
4. Re-check the role map afterwards for broken chains: a custom type may have mapped through the entry you removed - repoint such chains straight at the intended standard type.
5. If the offending mapping lives in a namespace role map (RoleMapNS, PDF 2.0), Acrobat cannot edit it; the namespace role map was generated incorrectly by the producing application, and the only reliable fix is regenerating the file from its source with a compliant export pipeline.

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

Note: Only same-namespace remapping is prohibited: cross-namespace aliases (e.g. a PDF 2.0 type mapped to a PDF 1.7 type for backward compatibility) are allowed, and EQChecker flags only same-namespace remaps plus standard-to-custom downgrades. Pitfall: some tools add role map entries automatically when tags are renamed - audit the role map after any bulk retagging.

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