Keyboard use of Next button doesn't evaluate conditions
Jul 23, 2019
I've noticed that the Next button of the player, which I've applied conditions to in order to reveal layers, behaves differently when it's responding to the user clicking a mouse than it does when it's activated by the keyboard.
Specifically, in the attached file, using a mouse to press the Next button allows evaluation of the conditions and the file behaves as it's supposed to (revealing layers in sequence).
Using the keyboard (tab and then spacebar), pressing the Next button does not evaluate the conditions, revealing all layers at once and then instantly moving to the next slide.
Why is there a difference? Is this a bug? Can I expect to not be able to use the player buttons to reveal layers if the design needs to be accessible?
This discussion is closed. You can start a new discussion or contact Articulate Support.