Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for select elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-21 | ✗→✓ | ▲ Improved | -8% | 0% |
| case-19 | ✓→✓ | ＝ Same ✓ | -12% | 0% |
| case-01 | ✓→✓ | ＝ Same ✓ | 29% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | 56% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | 68% | 0% |
Without an accessible name, screen reader users will not know what information the dropdown is asking for, making forms impossible to complete.
<label> element with a matching for attribute for every <select>aria-label or aria-labelledby if a visible label is not possibleCheck that every <select> element in your forms has a valid accessible name or linked label.
Add a <label> element with a for attribute that matches the id of the <select> tag.
Explain how accessible names for select elements provide the necessary context for users of assistive technologies.
Review the rendered markup and interactive states that affect Provide accessible names for select elements. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/accessibility/select-name
Other measured skills in the registry, with their headline benchmark lift.