- Success Criterion 4.1.2
- Conformance level A
Custom Slider Missing Its Value, Minimum, or Maximum Settings
4.1.2 — Name, Role, Value
Scenario
Setting
An online marketplace's seller dashboard
What’s wrong
Sliders (role="slider") missing value settings in code (aria-valuenow/min/max) or a name.
Example
An online marketplace's seller dashboard runs into this exact issue: sliders (role="slider") missing value settings in code (aria-valuenow/min/max) or a name.
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. On an online marketplace's seller dashboard, this barrier means they are excluded from part of the experience.
How to test
Inspect a slider (role="slider") in DevTools: check for aria-valuenow, aria-valuemin, aria-valuemax, and a name — any missing fails.
How to fix
Add value settings in code (aria-valuenow/min/max) (and aria-valuetext where useful) plus a name to sliders.
Outcome
Corrected, an online marketplace's seller dashboard now lets a visitor complete the task without extra help.
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