Hello! I'm struggling to understand what this means from a development standpoint.
As a developer do I need to do anything on my end to make a slider accessible to a screen reader? I understand changing Focus order, but if there's content hidden in a slider that might be difficult for someone to access, do I need to somehow note that so the user knows to switch the screen reader to Browse mode?
I appreciate you sharing your concerns as you create your accessible course. For anyone following along, the image is from our Storyline 360: Working with Sliders article, specifically the Understanding Slider Accessibility section.
Sliders are accessible, which includes the navigation you are referring to. Regular screen reader users will be familiar with navigating using Browse and Focus modes. No additional work is needed, but providing clear instructions to set expectations is good practice, especially if there is content on layers along the slider steps.
The sliders them selves are accessible, but the focus order does not leave the slider so content is not read as you move the slider, you could change the state of the slider and add the content in the alt text of each state
2 Replies
Hi Heather!
I appreciate you sharing your concerns as you create your accessible course. For anyone following along, the image is from our Storyline 360: Working with Sliders article, specifically the Understanding Slider Accessibility section.
Sliders are accessible, which includes the navigation you are referring to. Regular screen reader users will be familiar with navigating using Browse and Focus modes. No additional work is needed, but providing clear instructions to set expectations is good practice, especially if there is content on layers along the slider steps.
The sliders them selves are accessible, but the focus order does not leave the slider so content is not read as you move the slider, you could change the state of the slider and add the content in the alt text of each state