Disabling accessibility when setting tab key as a trigger

Apr 16, 2019

I just realized that I have posted to a thread which is many years old but still being discussed. The thread emphasizes that when tab is used as trigger key, the navigation functions of player such as menu, next, previous etc. gets highlighted and the tab key trigger doesn't work as expected. I have been able to solve this problem using javascript and some variables. Please follow the below link to view an example.

http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/sto_1d8ib7dq02utd251sb1fb6q979/story.html

1 Reply

This discussion is closed. You can start a new discussion or contact Articulate Support.