Fix guide · Form fields without labels

How to fix “Form elements must have labels”

By · Updated

A text box on the page has no label tied to it, so a screen reader can't say what to type. Give each field a visible label element connected to it with for and id.

axe rule
label
WCAG
4.1.2 Name, Role, Value (Level A)
Lighthouse
Google Lighthouse and PageSpeed Insights report it as “Form elements do not have associated labels”

What it means

Sighted visitors work out a field from the words near it. A screen reader can only say what's connected to the field in code. With no label, a visitor hears "edit text, blank" and has to guess whether it wants a name, a phone number or a case number.

The WebAIM Million found missing form labels on 51% of home pages in 2026, and 33.1% of all form inputs it checked weren't properly labeled.

Watch for one catch. axe counts placeholder text as a name, so a field with only a placeholder may pass this rule. W3C points out that placeholder text usually has low contrast and disappears once someone starts typing, so it's a poor stand in for a label.

Who it affects

People who use a screen reader, people with memory or attention difficulties who lose track once a placeholder vanishes, and voice control users.

How to find it

  1. Run the free checker. It lists each unlabeled field with its name attribute, like name="city".
  2. Check search boxes, newsletter sign ups and contact forms. Search boxes in headers are a common miss.
  3. Click on a field's label. If the cursor doesn't jump into the field, the two aren't connected.

How to fix it

  1. Add a label element with the field's name, and match its for attribute to the field's id.
  2. Keep the label visible. If the design truly can't show it, as with a single search box next to a Search button, an aria-label on the field is acceptable.
  3. Use placeholder text only for an example of the format, like MM/YYYY, never as the only name.

A field with no label

Before · fails
<input type="text" name="city">
After · fixed
<label for="city">City</label>
<input type="text" name="city" id="city">

A placeholder doing a label's job

Before · fails
<input type="email" placeholder="Email address">
After · fixed
<label for="email">Email address</label>
<input type="email" id="email" autocomplete="email">

From a real fix

The law firm site I fixed had an intake form where a City field had no label tied to it, so a screen reader had nothing to announce. Connecting a real label element to the field fixed it.

In your website builder

Where each platform’s own help pages cover it, as of November 2026. Menus move, so follow the link if a step doesn’t match what you see.

WordPress
It depends on your form plugin. In Contact Form 7, wrap the tag in a label, like <label>Your name [text* your-name]</label>. Most other form plugins have a Label field on each field's settings. WordPress help
Squarespace
In the form block's Content tab, choose Edit Form Fields, click a field and give it a label. Squarespace help
Wix
Edit the form, select the field, open Settings and fill in Field title, then use Show field title so it's visible. Wix notes its older forms aren't accessible. Wix help
Webflow
Give the input an ID in its settings, then select its Field Label and add a custom attribute named for with that same ID. Webflow help

What a scanner can and can’t tell you

Fixing this clears one automated check. It doesn’t mean the page is accessible, and it doesn’t settle any legal question. Automated tests catch only part of the problems. W3C puts it plainly: evaluation tools “can not determine accessibility, they can only assist in doing so.” The rest takes a person working through the site with a keyboard and a screen reader.

Source: W3C WAI, Selecting Web Accessibility Evaluation Tools. Not legal advice.

Sources

All checked November 8, 2026. The rule wording is axe-core 4.14.0’s own.

Related fixes

Every fix guide →

Check a page for free

Scan any page of your site against WCAG 2.1 AA in about 30 seconds. You get the problems automated testing finds, in plain words, with a link to a fix guide for the common ones.

Run the free checkno sign up · one page at a time

Rather have someone fix it for you? Tell me about your site.