I'm creating a simulation of software that requires users enter text and press tab to jump to the next field. I'm trying to advance to the next slide after a user inputs text into a text box. They type something and hit tab, which I was hoping, would jump them to the next slide.
I've set this style up with the "enter" key , and it works 100% of the time. However the Tab key struggles, and I cant' figure out alternatives.
When I test the procedure of the Tab key to advance a slide , it works very well while previewing in Storyline, however once exported into html5 and tested, it fails every time.
It sounds like you are running into some snags when reviewing the course in IE. Thank you for the additional context and testing!
To make sure I am on the same page, I have a couple of questions for you:
Which Storyline product are you using?
Which version are you currently running?
I also wanted to add that when using the Tab key in a Storyline course, it can cause a yellow box to appear around objects in your course. This is an accessibility feature in Storyline that assists learners with screen readers, which you can learn more about here.
Are you able to share a copy of your file with us? If so, you can upload it to this thread using the Add Attachment button or you always have an option to share privately with our Support Engineers. Either way, we'll delete it when done testing.
I've done some research on the yellow boxes for accessibility. And tested what happened if I deleted the whole tab order for these objects. But didn't find it was helpful. It just put yellow boxes around the players buttons, like the seek bar and play button.
I'll see if I can upload the materials for better review.
I still think it's interesting that it works well in Chrome but not IE
Thank you for sharing that information. You can delete the tab order or stop making those items available to Screen Readers, however, you can’t remove it from the player entirely since it is an accessibility feature.
I think it is odd as well that it works in Chrome and not for IE. Let me know once you're able to upload that to our Support team, and I can follow along!
4 Replies
Seems that the tab key only faults in Internet Explorer. Chrome does advance the slide.
Again, any insight to this issue would be great thank you
Hey Richard,
It sounds like you are running into some snags when reviewing the course in IE. Thank you for the additional context and testing!
To make sure I am on the same page, I have a couple of questions for you:
I also wanted to add that when using the Tab key in a Storyline course, it can cause a yellow box to appear around objects in your course. This is an accessibility feature in Storyline that assists learners with screen readers, which you can learn more about here.
Are you able to share a copy of your file with us? If so, you can upload it to this thread using the Add Attachment button or you always have an option to share privately with our Support Engineers. Either way, we'll delete it when done testing.
Hey Vincent
It's Storyline 360 Version 3.29
I've done some research on the yellow boxes for accessibility. And tested what happened if I deleted the whole tab order for these objects. But didn't find it was helpful. It just put yellow boxes around the players buttons, like the seek bar and play button.
I'll see if I can upload the materials for better review.
I still think it's interesting that it works well in Chrome but not IE
Hey Richard!
Thank you for sharing that information. You can delete the tab order or stop making those items available to Screen Readers, however, you can’t remove it from the player entirely since it is an accessibility feature.
I think it is odd as well that it works in Chrome and not for IE. Let me know once you're able to upload that to our Support team, and I can follow along!
This discussion is closed. You can start a new discussion or contact Articulate Support.