Accessibility ruining my day..........

Jun 28, 2018

Hi All, 

I have Knowledge tests using multiple choice interactions that are behaving oddly while I'm setting up for a screen reader to play nice. 

Issue 1. As I move through each page the screen read first focuses on my desktop and  reads the files name out to me, then changes focus to the SL window as a whole within my browser. It repeats this process on EVERY page as I progress through the course. 

Issue 2. Each page has the question both visible and narrated by a VO pro, so the text element of the question is set as invisible to the screen reader. Once the question is read out and the user tabs to the multiple choice options these are read out in the wrong order consistently regardless of turning shuffle answers on/off. 

I have set visibility for EVERY item appropriately in all layers including the master layer. 

I have removed all items SL3 will allow me to remove from the tab order and set an appropriate order for the remaining objects.

Regarding Issue 2 you seem to be able to set visibility for the individual answer choices but then have no control of these in the tab order screen? but the interaction as a whole does appear in the tab order screen? Surely given that this is a list and a built in SL function there should be some way to control this order? 

Using latest build of SL3, Windows Narrator to test, and playing course in chrome hosted locally. Before anyone asks yes I'm working on the course from a local drive. can't post the file here due to privacy restrictions. 

5 Replies
Ashley Terwilliger-Pollard

Hi Martin,

It looks like I also recently responded to you in this discussion - and I copied it below so that we could keep our conversation here:

It sounds like you're looking to skip the player navigation pieces? If so, you'll want to follow these steps:
  1. You'll tab through the slide objects in the order defined by the content author.
  2. When you press the Tab key after the last object on the slide, the screen reader will instruct you to press the spacebar or Enter key if you want to skip player navigation.
    • If you press the spacebar or Enter key, your next tab will jump back to the first object on the slide.
    • If you don't press the spacebar or Enter key, your next tab will proceed to the player navigation elements, starting with the previous and next buttons.
The option to skip player navigation is always enabled in published courses. You don't need to do anything to activate it.The initial tab into the course will still focus on the player window first, and read the Storyline file name.

As for your question and answer set up, the set of answers are one block in the Tab order set up, but I did notice that when the answers are set to shuffle the tab order follows the order I entered them into Storyline. That part looks like a bug to me, so I'm going to share it with my team and get some more eyes on it. I'll keep you posted here! 

martin beaver

Hi Ashley, 

Sorry I'm not sure what you mean.

I basically have the player disabled and we use our own navigation on slides. 

Every time you switch to a new slide the focus switches to the entire window, reads out the filename, the selects the whole frame as a selectable object (despite all background objects/images having this turned off) then the first tab moves to the interaction object. 

Re the shuffle thing, the answers are not set to shuffle however it reads them in reverse when tabbing to the interaction object as a whole? 


martin beaver

Hi Ashley, 

I'm sorry but I'm not able to share files here due to our company rules. 

RE: Issue 1. I think I understand a little more based on your link, essentially 'You don't need to do anything to activate it.The initial tab into the course will still focus on the player window first, and read the Storyline file name.'  This is happening on every single page of the course. 

We have our own custom slide elements to achieve navigation and other features and we disable/set to transparent etc as many of the in built player elements as possible. From what you've described there it seems that despite not utilising the built in elements, tab focus is automatically switching to them and therefore reading out the filename every time.  What I find puzzling about this is that if we were utilising these elements then this behaviour suggests that this would happen every time a user tabbed from player to content? Surely nobody wants the file name of the course read out to a partially sighted user on every single page?  

RE: Issue 2. Regarding the Answers being read in the incorrect order, can you give me an eta for this fix given that being able to navigate these in the right order is pretty critical to meet any accessibility criteria?

Also on a separate thread I've asked about .png's having their filenames read by screen reader rather than their name as set in the timeline or accessibility panel?  Again I've just been asked to send you files but this isn't possible. Is this a known issue? Is there a fix? 

Due to these problems we're failing to meet WCAG standards with material and this is something we purchased Storyline specifically to achieve.  

Ashley Terwilliger-Pollard

Hi Martin,

#1 - I was able to replicate an issue where the JAWS screen reader reads the course title even if it's disabled in the Player features. So I'll include this discussion in that report with our team. It sounds like you're running into that, and perhaps a bit more in that every slide is reading it? 

#2 - I don't have an ETA on this fix yet, but I'll keep you posted here as soon as I have more to share. 

I saw your earlier post on the PNG image issue, and that Leslie shared that the issue David ran into was something specific to not having any alt text enabled 

I understand if you're not able to share your file, but since it's the best way for us to demonstrate the problem and document a defect, we'd happily accept a .story project shared here privately if that is allowed per your company rules. 

This discussion is closed. You can start a new discussion or contact Articulate Support.