02-001 One or more non-standard tag’s mapping does not terminate with a standard type.

A custom structure type's role mapping does not end at a standard type.

Checkpoint

02: Role Mapping

ISO 14289-1 (PDF/UA-1) clause

7.1-3

Test type in the protocol

Machine-testable

Applies to

Whole document

WCAG 2.x (AxisRemedy's informative mapping)

1.3.1 Info and Relationships (level A)

Notes in the protocol

NOTE: Although PDF/UA defines the nomenclature for heading levels above <H6> (<Hn>), these are not standard structure types (as defined in ISO 32000-1) and therefore <Hn> tags must (PDF/UA-1 7.1, paragraph 1) be role-mapped to a standard structure type. According to PDF/UA-1, PDF/UA-conforming processors are expected to ignore such mappings and respect the heading level.

How AxisRemedy handles it

Tested by the app. AxisRemedy tests this condition itself. For each document it records passed, failed or not applicable, and for every failure the object and the page.

What the check covers

Checks every structure type used in the tree and every /RoleMap entry. Names added in PDF 2.0 count as non-standard, because PDF/UA-1 is a PDF 1.7 standard.

Repairs that target it

• Custom structure types mapped to a standard type in the role map

Repairs are optional. The few that could change how a page looks, such as embedding a missing font, need your explicit consent.