Accessibility and screen readers

Hi Lauren, I see this is still an active conversation.  We completed a module for an external vendor, and they have come back saying there were a few accessibility issues when using a screen reader.  Was hoping someone may be able to give us some guidance.  We just tested in NVDA and have confirmed the issues.  We have done all the focus order, removed extraneous shapes etc within storyline, so not sure what else we should do.  

Here are a few examples of the issues we are experiencing:

- When they click on a button to see a text box, the text box is saying "blank" and you have to press the down arrow to continue to the actual text (we also have heard "clickable main landmark"
- When selecting some slide titles, the screen reader is saying "blank"
- When on slide titles in the menu, the screen reader is reading the incorrect title or "none"
- On our custom calculation slide the dynamic text is not being read for example "$ calculation"

Another issue is if you try to arrow down on the open side menu, it is not reading the slide names.

Hoping you might be able to guide us.  

Since the file was paid for by an external vendor, I was hoping I could provide you the storyline file privately. Please let me know if this is a possibility and next steps.

I have a related question: how do SL's zoom regions behave on readers? Do they obstruct captions and navigation?

Welcome to the community, Devin!

I'm sorry that you're experiencing similar issues. We're happy to work directly with you in a support case to help determine what's going on. Feel free to share a sample project with us for testing purposes, and we'll reach out with an update shortly after!

I am getting all these issues and I'll throw a couple more into the mix.

1. Random Yellow highlight boxes appearing when there is nothing on the slide, the slide master or feedback master (if on a layer).
2. Screen reader (NVDA) deciding not to read any text on screen, or not reading all text. I am familiar with NVDA pausing after 100 characters (using Insert+DownArrow(twice)) it reads it all. However, on some slides it simply does not read the text, even though it is in the Focus Order.

Are you using latest update? A lot of fixes were added for this.

Thanks Phil. I do have the latest version now but the module was likely built initially with a much older one, if that is a factor. I will test this further tomorrow and see how it goes. Initial preview of the module still shows these issues but perhaps better luck with publishing for web or SCORM.

Hi Ray,

If you still need our help after your testing, please share your project file privately with our support engineers to investigate what's happening with your permission. It will be deleted when troubleshooting is complete.

Thanks Leslie. I needed to seek permission from our client and have now submitted the support case.

We are experiencing a similar problem and I'm hoping someone can help. There is so much extra wording before NVDA reads a button name. For example: Clickable lesson content main landmark storyline grouping <project name> dash admin frame main landmark review. The only thing it should read it "Review." It's the same with buttons. Is this really how it's supposed to be read? Any help would be greatly appreciated. 

Hi everyone.  Great thread.  I'm just getting into accessibility so learn a lot here.  Can anyone tell me how to set up a slide so screen readers do not read hidden text.  I have a 25 question quiz  that generates five possible topics in the course.  Depending on the 'score', zero to five of the answers are shown, with the others present but hidden. I want the screen reader to read only the shown items and ignore the others. Any suggestions please.