THead
| Description | Defines the header section of a table, containing cells that label the columns or rows and provide context for the table data. |
|---|---|
| Namespace | 1.7 2.0 |
| Category | block |
Attributes
Specifies how the element is placed relative to surrounding content (e.g., block-level or inline flow).
Defines the direction of text flow (e.g., left-to-right, right-to-left, or vertical).
Sets the background color for the element’s content area.
Specifies the color of the border around the element.
Indicates the style of the border (e.g., solid, dashed, dotted).
Defines the thickness of the border line in user space units (such as points).
Determines the space between the element’s border (or boundary) and its inner content.
Applies the primary color (fill or stroke) for the text or graphic content.
Declares an explicit width for the element in user space units.
Declares an explicit height for the element in user space units.
Main indicator of type. This semantic association allows tools to present and support interaction with the object in a manner that is consistent with user expectations about other objects of that type.
Differences
Well tagged PDF:
The 'THead' element in Well-Tagged PDF is used to group header rows in a table, providing a clear separation from the table body.
It should enclose all header rows and be distinctly separated from the body ('TBody') and footer ('TFoot') sections to preserve table semantics.
PDFUA:
In PDF/UA, the 'THead' element enhances accessibility by clearly delineating the header section of a table, which is essential for establishing context.
The header group must be tagged and associated with corresponding data cells, ensuring that assistive technologies can reliably convey the table's structure.
Use cases
Complex table with two rows in header, two rows in the body and one row in the table footer
Try itTag Relationships
Permitted Parent Tags
Permitted Child Tags
Click on any tag to view its details.
Related Matterhorn Protocol checkpoints
- Tags are not in logical reading order.
- Structure elements are nested in a semantically inappropriate manner. (e.g. a table inside a heading).
- The structure type (after applying any role-mapping as necessary) of a structure element is not semantically appropriate.
- A table-related structure element is used in a way that does not conform to the syntax defined in ISO 32000-1, Table 337.