in a storyline file, the audios integrated on a page start simultaneously with the NVDA programme. The result is that you can hardly understand anything. Is there a possibility in the NVDA screen reader to start the audios with a special button? Or is it possible, that NVDA waits until the audio that was started automatically has finished playing? Is there a function in Storyline that can support this?
Most people who use screen readers will switch off the audio. There is a requirement in WCAG where audio is used there should be the option to turn the audio off.
Does Articulate have any tutorials or guides on how to navigate a Storyline or Rise module using the NVDA reader? Our employees with visual impairments struggle with Rise, for example. Many use landmarks to move through a page and it seems rise does not use landmarks. Our users get stuck with the following. A lesson with a basic header title, then a video and then a divider that says continue when the video has completed. When the user "eventually" gets off the many and to the main page, hitting Shift + down Arrow does read the header text, then hitting tab gets them to the video which it plays. Even when the video is finished and the continue button is available there is no way to jump to the Continue button to move to the next lesson. I am surprised that with the focus on accessibility with Rise and Storyline there are no specific tutorials or examples of using a Reader to correctly navigate a Rise course or Storyline module. Has anyone got examples of navigating a rise module using an NVDA reader please so I can make sure our modules are correct and to provide assistance to our users?
What is interesting though is that if any of the Pre-made Rise courses with Real content are put through an accessibility audit they all fail.....so we cannot real complain when impaired users highlight issues...which is why I would like to see an example of a user using a reader with a Rise course....
5 Replies
Hello Wolff!
Thanks so much for reaching out!
I'd like to share this tip from the NVDA website on how to start and stop NVDA:
We recommend not auto-playing the audio within your course. This way, your learners will control the playback.
Feel free to share your .story file in the thread so we can take a closer look at your current setup!
Looking forward to hearing from you!
Most people who use screen readers will switch off the audio. There is a requirement in WCAG where audio is used there should be the option to turn the audio off.
Does Articulate have any tutorials or guides on how to navigate a Storyline or Rise module using the NVDA reader? Our employees with visual impairments struggle with Rise, for example. Many use landmarks to move through a page and it seems rise does not use landmarks. Our users get stuck with the following. A lesson with a basic header title, then a video and then a divider that says continue when the video has completed. When the user "eventually" gets off the many and to the main page, hitting Shift + down Arrow does read the header text, then hitting tab gets them to the video which it plays. Even when the video is finished and the continue button is available there is no way to jump to the Continue button to move to the next lesson. I am surprised that with the focus on accessibility with Rise and Storyline there are no specific tutorials or examples of using a Reader to correctly navigate a Rise course or Storyline module. Has anyone got examples of navigating a rise module using an NVDA reader please so I can make sure our modules are correct and to provide assistance to our users?
I don't believe there is any tutorials, the hope would be they navigate using the same way they would a web page.
May help to raise a support case to look at the issues
What is interesting though is that if any of the Pre-made Rise courses with Real content are put through an accessibility audit they all fail.....so we cannot real complain when impaired users highlight issues...which is why I would like to see an example of a user using a reader with a Rise course....