Keyboard accessibility for the player menu and the Next button?
Sep 05, 2017
Hi,
I have just started using Storyline 360, and I'm hoping you can point me in the right direction. I am very glad to read that Storyline 360 provides full keyboard navigation.
I have two questions.
1. Is there a way to make the menu in the player keyboard accessible? In testing on my laptop, I can navigate to the menu via the Tab key, and traverse the menu items with the arrow key, but once the menu item is selected, I can't activate it. Is there a way to do that?
2. Is there a way to make the Next button keyboard accessible? I tried to set up a trigger for that, but I must be doing it wrong.
I attached a screenshot of my trigger. Is there a different way I should specify the key to activate the trigger?
Thanks!
Karen
12 Replies
Hello Karen!
Great questions :)
It's easier to visualize this one, so I put a sample course together.
You can see in my short video here that the Next button works as well as navigating via highlighted menu item. Just be sure to hit the Spacebar key to select.
Sorry, I hit enter too fast. I did not see an image attached regarding your trigger set-up. Feel free to re-attach here in the forums if you need me to take a look at something :)
Thanks Leslie! I had tried various keys, don't know why I didn't think of the spacebar. So that answers one question.
I will try again to attach my screenshot with the trigger popup.
I would like to be able to create a trigger for the master slide that would allow a learner to advance to the next slide without having to tab through everything on the current slide ̶ to use the keyboard instead of the next button. To enable someone who does not use a mouse, or can't see the screen, to navigate forward or back with ease.
In my example I have a square bracket key specified for the trigger, but ideally I think I'd use the arrow keys. Is there special nomenclature for the key field?
Hi Karen! Glad that was able to help you out.
You should be able to add the triggers for the arrows to navigate thru the slides. I would recommend placing those on the actual slides though vs the master slide.
I'm attaching my demo project as an example for you to take a look at.
Hi Leslie,
Excellent! This is just what I wanted, thank you so much!!!
Karen
No problem Karen :) Glad I was able to help you out here!
A quick update. We have learned that the arrow keys are used by the JAWS screen reader, so don't work for navigation if they are viewing the course with assistive technology that already has an assigned purpose for those keys, and we have gone back to using the bracket keys for navigation.
Leslie, I am curious about why you suggest placing the triggers on the actual slides vs the master slide. Since it's functionality we want on every slide, the master would seem to make more sense. Is there a time when the trigger won't work if it is on the master?
Thanks again for your help!
Karen
Well Karen, I'm going to be honest with you. I don't remember 3 months ago for sure and you're right, it should work just fine if you just have linear navigation.
That's the only reason I can think I may have recommended otherwise is for any branching.
I apologize if that was confusing and now wish I had finished a thought in that reply :)
TGIF!
Ha ha, no worries, I should have asked right away. And so far, I have just been thinking about linear nav, not branching, it makes total sense that with branching, going to the next slide is not always what you want! I think we'll try it in the master, and just hold the thought that for branching we would need to customize.
Hope you have a great weekend!
Karen
Sounds great Karen! You have a great weekend as well :)
I am trying the create a accessibility course, where i am finding difficult to focus the menu item through the TAB key. although i am getting the yellow border, which reads "Slide list tree view" in NVDA and reads"Blank" for the menu items.
Hello Bijan,
Looks like I responded to a similar question here. Just linking for anyone following along.
This discussion is closed. You can start a new discussion or contact Articulate Support.