Quizzes and Accessibility- Try Again

Feb 19, 2020

Hi all,

I have a basic multiple choice question with unlimited attempts. I have removed all unnecessary tabs from the tab order. When I use a screen reader to view the question, it works great and allows me to answer. If I get the answer incorrect, it takes me to the "try again" layer (so far, so good). However, when it takes me back to the slide, I have to tab through all the slide elements. As in, it does not start me back at the "beginning" of the slide or take me to the questions.

Does anyone know if there is a workaround for this?

I essentially want to make the navigation simple for those using the keyboard by taking them to a natural slide element without having to re-tab through it all again.

File attached.



4 Replies
Aparna Kolekar

Hi, Lauren,

I am experiencing the same issue with my Multiple Choice question's 'Try Again' layer, as Shannon describes above in this thread. However, I do not have access to the short tutorial that you had shared above. I am using the most up-to-date SL360 version as well as Jaws versions. 
Can I have some guidance on this, please?

Katie Riggio

Greetings, Aparna!

In Update 41, we had a bug where the focus stayed on the player's submit button when submitting a quiz choice. That caused learners to click the Shift+Tab keys to return to the skip navigation shortcut to get back to the quiz content.

That bug has been fixed. I used Storyline 360 Update 46 to publish Shannon's Accessibility_File.story file and then uploaded the package to Tempshare. Next, I launched the output on Chrome 87 with JAWS 2020. 

Let me know if that helps!

Aparna Kolekar

Hi Katie, 

Thank you for sharing the video. It certainly helps and works for SL freeform questions whereas I was working on a custom question so it didnot work on that. However, one of our team members has come up with a workaround which works just fine for now. So, thank you once again. We will certainly reproduce the behaviour shown in the video for our other freeform questions. 

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