No accessibility annotations are needed for sliders, but keep these considerations in mind if you are modifying Carbon or creating a custom component.
Carbon bakes keyboard operation into its components, improving the experience of blind users and others who operate via the keyboard. Carbon incorporates many other accessibility considerations, some of which are described below.
Tab order goes from slider to text input. Arrow keys are used to change the
Shift+arrow changes the slider value by a larger increment (such
as by 10 instead of 1). Users can also directly enter a value in the input.
Keep these considerations in mind if you are modifying Carbon or creating a custom component:
stepvalue determines the change increment when moving the slider, either by pointer or keyboard. A value of
stepMultiplierdetermines the value change when the keyboard is used to alter the slider by pressing
Shift+ Arrow key. A tenth of the total range is recommended as a value, such as
"10"in a 0-100 slider.
- See the ARIA authoring practices for more considerations.