How to fix “Select element must have an accessible name”
By Justin Zagar · Updated
A dropdown menu on the page has no label, so a screen reader announces the current choice with no idea what it's choosing. Give the select element a label with for and id, like any other form field.
- axe rule
select-name- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Lighthouse
- Google Lighthouse and PageSpeed Insights report it as “Select elements do not have associated label elements.”
What it means
A select element is a form field like a text box, and it needs a name the same way. A first option that reads "Choose a state" doesn't count. Once someone picks Florida, that hint is gone and the dropdown is just "Florida, combo box".
Missing form labels show up on 51% of home pages in the WebAIM Million 2026, and dropdowns are part of that count.
Who it affects
People who use a screen reader or voice control.
How to find it
- Run the free checker. Each dropdown it lists shows its name attribute in the code.
- Check sort menus on shop pages, state and country menus in forms, and language pickers.
How to fix it
- Add a visible label element and point its for attribute at the select's id.
- For a sort menu where a visible label doesn't fit the design, use an aria-label such as "Sort products".
A state menu
<select name="state">
<option>Choose a state</option>
<option>Florida</option>
</select><label for="state">State</label>
<select name="state" id="state">
<option value="">Choose a state</option>
<option>Florida</option>
</select>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
- Form elements must have labels
Form fields without labels
- Buttons must have discernible text
Buttons with no text
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.
Rather have someone fix it for you? Tell me about your site.