Form widgets belong inside a Form element

PDF/UA check WIDGET_PARENT_FORM · Forms · severity High · PDF/UA 8.10.1 General

↩ Back to the rules index · WCAG cross-reference

Why it matters#

Form fields need a Form structure parent so screen readers can announce them as form controls in the correct location.

What you will see#

A widget annotation is tagged, but not under a Form structure element.

How to fix#

Enclose the widget annotation's OBJR in its own Form structure element, with at most one widget per Form element. If the widget is invisible or used only for calculations, mark it as an artifact instead.

Step-by-step guide#

1. Open the Accessibility tags panel and choose Options > Find > Unmarked annotations to locate widget annotations that have no object reference (OBJR) in the structure tree; tag each one so an OBJR is created.
2. For each flagged widget whose OBJR sits under a non-Form parent (e.g. P, Sect, Div), create a new Form tag (Options > New tag, type Form) at the position in the tree matching the field's place in the reading order.
3. Drag the widget's OBJR into the new Form element, and remove the empty or wrong-typed old wrapper if any remains.
4. Ensure each Form structure element encloses at most one widget annotation (ISO 14289-2 section 8.10.1). If several OBJRs share one Form element, split them into one Form element per widget.
5. If the widget is invisible or used exclusively for calculations, do not tag it as Form at all: mark it as an artifact instead, per the section 8.10.1 example.
6. Position each Form element next to the content the field relates to, so its label and surrounding text provide context (section 8.10.2.1).

Verify: Re-run the EQChecker scan: WIDGET_PARENT_FORM should report zero errors.

Note: A Form structure element represents a single widget, not a whole field: one radio-button field with five widgets needs five Form elements (section 8.10.1 note).

WCAG success criteria#

4.1.2 Name, Role, Value — Level A#

Every UI component must expose a correct name, role, and (where relevant) state/value to assistive technology.

Understanding 4.1.2

Standards#

This check contributes to the following standards:

PDF/UA WCAG A EN 301 549