It feels unintuitive to ask the user to click the player's "next >" button when there is button interaction on the slide. We also don't want to user to advance until the buttons are interacted with, so some conditions are needed anyways.
Is there a reason to keep the player's "<prev next>" navigation at all for accessibility? They also have to tab through all the other player features to reach it, versus a button where we can control the focus order.
Personally, I think it is unintuitive to ever have a next button, unless you are reading an electronic book. If there are are interactions on a slide, after the last one is finished, it's time to move on,. This can be either by choosing from among the options of where to move, or indicating feeling finished with the current interactions.
I believe accessibility guidelines apply to how the learners can move on, not where they can move.
1 Reply
Personally, I think it is unintuitive to ever have a next button, unless you are reading an electronic book. If there are are interactions on a slide, after the last one is finished, it's time to move on,. This can be either by choosing from among the options of where to move, or indicating feeling finished with the current interactions.
I believe accessibility guidelines apply to how the learners can move on, not where they can move.