Hello, I have been working on making a course in Storyline 360 accessible. When I tab through, I can use the standard player buttons no problem. However, I have two custom buttons that display different lightbox slides, and once I select those and tab through to close the lightbox, I can no longer tab anywhere outside of the body of the course. I can no longer access any of the player buttons. Has anyone else encountered this or know of a solution?
Try publishing your course and then review it. The issue you are having seems to only happen while previewing the scene. Preview does exactly what you are describing where as a "Published" course seems to work fine.
Thanks Bob! I tested in scorm cloud and Review and the tabbing is better, but what is strange is that the only way to get back to the player buttons is to select the main course area through the tabbing. (For example, tab to player link, lightbox opens, tab to lightbox close x, then cannot tab to outside buttons UNLESS I tab to select the whole course area rectangle, then can tab outside of the page again.) Do you (or anyone else out there) happen to know if that is normal functionality?
My tabbing seemed to work and went back through the navigation buttons. I know there are several instances where Storyline seems to tab to something like a "skip nav" link. We recorded that in a course that just went through our trusted tester program. I would wager a guess that could be what is happening.
As for normal functionality, I'll leave that to the Articulate staff to answer. I will test it again just our designers decide to use a lightbox slide. Hopefully someone on the staff will give this a quick look.
Good luck with your course. Making everything compliant is fun. ; )
Thanks, Jennifer. I did get "stuck" tabbing on the slide stage after closing the lightbox slide. After I tested this in a new file, I found that this is a bug in the Storyline 360 HTML5 output. The Flash output appears to work correctly.
I'll share this with my team so we can move forward with finding a solution. Thanks again for bringing this up, and I'm sorry if it's causing headaches!
Jennifer, if it helps, I began encountering the same problem with the previous and next buttons after updating Storyline last week. Hitting the tab key also automatically selects answers in assessment questions, when it should only highlight them.
I put in a ticket Thursday night, so hopefully, this will be resolved quickly.
Good news, Jennifer! We recently released another update for Storyline 360, and we included a fix for the issue where closing a lightbox slide using the Tab key prevented you from navigating to next slide in HTML5.
You can take advantage of this fix by updating Storyline 360 and republishing your file.
13 Replies
Try publishing your course and then review it. The issue you are having seems to only happen while previewing the scene. Preview does exactly what you are describing where as a "Published" course seems to work fine.
Thanks Bob! I tested in scorm cloud and Review and the tabbing is better, but what is strange is that the only way to get back to the player buttons is to select the main course area through the tabbing. (For example, tab to player link, lightbox opens, tab to lightbox close x, then cannot tab to outside buttons UNLESS I tab to select the whole course area rectangle, then can tab outside of the page again.) Do you (or anyone else out there) happen to know if that is normal functionality?
My tabbing seemed to work and went back through the navigation buttons. I know there are several instances where Storyline seems to tab to something like a "skip nav" link. We recorded that in a course that just went through our trusted tester program. I would wager a guess that could be what is happening.
As for normal functionality, I'll leave that to the Articulate staff to answer. I will test it again just our designers decide to use a lightbox slide. Hopefully someone on the staff will give this a quick look.
Good luck with your course. Making everything compliant is fun. ; )
Hi Jennifer! I'd like to get a better idea of the tab order you're seeing. Could you share your SCORM Cloud link here for me to test? Thanks!
An abbreviated version of the training (just the first two slides plus the lightbox slides) can be found here: https://cloud.scorm.com/sc/InvitationConfirmEmail?publicInvitationId=22f056ca-4ef5-4a35-802c-258a2dcb42a7
Thanks, Jennifer. I did get "stuck" tabbing on the slide stage after closing the lightbox slide. After I tested this in a new file, I found that this is a bug in the Storyline 360 HTML5 output. The Flash output appears to work correctly.
I'll share this with my team so we can move forward with finding a solution. Thanks again for bringing this up, and I'm sorry if it's causing headaches!
Jennifer, if it helps, I began encountering the same problem with the previous and next buttons after updating Storyline last week. Hitting the tab key also automatically selects answers in assessment questions, when it should only highlight them.
I put in a ticket Thursday night, so hopefully, this will be resolved quickly.
Hi there Mike! I had a peek at your case, and I can see that Wilbert is testing your file as we speak. You should hear back from him shortly!
Thanks, Alyssa. I’ve been trying to get a course out for release, so I’m keeping my fingers crossed. ☺
Hey again Michael,
Just a quick note - you can edit out your contact information from your post if you'd like! Replying via email will include your signature. Thanks!
Brilliant, thanks.
Good news, Jennifer! We recently released another update for Storyline 360, and we included a fix for the issue where closing a lightbox slide using the Tab key prevented you from navigating to next slide in HTML5.
You can take advantage of this fix by updating Storyline 360 and republishing your file.
Let me know if you have any questions about that!
Hi all,
The issue in Storyline 360 where closing a lightbox slide using the Tab key prevented you from navigating to next slide is now fixed.
Please follow the steps here to update Storyline 360!
This discussion is closed. You can start a new discussion or contact Articulate Support.