Form
| Description | Encapsulates interactive form elements, allowing for user input and data collection within the PDF. |
|---|---|
| Namespace | 1.7 2.0 |
| Category | grouping block 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.
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 'Form' element in Well-Tagged PDF represents interactive form fields and related objects, grouping them into a cohesive structure.
Form elements should be properly grouped and associated with corresponding labels and actions. They must be accurately reflected in the structure tree to support interactivity and content reuse.
PDFUA:
In PDF/UA, the 'Form' element is crucial for accessibility in interactive documents, ensuring that form controls are identifiable and operable by assistive technologies.
All form fields must be tagged with clear labels and interactive actions defined, with additional metadata provided where necessary to guide users with disabilities.
Use cases
Edit form field with label
Try itNon interactive form field represented with text
Try itTag Relationships
Permitted Parent 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.
- Non-interactive forms are not tagged with the PrintFields attribute.
- A form field whose hidden flag is not set and whose rectangle is not outside the crop-box and does not have a TU key does not have an alternative description (in the form of an Alt entry in the enclosing structure element).
- A widget annotation is not nested within a Form tag.