# Select Name

> 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.

- Skill: `thedaviddias/select-name` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add thedaviddias/select-name`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedaviddias/select-name/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: thedaviddias (https://skillmd.com/u/thedaviddias)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/thedaviddias/select-name

---


# Provide accessible names for select elements

Without an accessible name, screen reader users will not know what information the dropdown is asking for, making forms impossible to complete.

## Quick Reference

- Use the `<label>` element with a matching `for` attribute for every `<select>`
- Alternatively, use `aria-label` or `aria-labelledby` if a visible label is not possible
- Avoid using the first option as a replacement for a proper label

## Check

Check that every `<select>` element in your forms has a valid accessible name or linked label.

## Fix

Add a `<label>` element with a `for` attribute that matches the `id` of the `<select>` tag.

## Explain

Explain how accessible names for select elements provide the necessary context for users of assistive technologies.

## Code Review

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