What a screen reader is reading following upgrade

There have been many discussions about the new upgrade and AT compliance. Rather than this get lost, I am starting a new post. I have taken a slide and recorded what is being read by JAWS. Please listen to the audio files alongside the screen shot. 

The first audio file is me navigating through, using the down arrow key (after the slide title was read several times).

The second audio file is playing by itself with no navigation at all.

In the player settings, the title is blank and left hidden. Slides are named as usual. Tab order seems correct.

Questions:

1. Why does the slide title get read out so many times?

2. Is there a way to get it to read the bullets properly? Usually, on a webpage, it will say, "Bullet list with 5 items," or something like that and then you can navigate through each item. Storyline doesn't seem to recognise the bullets so it doesn't announce them and it doesn't pause in the right places. For this example, I have put a comma in white text after each bullet point.

3. Why does the audio randomly stop in the middle of a sentence? This happens on all slides when using the arrow keys to navigate. It doesn't happen if you just leave it to play through, but then you can't use any buttons.

4. I can see when there is a button coming because I designed it and have vision. How would a blind person, navigating this for the first time, know when to suddenly switch between arrows and tab? You can access buttons with the arrow keys and space but it doesn't tell you you can until after you've done it. 

Sorry for the long post but I wanted to explain some of the issues well enough for you to understand.

 

12 Replies
Noel Sapp

Thanks for sharing your experience. I have to say getting Storyline360 level with compliance standards is frustrating, to say the least.

I too agree that bullet lists should be appropriately tagged as such. In HTML or PDF docs, the List tag announces the list and actually counts how many List Items there are nested under it. Then each List Item (bullet) is announced as 1 of 4, or for how ever many total bullets there are within the list element. I'm not sure Storyline360 deals with content tags much at all. I posted a similar issue with slide titles not having HTML Header tags (H1, H2, etc.) so clients expecting to hear and navigate to headers are unable to do so.

Your example of the slide title being read sounds like it is reading the HTML div block open tags (or something). Very odd stuff. Anyway. I just wanted to comment, say thanks for sharing, and to offer a free bump so someone can see your thread again.

Leslie McKerchie

Hi Nicki,

No worries about the long post. I appreciate you sharing the details.

  • Numbers 1 and 2 are documented items that we are looking into and I've attached this conversation as we track user impact and so that we can share updates with you here.
  • For number 3, I can hear it in your sample, but I've not had this experience nor do I see this reported anywhere.
    • You should not have to press any keys to listen to slide content and this article explains the expected behavior.
  • I'm not sure I'm following number 4. Is the button on the slide? If so, the screen reader is reading it, right? If you have a sample slide, I'd be happy to take a look to better understand what you're running into.
Lesley Mizer

I'm testing a course published with the Jan 22 update, and with the NVDA screen reader, and it isn't automatically reading the text on the slide. It only starts reading automatically when I open the course the first time, but then it'll repeat everything from the beginning- until I press a key. Once I press a key and navigate to subsequent slides, I have to press the "+" or the NVDA key (mine is the Caps lock) and the down arrow for it to begin reading the slide. And, it also reads the titles several times, so I removed the title from the course player, and I've hidden the title text boxes that are on the slides from the screen reader.

Before having access to the screen reader, I was naming the title text boxes, "heading" thinking the screen reader would read that out and then the text of the header, but it doesn't do that. It just reads the text.

That said, I'm a beginner to NVDA and I'm still learning to navigate with it.

Nicki Berry

Hi Leslie

No. 4 - If I'm using the arrow keys to tab through, when I get to the previous/next buttons, it reads them out: "Next button." I can press space to activate but it doesn't tell me that. After I've pressed space to activate, it reads it again "Next button, press space to activate," but it's too late then. Using the tab key instead of arrows, it works fine but that is what I was asking... I know to change to the tab key because I can see that the next thing after the final bit of content is a navigation button, but a blind person wouldn't know this. 

Noel Sapp
Nicki Berry

Hi Leslie

No. 4 - If I'm using the arrow keys to tab through, when I get to the previous/next buttons, it reads them out: "Next button." I can press space to activate but it doesn't tell me that. After I've pressed space to activate, it reads it again "Next button, press space to activate," but it's too late then. Using the tab key instead of arrows, it works fine but that is what I was asking... I know to change to the tab key because I can see that the next thing after the final bit of content is a navigation button, but a blind person wouldn't know this. 

Hey. Sorry to keep bugging you about this thread! Are these prev/next buttons custom? Or are you using the default navigation that the player provides?

The reason I ask is that I've noticed that when I group objects to create a button-like object with a trigger, I get a similar issue in which my screen reader will try to read literally every object within the group. So for example, say I have 1 icon and 1 text field grouped to act as a single button. Once I've tabbed to the grouped button object, I hear "Icon's name, button" for the first object, then it stops. I tab again to the second object within the group to hear, "Whatever text I have in the grouped text field, button." Finally, if I tab again  then I hear, "My custom group/button name that I created as Alt text, button. Press Space Bar to activate."

Of course I can press space bar at any time while I'm tabbing through and it will activate. I don't want the user to activate the button until the actual text of it has been read so my work around has been to literally set everything within the button group to NOT be read by a screen reader. Instead, I have to place the text that I want the listener to hear as the Alt text of the button group.

This gets very annoying when importing icons from the SL360 Content Library as many of them have several separate elements all grouped and sub-grouped. Even if I set the icon to be ignored by a screen reader, it will still try to read all the individually grouped items!!! I recently imported one icon that had like 9 different elements. Each one was tabable and recognized by JAWS. UGH.

I bring all this up in case you're using similar custom button groups. This may not at all be related to what you're experiencing, but figured I'd throw it out.

Nicki Berry

Yes, I am using custom navigation buttons. They look like this:

Previous and next buttons

They are an arrow image and the object has a border, so it's not a group. The screen reader reads it according to the alt text - "Next button" but it only adds "press space to activate" if you tab to it, NOT if you use the arrow keys. That is the same with all buttons.

Ren Gomez

Hi Nicki,

Good news! We fixed the issue where JAWS was not announcing bullets in lists on stage.

Here's how to install the latest Storyline 360 update to see all the recent enhancements and fixes.

If the problem reappears, please connect with our team, or share a screen recording here, and we'll be happy to help!