"Select element must have an accessible name": how to fix drop-down menus with no label
Published · Updated
“Select element must have an accessible name” is the error you’ll see in axe. Lighthouse calls it “Select elements do not have associated label elements”, WAVE calls it “Select missing label”, and the Tabwise scan calls it “Drop-down menus without labels”. They all mean the same thing: a drop-down menu on your page has no name.
A drop-down is a box you click to pick from a list, like the number of guests or your county. If it has no label, a screen reader user hears the choice, such as “2”, but not the question. They don’t know whether 2 means adults, children, nights or rooms.
In our study of Irish business websites, almost one in ten (9.5% of 6,576) had a drop-down with no label. Across all the Irish business websites in our studies, it was 6.2% of 12,397.
Who this affects
Mainly people who use a screen reader. That’s software that reads the page aloud, used by blind people and many people with low vision. They hear the label first, then the choice. Without the label, they hear a number or a word with no context.
It also affects people who use voice control. They move to a drop-down by saying its name, like “click County”. If it has no name, there’s nothing to say.
Where it turns up
These are the drop-downs we see most often with no label:
- Booking widgets: number of adults, children, nights or rooms.
- County pickers: on contact, delivery and enquiry forms.
- Enquiry forms: “Which service are you interested in?” or “How did you hear about us?”, where the question sits nearby as plain text but isn’t connected to the box.
- Date pickers: separate boxes for day, month and year.
Online shops have them too. Product options, like size and colour, are often drop-downs. In our study of Irish online shops, 3.7% of 2,385 had a drop-down with no label. That’s lower than across all businesses, but a missing label on “Size” can stop a sale.
How to fix it
Every drop-down needs a visible label that’s connected to it, like “Number of adults” or “County”. The first option in the list, such as “Choose one”, doesn’t count as a label.
Run our free scan first. The report tells you which drop-downs have no label. Our guide to reading your scan report explains each part of it.
If it’s a widget from another company
Many of these come from booking engines, reservation systems and other third-party widgets. You can’t change their code, but you can ask them to. Send this to the company that supplies the widget:
Our accessibility scan says some drop-down menus in your widget have no label (WCAG 2.1 success criterion 4.1.2). Can you give every drop-down a visible label that’s connected to it, like “Number of adults” or “Nights”? When will that be fixed?
You can also ask whether they have accessibility documentation, and whether their widget has been tested with a screen reader. Keep their answers. If you’re covered by the accessibility rules, they help with your accessibility statement.
WordPress and WooCommerce
Drop-downs in contact forms come from your form plugin. Open the form and check each drop-down field’s settings for a label. If you use Contact Form 7, its page on checkboxes, radio buttons and menus covers drop-downs.
Product option drop-downs come from WooCommerce and your theme. If our scan flags one, contact your theme’s developer. Then run our free scan again to check.
Shopify
The size and colour pickers on product pages come from your theme. If our scan flags one, contact your theme’s developer. If the drop-down comes from an app, such as a product options app, contact that app’s developer.
Wix
For drop-downs in Wix Forms, give each field a title. Wix’s help page on creating an accessible Wix form shows where, and how to make sure the title is shown.
Squarespace
In a Squarespace form block, each drop-down field has its own label. Squarespace’s guide to form fields explains how to set it.
If someone else built your site
Copy this and send it to your web person:
Some drop-down menus on our website have no accessible name, which fails WCAG 2.1 AA (success criterion 4.1.2). Please give every drop-down a visible label that’s connected to it, including booking, county, enquiry and product option drop-downs. If any come from a widget or app, can you tell me which one?
How to check it’s fixed
Run our free scan again. It lists any drop-downs that still have no label. It checks your homepage and up to four pages linked from it, so look at your other booking, contact and product pages too.
Then try a quick test by hand. Click on the label next to each drop-down. That should move you into the drop-down. If nothing happens, the label probably isn’t connected.
For other pages, try the free WAVE checker from WebAIM. Type in the address of any page and look for “Select missing label” in the results.
For your web developer
axe reports this as select-name, against WCAG 2.1 success criterion 4.1.2, Name, Role, Value.
- Connect a visible
<label>to every<select>:
<!-- Before -->
<select name="adults">
<option>1</option>
<option selected>2</option>
</select>
<!-- After -->
<label for="booking-adults">Number of adults</label>
<select id="booking-adults" name="adults">
<option>1</option>
<option selected>2</option>
</select>
- For a question that sits nearby as plain text, either make it the
<label>or point to it witharia-labelledby. - A first option like “Choose one” is not a name. Unlike
label,select-namedoes not accept aplaceholder. - For day, month and year boxes, group them in a
<fieldset>with a<legend>, and give each<select>its own label (“Day”, “Month”, “Year”). - Check drop-downs injected by booking engines and product option apps, which often load after the page and aren’t in the theme code.