Rules · select-name
Failure reference
Select fields without an accessible name.
Country pickers, quantity selectors, sort orders — a <select> without a name is a mystery menu.
What fails — and who it fails
The failure, in plain language.
Selects labeled only by proximity or a first disabled option ("Bitte wählen"). The accessible name must be programmatic.
Detection — what the machine can and cannot judge
How the scanner finds it.
- Every select is checked for a label association, aria-label or aria-labelledby.
The legal reading — factual, not fearful
Where this sits in enforcement.
Same family as field labels: checkout-path, task-blocking, and first on guided-audit checklists for commerce.
The fix — by pattern
The pattern that clears it.
- <select><option>DE</option>…</select>
+ <label for="ship-c">Lieferland</label>
<select id="ship-c">…</select>Fix the template, not the page — one change typically clears every instance at once. The triage engine groups findings by template pattern for exactly that reason.
Verification — resolution is evidence, not a checkbox
Fixed means a scan said so.
On monitored domains, mark the finding fixed and the next scan verifies it: zero remaining instances converts the finding to Resolved, and both the claim and the confirmation land in the append-only ledger. Criteria that need human judgement close through sign-off in the coverage matrix — covered by the right method, never by assumption.
Related failures:
See where your templates stand.
A complimentary assessment renders up to 25 public pages in an EU-hosted browser and shows every instance of this failure — grouped, ranked, and honest about what still needs a human.