Player Keyboard Shortcuts

Thanks, but that is for the software, not the player!

I was referring to Next Slide/Previous Slide etc. when a student is working through a module.

Mike

Hi Mike!

I've looked around for information on this for you. So far, I don't see a list of default keyboard shortcuts for the player, itself. However, I did find out that some published files, particularly in Flash do allow users to tab through the options in the player.

It's a little tedious, but it is possible for some published files.

To test this, make sure you've clicked inside the presentation. If students hit the "tab" key on their keyboards, they should be able to navigate through the different sections of the player, including the "Previous" and "Next" buttons. Once the button or menu item is selected, hitting "space" on the keyboard should activate the object they've selected.

The selected item should appear highlighted as shown in the image above, if this feature is possible with the published file.

As I mentioned before, though, this may not work with all published files. It may also depend on how the student is viewing the file.

I certainly hope this information helps. If you're able to find any additional information about navigating through the player using keyboard shortcuts, please share!

Have a great evening,

Christine

That's a good suggestion Christine!

I have seen that before as I used it when playing with some text variables (and it is mentioned in the Section 508 compliance blurb).  You're right thought, it is very long winded and a bit painful to do it this way!

It just surprises me that Storyline would not have keyboard shortcuts for navigation when Studio certainly does.

Mike

Hi Mike,

I was just wondering if you found a solution to this because I am trying to do the same thing.

The only solution I have figured out so far is to create slide triggers for every slide. For example, Jump to previous slide When the user presses the Left key. These are kind of time consuming to add, so if you found another solution that would be great!

I realize this is an old post, but I thought it was still worth a shot.

I have a course I built last month in story line that has keyboard shortcuts. exp. left, page down, and down button go Prev Screen and right, page up and right go Next Screen, space pauses, and then tab is default to tab through. Question is i built another course today with the same template i built, and keyboard shortcuts aren't working. there are no calls/triggers for each on slide( in either of them), and to be honest i can't figure out how the first ones are even working. anyone know where this can be set at? i know it can work just how....thanks

Hi Jeremy,

I suggest attaching the triggers to some invisible shapes and then adding those to every slide in order to quickly add keyboard navigation.

i figured out what i did, im to smart for my own good. i setup a master slide look with all my triggers built into it. so when im building i don't see that there are any triggers on it unless i go into master slide view. and since my page names were different they triggers were unassigned. so just reapplyed to new names and all is good..thanks for input though, that would probably do the same thing just with hidden objects not master slide.

Awesome Jeremy! Thanks for the update and letting the community know.  Hope that you have a great day!

hi guys, I'm optimizing our projects for accessibility, all good and well, but can't figure out how the user would be able to scroll the scroll entry field scrollbar down with the keyboard. Any ideas?

hi guys, I'm optimizing our projects for accessibility, all good and well, but can't figure out how the user would be able to scroll the scroll entry field scrollbar down with the keyboard. Any ideas?

Was this ever figured out? I'm trying to optimize for Accessibility and we need keyboard triggers to move next/previous on each page. I've discovered that sometimes they work; sometimes they don't and it's completely random. It's also a giant pain to have to individually add triggers to each page of a course, but they don't seem to work at all if added from the Master slide. 

Hi Michelle

I believe that this works well since the last update, just republish any older courses to make them work also. 

Regards

Byron

Thanks for the update, Byron! And Michelle, please give that a shot and feel free to let us know if issues persist for you. :)

I have the same issue as Michelle. I currently have the latest version of Storyline (Update 6) installed and keyboard shortcuts do not work consistently for me.

Hi, David -- Thanks for your response. If you would like our Support Engineers to take a closer look for you, please use this form to submit, and I will be on the look out for your case to follow along. 

I didn't read Mike's question carefully enough, but this answer is exactly what I was looking for! Woohoo! Thank you!

Glad that this older thread was able to assist you as well Jazzmine. Thanks for popping in to share.

I understand from the above discussion that I can add navigation controls to each slide or a template for future presentations but I'm converting a lot of Studio files to Storyline for accessibility and would prefer to avoid making these changes to each slide.  Did Storyline 3 every build in keyboard shortcuts for the player that will pause/play and go to previous and next slide without requiring the user to tab through all of the content and controls?  A screen reader user often needs to pause the narration then tab through slide content then quickly start narration again with independent control. 

Hi Steve,

I really appreciate the insight you've shared here. While there isn't a keyboard shortcut for learners to play and pause the timeline independently of the tab order, I can see how that would be a useful feature for accessibility. I'd be happy to bring this feedback up with the team, so thanks for the idea!

Hi Alyssa, Was this feature ever added?

Thanks.

Hi there, Alex. Thanks for checking in!

It's not a feature of Storyline as of yet. We're tracking customer requests for this ability, so I'll add your vote to that Feature Request!

Hi Alex,