Form field has no label

Why does it matter?

Without a label, a screen reader announces only "edit text", and voice-control users have no name to say. A placeholder is not a label: it disappears as soon as someone types, and many screen readers do not announce it.

Who it affects: Screen reader users, voice-control users who say a field's label to move to it, and people with memory or attention difficulties who lose a placeholder once they type.

51.0% of the top million home pages had form fields without labels in 2026. WebAIM Million 2026

What does Lumtera flag?

Inputs, selects and textareas with no associated <label>, aria-label or aria-labelledby. Fields that rely on a placeholder alone are called out specifically.

Check ID form-field-no-label — use it to filter the content report or with wp lumtera issues --rule.

How do I fix it in WordPress?

Add a visible <label> tied to the field with for="field-id", or wrap the field inside its label. In form-builder plugins, turn on the field's label (you can style it smaller, but keep it). A placeholder is not a label.

Example

<input type="email" placeholder="Email address">

<label for="email">Email address</label>
<input type="email" id="email">

How do I check the fix?

1. Update the post. The issue disappears from the Lumtera Accessibility sidebar on the next check, and from the site report on the next scan.
2. Click each field's label: the cursor should move into the field. With a screen reader, each field should announce its label when it receives focus.