When using Jaws or another screen reader, you would need to enable each item and text on the screen to be visible to accessibility tools as described here. If it's an image or other object, you'll also want to include some alt text so that the screen reader accesses that instead of the file name of the object/image itself. If the text is part of a video, you may want to look at using the notes feature in Storyline or setting up a closed captioning behavior.
Thanks for your reply my issue is resolved, i was using goggle chrome and Screen Reader Support only Articulate Storyline’s Flash-based output in internet explorer.
But now i want to know that can we skip Interface elements (menu, resources, items) on every slide by a screen reader.
I Also want to know that which is the best way for creating 508 Compliance course using default Story line Player or creating customized player. Because when i am using default player The Screen reader "NVDA" does not read NEXT And PREV Button by tab button.
6 Replies
Hi Amar,
When using Jaws or another screen reader, you would need to enable each item and text on the screen to be visible to accessibility tools as described here. If it's an image or other object, you'll also want to include some alt text so that the screen reader accesses that instead of the file name of the object/image itself. If the text is part of a video, you may want to look at using the notes feature in Storyline or setting up a closed captioning behavior.
I also wanted to share some additional documentation here on Storyline's 508 compliance.
Hi Ashley,
Thanks for your reply my issue is resolved, i was using goggle chrome and Screen Reader Support only Articulate Storyline’s Flash-based output in internet explorer.
But now i want to know that can we skip Interface elements (menu, resources, items) on every slide by a screen reader.
HI All,
I Also want to know that which is the best way for creating 508 Compliance course using default Story line Player or creating customized player. Because when i am using default player The Screen reader "NVDA" does not read NEXT And PREV Button by tab button.
Hi Amar,
If you wanted to skip elements you'd need to disable them from being accessible to screen readers as described here.
You can't do this for player features though.
In the Player, it uses Next, and Prev for Previous. Will the screen reader read it as Prev, or does it need to be spelled out and say previous?
Hi Debbie,
JAWS reads "Prev Button" and "Next Button". Let me know if you have other questions!
This discussion is closed. You can start a new discussion or contact Articulate Support.