PDF/UA-1 · CLAUSE 7.1
Custom tag types are not mapped correctly
The document uses non-standard structure types that are not mapped to standard PDF types, map in a circle, or remap standard types to something else.
Why it matters
Assistive technology cannot interpret unknown tag names. A custom tag such as 'BodyText' means nothing unless it maps to P.
How to fix it
- Edit the role map in the structure tree root so every custom type resolves to a standard type such as P, H1, Table, or L.
- Remove any mapping that redefines a standard type (for example mapping H1 to P).
- Prefer standard tags in the authoring tool so the role map stays small.
What the standard says
All non-standard structure types shall be mapped to the nearest functionally equivalent standard type, as defined in ISO 32000-1:2008, 14.8.4, in the role map dictionary of the structure tree root. This mapping may be indirect; within the role map a non-standard type can map directly to another non-standard type, but eventually the mapping shall terminate at a standard type
Check your own PDF
Validate a file against PDF/UA-1 and see whether this rule fails in your document.
curl -sS -X POST "https://api.ua1.dev/api/validate?format=compact&profile=ua1" \ -F "file=@document.pdf"