Tab as a Key

I'm creating a software interaction and I want to the learner to use the Tab key as a trigger. I initially had the Enter key as the trigger, but was advised the software program used Tab instead of Enter.

As it stands, the Tab key does not trigger the layer. Is it possible for me to use the Tab, or should I abandon it and go for Enter?



35 Replies
Tom Neel

Hello everyone! I have the same issue with the Ctrl and Alt keys... in my project, I want to create a trigger when the learner presses just the "Ctrl" key, not "Ctrl+ some other key"

Same thing for "Alt" (just Alt, not Alt+something else)

Is this possible?

Thanks a million, I hope you all have a great day!


Judith Blackbourn

This is for Brandon Driggers. He sent me a question by personal email, but I don't see his return email address.

Hi Brandon,

In Storyline, pressing Tab or Enter sends the focus to the Submit button. The Incorrect or Correct response comes up. The learner has to click Continue on the response message to continue. Most times, you continue to the next film cell.

Some options:

1.      When you record the simulation, do not tab between the fields – click in each field in the correct order and type the entry. This allows Storyline to capture the keystrokes from the learner without looking for a Submit each time.

2.      Keep the tabbing between the fields when you record, but realize that each time the user tabs, it activates the Submit button. This can be pretty annoying because the Incorrect or Correct response comes up each time you hit tab.

3.      You can record the simulation with the tabs, and set a trigger to move to the next scene when the control loses  focus.
Go to the slide containing the first field the learner enters. In the triggers for the simulation, add a trigger to jump to the next slide when the control (the entry field)  loses focus. You have to do this on each slide to keep the tab from activating the Submit button.

The Trigger Wizard should look like this:

Your triggers will look something like this. The arrow points at the trigger I added.

Let me know if this helps and if you need more details.

Good luck,


James Brandwood

HI Everyone,

I am having a similar problem.

I am using a trigger to hide a layer when the user presses the tab key. However when I do a slide preview, pressing the tab key not only hides the slide but it also highlights an option in the top bar. If I press tab more times it jumps around the slide navigation options.

Is there a way to prevent this from hapening? 

Peter Anderson

Hi Nich, 

Good question. You can disable the yellow box for objects on your slide, but I don't see a way to disable it for menu items or player nav buttons. I did a quick test though, and it seems that if you build a trigger (to advance to the next slide, for example), that Storyline will respect that trigger first before any of the menu or player items become highlighted. 

Peter Anderson

James Brandwood said:

Hi Peter,

I can't see a way to stop tab selecting the menu items either - which is quite supising really. Is there way to change the colour of the highlighting? I have looked through Colour and effects and couldn't see it as an option.

James Brandwood said:

Or better yet - Is thee a way to turn off accessibility features altogether?

Hi James, 

Those would both have to be feature requests at this time. And good ones

JJ Johnson

I need users to be able to tab through my simulation screeen WITHOUT Storyline going into Accessibility mode (or whatever it's called--it's a major annoyance, whatever you call it).

Is there a way to just turn off this yellow box tabbing functionality (you know what I mean) globally? If not, there definitely should be.

Samarpan Dutta

Ashley Terwilliger said:

Hi JJ,

There is not a way to turn off the accessibility features, but as you'll see Peter recommended, you're welcome to submit it as a feature request.

Hi Ashley,

We are still following the tutorial posted earlier in the forums to disable the accessibility feature for each object on every screen of our project. Just wanted to circle back to check if you have any updates on this feature request. Being able to disable this feature at a project (Story file) level would be a real boon.