Skip Navigation problem after 8/29/17 release
Aug 31, 2017
After publishing Storyline 360 courses this week, we have noticed that Skip Navigation is not available. Tabbing goes from the last item on the slide directly to the first item in the player. We noticed this publishing our first course after the 8/29/17 updates in both Articulate Review and SCORM Cloud and have tested in IE and Chrome.
We need this functionality ASAP for our current 508-compliant courses.
I have submitted a ticket (Case # 01128432) but wanted to see if anyone in the Heroes community has noticed the problem this week.
5 Replies
Hey Margaret!
I haven't come across this issue yet, but submitting a case was the perfect move. It's been escalated and one of our Support Engineers will be reaching out to you directly soon.
Would you mind sharing one of your unpublished .story project files you're seeing this happen in so that our Engineers can do some testing first-hand? You can upload it directly to your case using this form.
Thanks for letting us know you're running into this- and I'll be keeping an eye on your case as well!
Hi, Ali!
Thanks for reaching out. We have created a sample that has the format of our actual course, and the sample we created has the same issue. I will be uploading that .story file to my case shortly!
Thanks again.
Margaret
Thanks, Margaret! I see you uploaded your file, and our Support team will reach out to you via email as soon as they've tested it. ☺️
I just wanted to follow up in case someone finds this thread via search. The problem was that we removed all of the player features below the slide. We previously had only the built-in closed caption button there but recently created our own custom cc button.
Without anything in the player below the slide (no Next/Prev/Submit buttons, cc button, seekbar, or volume control), Skip Navigation was no longer a stop after tabbing through the last item on the slide. The tab order went directly from the slide to the menu on sidebar left.
Thanks for popping back in to share Margaret :)
This discussion is closed. You can start a new discussion or contact Articulate Support.