New in Storyline 360: Improved Player Controls

Dec 15, 2020

Mike Olivieri
By Mike Olivieri

It’s easier than ever to give your learners an intuitive navigation experience. In our latest Storyline 360 update, now the built-in player controls are more in line with the way users interact with other media players. The new player controls are not only more intuitive but they’re also more accessible, since the keyboard navigation now moves from left to right. 

You’ll notice these player improvements in Storyline’s classic, modern, and mobile players. 

Adjustable Player Settings

 

You’ll also notice that we’ve added a new settings control to the player so learners can customize their learning experience. Within the player, they can:

  • change the zoom mode to enlarge/reduce the zoom level of the slide’s contents 
  • turn accessible text on/off
  • enable/disable keyboard shortcuts 

Accessible Player Controls

Learners can now use keyboard shortcuts to access player controls to mute/unmute, replay the slide, and more, as shown in the screenshot above.

Keep in mind, you’ll need to install the update to see these changes in your new projects or in projects you republish. 

And if you use navigation slides in your courses, now is a good time to update the instructions or any screenshots to reflect these new changes.

Want to get a feel for the new experience? See it for yourself here.

And to keep tabs on Storyline 360 features in the works, bookmark our What’s New, What’s Next page.

52 Replies
Robin Wooten
over 3 years ago02/01/21 at 6:45 pm (UTC)

Again - thanks for the info on GeForce. Right now I do not have students who need the zoom adaptation. I think I will just handle it on a case by case basis and have them alter their GeForce in some way on their computers as needed. It is nice to be able to offer these accommodations if needed. Robin

Lauren Connelly
over 3 years ago02/05/21 at 7:53 pm (UTC)

Hi Olga!

Thank you for jumping into this discussion to share this with us! I understand that you aren't seeing the keyboard shortcut list appear when running NVDA. Unfortunately, I'm noticing the same on my end. You can see my test here. Link.

It looks like the keyboard shortcut menu can only be opened when the Menu is selected, or the slides in the Menu are selected. We have this logged as a software bug, and I'll add your comments to the report. We'll report back to this discussion when we have an update to share.

Again, thank you for taking the time to share this with us!

Janis Goodheim
over 3 years ago02/07/21 at 12:23 am (UTC)
I have to ask about the icon locations in the player as well. My client has had the CC and Audio icons on the far left for several years, and when they saw the placement after the seekbar, they were not happy and asked me to move it. Question: HOW DO I MOVE THE CC AND AUDIO ICONS IN THE PLAYER TO THE FAR LEFT (to the left of the seekbar)?
Olga Salinas
3 years ago02/09/21 at 2:22 pm (UTC)

Hi, Lauren,

Something else to consider while working on this fix. The NVDA reader doesn't read punctuation, so when reading the shortcuts for Display List, Next Page, and Previous Page, it doesn't announce the full shortcut. Can you build in alt text so that it does? or is there a way for us to do that on our end?

Thanks again.

Katie Stripe
3 years ago02/12/21 at 11:23 am (UTC)

Am I correct in understanding that these accessibility features are not available when a course is published as a SCORM package through an LMS?

I am using Blackboard and AT Bar and I cannot make text adjustments to the content deployed in Blackboard, this is something we have had comments about from students but we also need to deploy as SCORM for tracking purposes.

 

Is adding these features to the SCORM deployment on the road map?

 

Many thanks

Katie

Mark Klosowski
3 years ago02/12/21 at 3:18 pm (UTC)

Hi Katie,

We test with SCORM and the accessibility features are expected to work in an LMS.

Without seeing your project, it's difficult to guess what might be preventing you from using accessible text. One thing to check is whether you have Modern Text enabled (In the Design tab, open Fonts, then scroll to the bottom. Use Modern Text should be checked).

If it's still not working, please create a bug report so we can investigate it.

Leslie McKerchie
3 years ago02/23/21 at 2:22 pm (UTC)

Hi Daniel,

Great news!  We just released another update for Articulate 360 and included a few important fixes you'll see in the release notes.

The item you'll be interested in is:

Fixed: When the seekbar was set to allow dragging only after completion, learners could drag the seekbar before completion on smartphones in portrait orientation.

Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.

Louise Skelton
3 years ago03/08/21 at 5:50 am (UTC)

@staff

I have a problem.  When rise was first launched the block feature the auto colour was #FAFAFA  which was fine and I produced all my storyline slide backgrounds to that colour too, in order to make the block blend seamless.

Previously when using the modern player as I had all controls turned off no trace of the player showed, now since I have chosen to feature the accessibility option it has activated the player in white creating a border around my blocks. 

If I use the classic player with more control I do not get the full accessible control. 

I now face the prospect of having to go through all my storyline blocks and the rise insert block to change them to white or black only. Can the player not include a #FAFAFA option at least? 

Mark Klosowski
3 years ago03/08/21 at 1:30 pm (UTC)

Hi Louise,

I have a couple of suggestions that might help.

1) Accessibility controls are also available through the player's shortcut keys menu, displayed by pressing shift + ?. Even when the gear control is not displayed, learners can turn on Accessible text ctrl + alt + t or Zoom to fit ctrl + alt + z. And you, as the author, can also turn on Accessible Text by default, if you want, using one of Storyline's built-in variables:
Setting the built-in variable Player.AccessibleText

2) For the classic player, the accessibility controls only show two settings. The Zoom to fit option isn't in the list since the classic player has always supported browser zoom. The player's shortcut keys menu shift + ? also works in the classic player, so the gear doesn't need to be visible.

I have also added your comments to the feature request that we have for making the colors of the modern player more customizable.

Please reach out to me if these suggestions aren't clear, or if I've misunderstood the issue you're reporting.

Regards,

--Mark

Jordan Pipka
3 years ago05/05/21 at 5:09 pm (UTC)

PLEASE, just give us the option to choose which side we want the volume, CC, and accessibility controls on!

I don't know why you guys decided to move all the controls to the right. Before, it was nice and easy. You had your misc controls on the left side and your next/back buttons on the right. There was a nice separation between buttons, which not only looked cleaner but helped in avoiding confusion (especially when disabling the next button as it was easier to notice when it became enabled because it wasn't crowded by other buttons). Now, the buttons are all jumbled up on the right side. It not only looks messy, but you also end up moving your mouse over the other controls (and the volume pops up) on the way to the next/back buttons. 

Your players already have a ton of customization/positioning options. I don't think this would be a difficult feature to add.

Sign In to Reply