I'm using Storyline 2. I developed an interaction in which users press the Tab key to move from field to field in a screen, but it's not working properly either in Preview or in the Published file. For some reason, the focus wanders to elements in the Storyline interface itself, such as the Resources link. Is there any way to correct this?
I've attached the interaction in question, with proprietary elements wiped out. I've numbered the fields so people can see where the Tab key should move.
FYI: The interaction doesn't work at all in HTML 5.
The Tab key is designed as an accessibility element. You can see a bit more information about that here. There isn't a way to disable that because of it's connection to accessibility.
Are you using the tab key as it's the same key used in your live environment?
Correct: The Tab key is the primary navigation method in the software I'm simulating. Guess I'll kill off the simulation and just tell people about it instead.
2 Replies
Hi Jennifer,
The Tab key is designed as an accessibility element. You can see a bit more information about that here. There isn't a way to disable that because of it's connection to accessibility.
Are you using the tab key as it's the same key used in your live environment?
Correct: The Tab key is the primary navigation method in the software I'm simulating. Guess I'll kill off the simulation and just tell people about it instead.
Thanks,
- Jennifer
This discussion is closed. You can start a new discussion or contact Articulate Support.