Elgarde
Violations

Form input missing label

critical Accessibility WCAG 1.3.1 WCAG 4.1.2

How common

Very common, especially in custom-styled forms. Found on approximately 40% of websites.

What this means

A form input (text field, dropdown, checkbox, etc.) is not associated with a visible label. Screen reader users cannot determine what information the field expects.

WCAG requirement

  • 1.3.1 — Info and Relationships: information and relationships conveyed visually must be programmatically determinable
  • 4.1.2 — Name, Role, Value: all user interface components must have an accessible name

Common causes

  • Using placeholder text instead of a <label> element
  • A visible label exists but is not connected to the input (missing for attribute)
  • Custom-styled inputs that replace native <input> elements without proper ARIA

How to fix

  1. Use <label> elements: <label for="email">Email address</label><input id="email" type="email">
  2. Don’t rely on placeholder: placeholders disappear when the user starts typing and are not a substitute for labels
  3. For visually hidden labels: use a CSS class that hides the label visually but keeps it available to screen readers
  4. Group related fields: use <fieldset> and <legend> for groups of checkboxes or radio buttons

Check your website for this violation

Free scan — no registration required. Results in 30 seconds.

Scan now