When you’re building an accessible e-learning course, one requirement is that your content work on screen readers. (If you’re not familiar with screen readers, check out this article before c...
Published 7 years ago
Version 1.0
Blog Post
Hi Nicole,
Apologies for commenting on this article a couple of years late, but I'm curious to learn more about the specifics of testing a Storyline 360 course with a screen-reading tool such as NVDA. I don't have access to the JAWS screen reader, so NVDA is all i have for testing. Your article is very well-done, but is more of a "why it's necessary" than a true "How-to" for using a screen reader to test specific items in a Storyline course with a screen reader. Do you have some best practices that Storyline designers and testers could use/look for specifically (in addition to the usual things like tab order, alt text, etc.)?
My team and I have found a reference guide of NVDA keyboard navigation shortcuts (https://dequeuniversity.com/screenreaders/nvda-keyboard-shortcuts#nvda-nvda_shortcut_keys) but none of them seem to address some of the UI elements unique to a Storyline module (e.g. non-active tabs and marker popups). This is a useful resource, but having the NVDA tool be able to recognize marker popups or open tabs such as Transcript, Menu, Resources, etc and have the NVDA read these elements has been a particular pain point for us. One of our Designers ran into a way to open marker popups by pressing the Tab and Spacebar keys together, but opening the marker popups is all it seems to do--*reading* the marker popups is another thing. Is there a shortcut combination not listed in the Deque U reference that would allow us to have NVDA read marker and tab popup content appropriately?
Thanks much ahead,
Michelle
Apologies for commenting on this article a couple of years late, but I'm curious to learn more about the specifics of testing a Storyline 360 course with a screen-reading tool such as NVDA. I don't have access to the JAWS screen reader, so NVDA is all i have for testing. Your article is very well-done, but is more of a "why it's necessary" than a true "How-to" for using a screen reader to test specific items in a Storyline course with a screen reader. Do you have some best practices that Storyline designers and testers could use/look for specifically (in addition to the usual things like tab order, alt text, etc.)?
My team and I have found a reference guide of NVDA keyboard navigation shortcuts (https://dequeuniversity.com/screenreaders/nvda-keyboard-shortcuts#nvda-nvda_shortcut_keys) but none of them seem to address some of the UI elements unique to a Storyline module (e.g. non-active tabs and marker popups). This is a useful resource, but having the NVDA tool be able to recognize marker popups or open tabs such as Transcript, Menu, Resources, etc and have the NVDA read these elements has been a particular pain point for us. One of our Designers ran into a way to open marker popups by pressing the Tab and Spacebar keys together, but opening the marker popups is all it seems to do--*reading* the marker popups is another thing. Is there a shortcut combination not listed in the Deque U reference that would allow us to have NVDA read marker and tab popup content appropriately?
Thanks much ahead,
Michelle