- Success Criterion 4.1.2
- Conformance level A
Rating Widget With No Name or Value Semantics at All
4.1.2 — Name, Role, Value
Scenario
Setting
A professional networking site's profile editor
What’s wrong
Rating widgets with no name/value semantics.
Example
<div class="checkbox" onclick="toggle()"></div> Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes.
How to test
Inspect a rating widget in DevTools: check for a name and value semantics (e.g., radiogroup pattern) — visual-only stars with no semantics fail.
How to fix
Give the rating widget a name and value semantics (e.g., radiogroup or slider pattern).
<input type="checkbox" id="opt-1"><label for="opt-1">Email notifications</label>A native input exposes its role and checked state automatically; a styled div exposes none of that without a lot of manual ARIA.
Outcome
On a professional networking site's profile editor, this barrier is gone for screen-reader and voice-control users who can operate only what the accessibility tree exposes — they no longer have to work around this.
Who is affected
Screen-reader and voice-control users who can operate only what the accessibility tree exposes.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Custom Dropdown or Slider With No Accessibility API Support
- Content Changes That Never Update Their Accessible Name
- Scripted Link or Button With No Real Role or Keyboard Support
- Clickable Div Turned Into a Control but Given No ARIA Role
- Form Field With No Programmatic Label at All
- Assistive Technology Never Told Which Element Currently Has Focus