How to fix select name on Adobe Commerce (Magento)

Steps for Adobe Commerce (Magento)

1. Unlabeled selects typically appear in: product option/swatch selects, the layered navigation sort dropdown, country/region selects in checkout, and currency switchers.
2. Create a custom theme (or use your existing child theme) under `app/design/frontend/<Vendor>/<theme>/`. Never edit core files directly.
3. For product options, override `Magento_Catalog/templates/product/view/options/type/select.phtml`. Locate the `<select>` and add `id="select_{{ $block->getOption()->getId() }}"`. Add `<label for="select_{{ $block->getOption()->getId() }}">{{ $block->getOption()->getTitle() }}</label>` before the select.
4. For the sort-by toolbar dropdown, override `Magento_Catalog/templates/product/list/toolbar/viewmode.phtml` and `toolbar.phtml`. Add a `<label>` with a matching `for` and add a matching `id` to the `<select>` for sorting.
5. For checkout country/region selects, override `Magento_Checkout/frontend/templates/onepage/shipping.phtml` or use a ViewModel/plugin to inject the correct `id` and matching `<label>` elements.
6. Run `php bin/magento cache:flush` and `php bin/magento setup:static-content:deploy`, then test with a screen reader and the axe browser extension.

What is select name?

Every dropdown menu on your website (a `<select>` element — things like "Choose a size", "Select a country", or "Sort by") must have a text label that is programmatically linked to it. Without this link, a screen reader user who tabs to the dropdown hears nothing useful — just "combo box" with no context about what they're supposed to choose. A label can be a visible `<label>` tag, a hidden-but-accessible ARIA attribute, or a wrapping label element — but something must be there and connected.

Screen reader users — who include blind shoppers, people with motor disabilities, and many others — cannot use unlabeled dropdowns. This directly breaks the shopping experience: they cannot select a product size, filter results, choose a shipping country, or complete a checkout form. Beyond lost sales, missing form labels violate WCAG 2.1 Success Criterion 4.1.2, which is cited in accessibility laws in the US (ADA), EU (EAA), UK (PSBAR), and Canada (AODA). Accessibility lawsuits overwhelmingly target e-commerce sites, and missing form labels are among the most commonly cited violations. Fixing this removes legal risk and opens your store to a wider audience.

See the complete Select name guide for every platform and the full background.