Help needed with Accessibility tabbing not working correctly in Storyline 2

Please help!

I am working on a compliance training where a few of the slides are not working as planned for the Tab Order to comply with the WCAG 2.0 requirement. I have attached one of the slides for review.

Here is how the slide should work when

  1. Overall slide (folio)
  2. Web design icon. User hits <Enter> to show layer Web design
  3. Web design - title text
  4. Web design - text definition
  5. Web design - instruction-web design. User hits <Enter> to show layer Information technology
  6. Information Technology - title text
  7. Information Technology - text definition
  8. Information Technology - instruction-IT. User hits <Enter> to show layer Marketing
  9. Marketing - title text
  10. Marketing - text definition
  11. Marketing - instruction-marketing. User hits <Enter> to show layer Contact center
  12. Contact center - title text
  13. Contact center - text definition
  14. Contact center - instruction-contact ctr. User hits <Enter> to show layer Test center
  15. Test center - title text
  16. Test center - text definition
  17. Test center- instruction-test ctr. User hits <Enter> to advance to the next slide.

Any assistance is greatly appreciated.

3 Replies
Alyssa Gomez

Hi there Jennifer, thanks for allowing me to take a peek at your file! I see that you have the tab order set up according to the list you provided, but Storyline isn't respecting that order. 

I was planning to share your file with our Support Engineers for further troubleshooting, but I see you already submitted a case. You're one step ahead of me! I'll follow along with your case as it progresses and share updates here in this thread. ☺️

Alyssa Gomez

Hi Jennifer!

I popped into your case this morning, and I see that Renato was able to reproduce the behavior your were seeing. It appears that the issue occurs when you show slide layer by using keypress triggers. He logged this as a possible software bug. In case you're interested, here's how we tackle bugs once we log them. 

Thanks again for bringing this up, and I'm sorry it's slowing you down!