How to Fix Form Fields Missing Labels for Accessibility
This check fails when an input, select or textarea has no accessible name, or when one field has more than one label element pointing at it. Screen readers then announce it only as "edit text" or "combo box". By the end of this guide, every form field on your site will have exactly one programmatic label, either a visible label linked by for and id, or an aria-label where a visible label is not practical.

Why it matters
2 Name, Role, Value. Blind and low-vision visitors cannot tell what to type, so contact, checkout and signup forms get abandoned and you lose leads and sales. Many accessibility lawsuits and demand letters cite this issue.
Labels also help sighted users, because clicking a linked label focuses its field, which gives a larger tap target on mobile. Browser autofill and password managers also identify fields more reliably when they are labeled. Google does not rank pages on this directly, but form usability affects conversions, and accessible markup gives crawlers and AI assistants clearer page structure.
What you need
Step-by-step fix
List every field that fails
Open each page that has a form and run axe DevTools (F12 > axe DevTools > Scan ALL of my page) or Lighthouse (F12 > Lighthouse > Accessibility). Note the rules that fail:
- label: an input or textarea has no accessible name
- select-name: a dropdown has no accessible name
- form-field-multiple-labels: a field has more than one label element
Also check forms that appear only after an action, such as the site-wide search, the footer newsletter box, popups and cookie banners. Open each one before you scan.
Link a visible label to each field with for and id
Give each field a unique id. Then add a label element whose for attribute matches that id exactly. The match is case-sensitive, and the id must be unique on the page.
Another option is to wrap the field inside the label element, but explicit for/id is more robust across assistive technologies. Add autocomplete values where they apply so autofill works too.
<label for="contact-email">Email address</label> <input id="contact-email" name="email" type="email" autocomplete="email" required> <label for="contact-message">How can Example Co help?</label> <textarea id="contact-message" name="message" rows="5"></textarea>
Name every select dropdown
Dropdowns fail when their only text is the first option, such as "Choose a country". The first option is not a name. Add a label exactly as you would for an input.
This matters most for country and state pickers, product variant selectors, sort-by menus and quantity dropdowns.
<label for="shipping-country">Country</label> <select id="shipping-country" name="country" autocomplete="country"> <option value="">Select a country</option> <option value="US">United States</option> </select>
Use hidden labels or aria-label for compact fields
Some fields have no room for visible text, such as a header search box next to a magnifier icon. For these, keep a real label and hide it visually with a screen-reader-only class. Alternatively, put aria-label on the field itself.
If visible text elsewhere already describes the field, point to it with aria-labelledby. Never hide a label with display:none or the hidden attribute, because that removes it from screen readers too.
<style>
.visually-hidden{position:absolute!important;width:1px;height:1px;padding:0;margin:-1px;overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap;border:0}
</style>
<label for="site-search" class="visually-hidden">Search example.com</label>
<input id="site-search" type="search" name="q">
<!-- or -->
<input type="search" name="q" aria-label="Search example.com">Remove duplicate labels on the same field
The form-field-multiple-labels rule flags a field that two label elements point to. This usually happens when a theme adds a floating label and a form plugin adds another one, or when a label wraps the input and a second label also uses for. Keep one label per field.
If you need extra text such as a hint or an error message, connect it with aria-describedby instead of a second label.
<label for="phone">Phone number</label> <input id="phone" name="phone" type="tel" autocomplete="tel" aria-describedby="phone-hint"> <p id="phone-hint">We only call about your order.</p>
Fix forms injected by apps and embeds
Newsletter popups, chat widgets, review apps and embedded CRM forms (HubSpot, Mailchimp and similar) often render unlabeled inputs.
- Check the vendor's settings first. Look for an option such as "Show field labels" or a label text field, and turn labels on.
- If no setting exists, contact the vendor or switch to their accessible embed code.
- If you have to, patch it with JavaScript. Add an aria-label after the widget loads. Treat this as a stopgap only, not a permanent fix.
document.querySelectorAll('.example-newsletter input[type="email"]:not([aria-label])').forEach(el => el.setAttribute('aria-label', 'Email address'));Re-scan and test with a screen reader
First, clear your page cache or CDN cache. Then re-run axe DevTools or Lighthouse on every form page and confirm that label, select-name and form-field-multiple-labels no longer appear. Next, tab through each form with NVDA (Windows) or VoiceOver (Cmd+F5 on macOS).
Check that every field announces a meaningful name. Finally, click each visible label and confirm the cursor jumps into its field.
Platform-specific notes
WordPress
In the block editor, the core Search block has a "Show label" toggle under Block settings. If you turn it off, the block still outputs a screen-reader label, so it passes. For form plugins: - **Gravity Forms**: set Form Settings > Field Labels > "Field Label Visibility" to Visible, or leave per-field labels filled in. Avoid emptying the label text. - **Contact Form 7**: tags don't output labels on their own. In the form template, wrap each tag, for example <label>Your email [email* your-email]</label>. - **WPForms**: if you enable "Hide Label" under a field's Advanced tab, the label is hidden only visually and still passes.
Shopify
Go to Online Store > Themes > Edit code. Online Store 2.0 themes such as Dawn already label the main fields with a field__label class and use visually-hidden labels for the search and newsletter fields. Custom themes and older themes often don't. To fix them, edit the relevant section or snippet files, such as main-search.liquid, header-search.liquid or footer.liquid, and the product form section. Add a label with for and id, using {{ section.id }} to keep ids unique. Unlabeled fields on checkout pages can only be changed through Shopify's checkout settings, not your theme. Many review apps and popup apps render their own forms, so check each app's settings for label options.
Wix
In the Wix Editor, select the form, click Edit Form, choose a field and open its settings. Make sure "Field title" (the label) is filled in. If you need a cleaner look, keep the title and shorten the text instead of deleting it, because a placeholder alone is a weak label. Wix generates the for/id link automatically, so you can't edit the raw HTML.
Webflow
In the Designer, drag a Form Label element above each field. Select the label, open Element settings (the gear icon) and set "For" to the field's ID. Then select the input and confirm its ID under Element settings. For search fields without a visible label, apply a visually-hidden combo class to the label rather than deleting it.
Next.js / React
JSX uses htmlFor instead of for, as in <label htmlFor="email">. Generate unique, SSR-safe ids with React's useId() hook, for example const id = useId(), so reused components don't create duplicate ids. Component libraries usually label fields only when you pass a label prop. In MUI that is TextField label="", and in Chakra it is FormControl with FormLabel. Search your code for inputs rendered without that prop.
Check that it worked
✅ How to verify
- axe DevTools reports zero issues for label, select-name and form-field-multiple-labels on every page that has a form.
- The Lighthouse Accessibility audit no longer lists "Form elements do not have associated labels" or "Select elements do not have associated label elements".
- In Chrome DevTools, go to Elements, select the field and open the Accessibility pane. It shows a non-empty Name that comes from a label element or aria-label.
- With NVDA or VoiceOver, tabbing into each field announces its purpose, such as "Email address, edit text, required".
⚠️ Common mistakes
- Using placeholder text as the only label. It disappears while the user types, often has poor contrast, and some assistive technologies ignore it.
- Hiding labels with display:none or visibility:hidden, which removes them from screen readers as well as the screen. Use a visually-hidden class instead.
- Copying a form block and leaving duplicate ids. The second label then points to the first field, and the copied field stays unlabeled.
- Adding a second label element for hint or error text instead of connecting that text with aria-describedby.
Is this still an issue on your site? Run a free audit — ZORO checks this and 294 other SEO, AI-visibility, accessibility and security signals, with fixes for your platform.
Check my site freeFAQ
Is aria-label as good as a visible label?
It meets the technical requirement, but a visible label is better for everyone. Sighted users and people with cognitive disabilities benefit from seeing the field name, and voice-control users need visible text to say. Use aria-label only where there is genuinely no space, such as a search icon field.
Do placeholder attributes count as labels?
Some automated checkers accept a placeholder as a last-resort name. Accessibility guidance (WCAG and WAI-ARIA authoring practices) still recommends a real label, because placeholders vanish on input and are often low contrast. Treat placeholders as hints, not names.
Do hidden inputs and submit buttons need labels?
No. Fields with type="hidden" are ignored. Buttons get their name from their text or value. A submit button still needs meaningful text, such as "Send message" rather than an empty icon.
How do I label a group of radio buttons or checkboxes?
Give each option its own label linked by for and id. Then wrap the group in a fieldset and put the shared question in a legend, such as "How should Example Co contact you?".
How to Fix Buttons Without Accessible Names on Your Site
How to Fix Missing Image Alt Text for Accessibility
How to Fix Links Without Discernible Text on Your Site
How to Fix Colour Contrast Errors (WCAG 1.4.3)
How to Fix a Missing or Invalid Page Language (html lang)
How to Fix WCAG 2.2 AA Accessibility Violations on Your Site