Table
| Description | Represents a table structure that organizes content into rows and columns, facilitating tabular presentation. |
|---|---|
| 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 'Table' element in Well-Tagged PDF is used to represent tabular data as a cohesive unit. It organizes rows, columns, and cells to support content extraction and reflow for reuse.
It must encapsulate table components (such as rows and cells) within a clearly defined structure tree. Row and column definitions should be explicit to maintain logical reading order.
PDFUA:
In PDF/UA, the 'Table' element ensures that tabular data is accessible and navigable by assistive technologies. It plays a critical role in conveying the relationships between cells.
The table must be tagged with clear associations between header and data cells, and any table summary or caption must be provided to support user navigation.
Use cases
Simple table
Try itComplex table with two rows in header, two rows in the body and one row in the table footer
Try itTag Relationships
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.
- Content is tagged as a table for information that is not organized in rows and columns.