Forum Discussion
Can the Pick One freeform question in Storyline be made accessible?
I am developing a course in Storyline 360 that incorporates the Pick One freeform question type. When using keyboard navigation, I can tab to the first item in the button set. However, when I use the arrow keys to navigate to the other selectable items, the object is selected as soon as it comes into focus. Is this standard behavior?
In addition, the client has requested the removal of the player frame for this project. As a result, the built-in submit button has been removed.
I have attached a file that functions similar to what I'm experiencing. I would appreciate any thoughts on how I can make adjustments for learners using keyboard navigation. Thanks in advance!
Hi PeteRix1!
Thanks for sharing your file! Happy to help with this!
It appears your design is using shapes as buttons, which is causing the behavior you reported. I suggest using actual buttons so the learner can tab through the elements. This will prevent the feedback layers from appearing until the ENTER or SPACEBAR is selected.
- Here's a quick Peek outlining the steps!
Also, if disabling the Player frame is a requirement, I suggest creating a custom button on the slide to act in place of the built-in Submit button.
- This screen recording shows how that can be built!
I've also attached a revised copy of your file, for your reference.
Please let me know if you have any more questions!
Thanks for the reply! I'll take a look and will let you know if I have any questions.
Hi Steven!
Sorry for the late reply to this.
Using shapes instead of buttons is not the cause of the issue. I'm encountering the same behavior with the buttons you created.
What is causing the behavior is having the items as a part of the Pick One button set with answers shuffled. Once the button set is in keyboard focus, using the arrow keys to navigate to another button in the set puts the item in focus and triggers the click event.
Thanks for your help!Hi PeteRix1,
Thanks for the additional information. I tested this on my end and what you're encountering is expected behavior. What you're experiencing is the equivalent of a mouse clicking on any of the objects to select them but not submit the interaction.With the mouse, clicking on an object puts them in the selected state, while when using the keyboard navigation, highlighting the objects using the arrow keys puts them in the selected mode. This is only true for objects that are part of a question slide where a selection is required. Shuffling the answers has nothing to do with the behavior, the objects still get put in their selected state whether the shuffle is enabled or not.
To recap:
- Tabbing to the choices puts the focus on the possible choices a learner can select on the slide
- Using the arrow keys puts whichever object is in the focus order first in its selected state
Has this behavior affected your slide's accessibility in any way?
