I m developing an accessible course in storyline 36o. Using NVDA reader to test the module accessibility. Firstly NVDA is reading the on screen text only on down arrow key and not on tab. On tab it's just reading the player buttons, and the rest of the default things. Secondly, it's reading 'blank' after each screen name.
I'm happy to help! Based on NVDA's keyboard shortcuts, using the down arrow reads the on-screen text and the Tab key navigates to interactive objects like buttons. What you're experiencing is expected when it comes to keyboard shortcuts.
When NVDA announces "blank," that means you've navigated to an empty spot and need to navigate to the next item.
What you're noticing is expected when using a screen reader.
I also want to ask about prev button's accessibility. For prev button, NVDA reader reads Slide navigation navigation landmark previous button. Is it ok? For next button it just reads Next button
Great question. NVDA is announcing the name of the group before the previous button. That's expected, too, since the previous button comes before the Next button.
I'm not sure that the reader announcing 'blank' is expected behaviour. I've published Rise 360 courses and had a much smoother and intuitive experience navigating with NVDA. It would be amazing if Storyline could offer a similar experience.
If you have a Storyline 360 project that you're experiencing difficulty with when using a screen reader, we'd be happy to help. Please share your project file publicly here or send it to me privately by uploading it here. I'll delete it when troubleshooting is complete.
7 Replies
Hello sayali!
I'm happy to help! Based on NVDA's keyboard shortcuts, using the down arrow reads the on-screen text and the Tab key navigates to interactive objects like buttons. What you're experiencing is expected when it comes to keyboard shortcuts.
When NVDA announces "blank," that means you've navigated to an empty spot and need to navigate to the next item.
What you're noticing is expected when using a screen reader.
Thanks Lauren..
I also want to ask about prev button's accessibility. For prev button, NVDA reader reads Slide navigation navigation landmark previous button. Is it ok? For next button it just reads Next button
Hello sayali!
Great question. NVDA is announcing the name of the group before the previous button. That's expected, too, since the previous button comes before the Next button.
I'm not sure that the reader announcing 'blank' is expected behaviour. I've published Rise 360 courses and had a much smoother and intuitive experience navigating with NVDA. It would be amazing if Storyline could offer a similar experience.
Hi Neil,
If you have a Storyline 360 project that you're experiencing difficulty with when using a screen reader, we'd be happy to help. Please share your project file publicly here or send it to me privately by uploading it here. I'll delete it when troubleshooting is complete.
Hi, can you please elaborate - what is the 'empty spot' you mention after the screen title is read?
Hi, Laurel.
I did a little digging, and it looks like we have a bug reported where NVDA adds "Blank" phrase when reading the Slide title.
Is this what you're experiencing?
I've connected this discussion to the bug report, and I'll be sure to come back to update you when I have some news.
In the meantime, here's more information on how we identify and tackle bugs.