Note
| Description | Contains supplementary or explanatory information such as footnotes or endnotes, adding context to the main content. |
|---|---|
| Namespace | 1.7 |
| Category | inline |
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.
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 'Note' element in Well-Tagged PDF is used for annotations or side comments that provide additional information about the main text.
Notes should be clearly connected to the relevant content and properly nested within the structure tree, enabling them to be excluded from the primary reading order if required.
PDFUA:
In PDF/UA, the 'Note' element is crucial for making supplementary commentary accessible, ensuring that extra information is available to users through assistive technologies.
Each note must include alternative text or descriptive metadata to explain its purpose, and be clearly associated with the related content within the structure tree.
Use cases
Example of a footnote tagged inline within a paragraph in compliance with PDF/UA-1
Try itExample of an endnote tagged after a paragraph in compliance with PDF/UA-1
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.
- Footnotes, endnotes, note labels are not tagged as Note.
- ID key of the Note tag is not present.
- ID key of the Note tag is non-unique.