TFoot
| Description | Represents the footer section of a table, grouping together table rows that contain summary information, totals, or additional annotations related to the table's content. |
|---|---|
| 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 'TFoot' element in Well-Tagged PDF is used to group footer rows in a table, often containing summary or total information.
Footer rows must be distinctly enclosed within a 'TFoot' element and properly linked to the rest of the table structure.
PDFUA:
In PDF/UA, the 'TFoot' element aids accessibility by clearly marking the footer portion of a table, which may contain important summary data.
It should be tagged with clear associations and, if applicable, include alternative descriptions to assist users in navigating table summaries.
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.