01-006 The structure type and attributes of a structure element are not semantically appropriate for the structure element. All of the following structure types must be taken into account: <Document>, <Part>, <Art>, <Sect>, <Div>, <BlockQuote>, <Caption>, <TOC>, <TOCI>, <Index>, <NonStruct>, <Private>, <P>, <H>, <H1>, <H2>, <H3>, <H4>, <H5>, <H6>, <L>, <LI>, <Lbl>, <LBody>, <Table>, <TR>, <TH>, <TD>, <THead>, <TBody, <TFoot, <Span>, <Quote>, <Note>, <Reference>, <BibEntry>, <Code>, <Link>, <Annot>, <Ruby>, <Warichu>, <RB>, <RT>, <RP>, <WT>, <WP>, <Figure>, <Formula>, <Form>.

A structure element's type or attributes do not suit what it holds.

Checkpoint

01: Real content tagged

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

7.1-2

Test type in the protocol

Needs a human judgement

Applies to

A single object

Notes in the protocol

NOTE 1: Structure type is not semantically appropriate if the nature of the content inside the structure element does not match the structure type of the structure element. NOTE 2: For any non-standard structure types, the standard structure type to which the type is role-mapped shall be used for validation. NOTE 3: Tables are regular when the number of logical cells is equal in each row after accounting for RowSpan and ColSpan attributes. While PDF/UA-1 does not prohibit irregular tables, irregular tables are almost always a strong indicator of improper table structure. It may be a good idea to raise a warning when such tables are encountered, but it is not required by the Matterhorn Protocol. NOTE 4: The value of table cell attributes is a function of the cell’s semantic role in the table’s structure. Therefore, a <TH> cell may not include a Scope attribute with an inappropriate value.

How AxisRemedy handles it

Left for you. A person has to judge this one. AxisRemedy does not test it; the report lists it as left for you.