Forum Discussion
Windows Narrator screen reader
Hi guys,
I'm trying to make my published courses to be read by Windows Narrator but it only reads interactive buttons (it doesn't read the body text at all). Is it a known problem? Or it's just J...
Hi Jacek!
It doesn't look like the attachment came through when you replied via email. Do you mind attaching it to this discussion instead?
I've listed out your questions below, and I'll answer them one by one:
Why does JAWS read the slide title 3 times in a row? Is this a snag in Storyline or JAWS? Can you remove this functionality completely?
Unfortunately, this is a bug in JAWS that we've noticed in other areas too. We are staying up to date with JAWS software updates and I hope this is included in an upcoming release. It is definitely somewhat obnoxious, and I've heard many screen reader users mention this bug.
However, I've heard that this issue was partially fixed in JAWS 2020 so that's a step in the right direction!
Why does JAWS read buttons twice?
This is the same bug that reads the slide title continuously, so hopefully, both of these will be fixed in the next update for JAWS.
JAWS doesn't read body text on some slides. It just reads blank.
I've noticed the same thing! Luckily, this was addressed in JAWS 2020.
The "blank" issue is addressed in this line:
- Added a new JAWS Settings Center option called "Skip Blank Lines While Navigating" which is on by default when reading web pages and PDF documents. This feature helps make reading more efficient as JAWS and Fusion ignores blank lines as you navigate using UP and DOWN ARROW. For those who prefer to hear blank lines while navigating, open Settings Center (INSERT+6) and clear this check box. You can find this new option in the Web / HTML / PDF group under Reading.
Why did we switch gears by removing the TAB navigation to using Key Arrows?
Simon, one of our talented Product Managers, explained this really well in this post.
Can you install a version of Storyline that doesn't use the Key Arrows and only uses TAB navigation?
Our Accessibility enhancements were first released in Storyline 360 Update 36 (Build 3.36.21213.0). We've continued to release improvements in Update 37 (Build 3.37.21453.0), Update 38 (Build 3.38.21779.0), and Update 39 (Build 3.39.21985.0). You'll find that content created in previous versions of Storyline 360 (Update 35 and earlier) aren't up to date with the recent WCAG standards. As we continue releasing accessibility enhancements, you'll see that courses built in previous versions of Storyline aren't fully keyboard-accessible nor do they communicate with screen readers properly.
