Forum Discussion
Screenreader doesn't work with dials or slider
Hi, I have 2 different courses with a slider and dial. I have set text state to become visible when these are moved. However, testing with a screenreader, just '1', '2', etc are read out, not the text. The focus order is correct. Please help, thank you
Hi Diane Bullock, Can you please share your SL file so that I can take a look and give it try?
Thanks, I have attached the dial one. Using NVDA published to review 360 :)
Hi again, Thank you for sharing your file and I apologize for the delay in responding back.
I had a look at your file and everything seems to be working fine at my end. The content in the text boxes were reading fine.
As per my observation, once the module loads, clicking on the TAB, it directly navigates to the dial icon and depending on the dial value the corresponding text box state changes. Once all the text boxes changes to normal state, then click the TAB button and it popup message (refer to screenshot) saying "Back to top" and select "Enter". By selecting that, you will be able to access the text boxes in the same order that you have specified in the FOCU order by using the down arrow key.
Hope you'll be able to move forward with this!!
Thanks Sandeep. You are saying you have to go through every dial setting, 1-6 first and only after that the text will read out, using the tab key? That might be a getaround but very complicated and how would anyone else know this? The dial is therefore pointless in this case.
Also, I found a few tutorials related to accessibility:
9 Basic Screen Reader Commands to Know When Testing Your E-Learning Courses
- The main carousel accessibility consideration for sighted users is to not make it auto-play. If you must make the carousel auto-play, then you need to provide a pause or stop button. If you use a pause or stop button, place it before the carousel, and provide descriptive link text like, “Pause animated content.”
Thanks JOhn, not sure what you mean by autoplay. No sound file, just talking about screenreaders
I guess this is the expected behavior in Storyline when it comes to 508-accessibilty. I found an article here.
Hi Diane,
I see that you’ve reached out to our Support Engineers and are working with my teammate, Johnrey. You’re in great hands! We’ll continue the conversation in your support case.
