Issue with restricting navigation with custom buttons and keyboard shortcuts
Jun 14, 2017
I've created a course with custom previous and next buttons. For Section 508 compliance, I've added keyboard shortcuts to these buttons so the learner can also use the left and right arrow keys to navigate.
However, I must also restrict the navigation on each slide so that the learner cannot advance to the next slide until either a) the timeline ends, or b) the interactions on the slide have been completed.
So I've followed some instructions I found on this site to set the next button in Disabled state upon entering the slide, and a trigger to change the state to Normal when the timeline ends. Then I added another trigger to try to restrict the corresponding keyboard shortcut (right arrow key) as well. The trigger I created is designed to jump to the next slide when the user presses the right arrow key if the state of the next button is Normal (which occurs at the end of the timeline per the first trigger).
This seems like it should work, but the right arrow key is allowing navigation to the next slide prior to reaching the end of the current timeline, despite the fact that the next button is in Disabled state until the end of the timeline.
I'm creating these triggers at the slide level instead of the master slide level because each slide has different conditional requirements.
I've also checked to make sure there are no "stray" or conflicting triggers that might be affecting it.
Any insights would be greatly appreciated.