Enum StructureRole
The semantic role of a StructureMark, named after the PDF standard structure type it maps to.
public enum StructureRole : byte
Fields
Document = 0The document root (
/Document).Section = 1A section (
/Sect).Paragraph = 2A paragraph (
/P).Heading1 = 3A level 1 heading (
/H1). Levels 2-6 follow consecutively.Heading2 = 4A level 2 heading (
/H2).Heading3 = 5A level 3 heading (
/H3).Heading4 = 6A level 4 heading (
/H4).Heading5 = 7A level 5 heading (
/H5).Heading6 = 8A level 6 heading (
/H6).List = 9A list (
/L).ListItem = 10A list item (
/LI).ListLabel = 11A list item's label (
/Lbl) — the bullet or number.ListBody = 12A list item's body (
/LBody).Table = 13A table (
/Table).TableRow = 14A table row (
/TR).TableHeaderCell = 15A table header cell (
/TH).TableCell = 16A table data cell (
/TD).Figure = 17An illustration (
/Figure).Caption = 18A caption (
/Caption).Artifact = 19Content that carries no meaning and must be hidden from assistive technology (page furniture, decorative rules). Emitted as an artifact, not a structure element.
Link = 20A hyperlink (PDF
Link), holding the link's text and an OBJR to its annotation. PDF/UA 7.18.5 requires both: an annotation a reader can activate but no element describing it is a link only a sighted user knows is there.
Remarks
The roles are deliberately the ones a Word document can actually justify from its own model. A role that would have to be guessed from page geometry is not here: inventing structure is worse than omitting it, because a screen reader trusts what it is told.