How to fix: “Form elements must have labels”
Form fields with no label, explained in plain English, with the exact fix and code you can copy.
- Scanner rule:
label- Standard:
- WCAG 1.3.1 Info and Relationships (Level A), WCAG 3.3.2 Labels or Instructions (Level A), WCAG 4.1.2 Name, Role, Value (Level A)
What this error means
Every text box, dropdown, checkbox and radio button must be connected to a label that says what to enter. The connection matters as much as the words. If the label is only placed visually next to the field, assistive technology cannot tell which label belongs to which field, so the person lands on a blank box with no instructions.
Missing form input labels were found on 51% of home pages in the WebAIM Million 2026 report. Source: WebAIM Million
Who it affects
Screen reader users, voice-control users (who say the label to jump to a field), people with cognitive disabilities who need clear instructions, and anyone using a small screen where placeholder text disappears as soon as they start typing.
Where it usually hides
- Contact and appointment-request forms that use placeholder text instead of labels
- Newsletter sign-up boxes in the footer
- Search boxes with only a magnifying-glass icon
- Checkout fields and discount-code boxes
- Dropdowns (select menus) with no label
How to fix it
- Give every field a visible <label>, and connect it with matching for and id values.
- Alternatively, wrap the input inside the label element, which connects them automatically.
- If the design truly has no room for a visible label (a search box, for example), add an aria-label that names the field.
- Keep placeholder text for examples only, such as 'name@example.com'. Never use it as the only label.
- If you want to hide a label visually, use a visually-hidden CSS class. display:none and visibility:hidden remove it for screen readers too.
Before and after
Before
<input type="email" placeholder="Email address">The placeholder disappears when typing and is not reliably announced as a name.
After
<label for="email">Email address</label>
<input type="email" id="email" name="email" autocomplete="email">The for/id pair connects the label to the field. autocomplete helps people fill it in faster.
On your website platform
Form plugins and builders
Contact Form 7, WPForms, Gravity Forms, Shopify forms and most form builders have a setting for label visibility. Make sure labels are turned on, or set to 'screen reader only' rather than removed.
Common mistakes
- Relying on placeholder text as the label.
- Two labels pointing at the same field, which causes confusing announcements.
- Hiding labels with display:none.
- Putting the label text in a div or span next to the field without connecting it.
How to check your fix
- Re-run a scan and confirm the label errors have gone.
- Click a label with your mouse. The cursor should jump into its field. If it does not, the label is not connected.
- In Chrome DevTools, open the Accessibility tab, select the field and check that the Name matches the label text.
Is this on your site?
Run a free scan and see every page and element affected. No account needed.
Questions people ask
Is placeholder text a valid label?
No. It vanishes when the user types, often has low contrast, and is not announced consistently. Use a real label, and keep the placeholder for an example.
How do I label a search box with only an icon?
Add aria-label="Search" to the input, and give the search button an aria-label too, or visible text.
What about dropdown menus?
A <select> needs a label in exactly the same way as a text box. Axe reports it separately as 'select-name', and the fix is the same.
Keep reading
- Buttons with no label: Buttons must have discernible text
- Low-contrast text: Elements must meet minimum color contrast ratio thresholds
- Links with no text: Links must have discernible text
- The accessibility mistakes we see on almost every small business site
Automated scans catch only part of what WCAG covers, and fixing a scan result is not a legal guarantee of compliance. Last reviewed November 16, 2026.