Visible form labels need an Lbl element

PDF/UA check FORM_LBL_STRUCTURE · Forms · severity High · PDF/UA 8.10.2.2 Form field labelling

↩ Back to the rules index · WCAG cross-reference

Why it matters#

A visible label sitting next to a form field is invisible to screen readers unless it's wrapped in an Lbl structure element. Users hear 'edit field' with no clue what to enter.

What you will see#

Text acting as a form label sits loose in the page instead of inside an Lbl element under the Form.

How to fix#

Wrap the visible label text in an Lbl structure element placed as a direct child of the Form element that also contains the widget's OBJR. For a label that covers a group of fields, place the Lbl inside the parent element that contains all of the group's Form elements.

Step-by-step guide#

1. Identify the visible text that labels the flagged field (e.g. the words First name: printed beside a text box).
2. In the Accessibility tags panel, locate the Form element containing the widget's OBJR and create a new Lbl tag as its direct child (Options > New tag; type Lbl if it is not in the list).
3. Move the label's text content into the Lbl element: expand the tag currently holding the label text and drag its marked-content item into the Lbl. Per ISO 14289-2 section 8.10.2.2 the Lbl must be a direct descendant of the same Form element that holds the widget's OBJR.
4. For a label that covers a group of fields (e.g. a question above several radio buttons), wrap it in an Lbl placed inside the parent structure element that directly or indirectly contains all of the group's Form elements.
5. Alternative path: if no usable visible label exists, the check also passes when the widget carries context another way - set the field's TU entry (All tools > Prepare a form > field Properties > General > Tooltip); a widget Contents entry (section 8.10.2.3) also satisfies the check, but Acrobat has no UI for it, so use the Tooltip path.
6. Check the resulting reading order: the Lbl should be read immediately with its field.

Verify: Re-run the EQChecker scan: FORM_LBL_STRUCTURE should report zero errors. A screen reader should announce the label text together with the field.

Note: Artifact content can label real content; in that case an Lbl element is not appropriate (section 8.2.5.16 note) and the TU/Contents path should be used. A Contents entry should not be identical to the visible label, since an identical entry adds no information (section 8.10.2.3).

WCAG success criteria#

1.3.1 Info and Relationships — Level A#

Structure and relationships conveyed visually (headings, lists, tables, labels, groups) must also be available programmatically.

Understanding 1.3.1

3.3.2 Labels or Instructions — Level A#

Inputs need labels or instructions so users know what to enter.

Understanding 3.3.2

Standards#

This check contributes to the following standards:

PDF/UA WCAG A EN 301 549