New Accessible Player Keyboard Shortcuts not working

Can someone please take a look? Please click on the first link and try to mute the file as it plays using Command+Alt+m - just hold the Control and Alt (option on Mac) keys and the letter "m" all at once. Se if the sound mutes or not when you do that.

I have been using most recent release version 3.48. After setting the accessibility checkbox in the Player settings on a brand new file, uploaded it to Review 360. Keyboard commands (other than Shift+?) don't work:

https://360.articulate.com/review/content/88ff6a22-f88f-473c-b306-cca74ae37a59/review

That file is here on Google Drive for you to download and look at:

https://drive.google.com/file/d/1h6B0iU_UVD5aUB4TkljFPUQeqEeh4nz1/view?usp=sharing

If you do take a look then please tell me if you can get any of the Command+Alt commands to work, and what browser / OS combination you are using.

Thanks!

Hello Jeff!

I see that you've reached out to our Support Engineers in a support case regarding this issue. My teammate, Chester, has logged this as a possible software bug where the keyboard shortcuts are working differently in a Mac environment. 

We'll continue investigating this issue with our Engineers and update you in your case when we have news to share. I appreciate you taking the time to share this with us!

Hello, I am having issues with the shortcuts as well.  They sometimes work, sometimes don't work. 

I am running the latest build of SL360 on Win 10, so is my client.  Testing with preview, in LMS, Review and with/without JAWS with same results.

I also have the issue with the conflicting Ctrl + Alt + Z shortcut with Nvidia Graphics application, and changed that applications shortcut to something else which helped.

We have tested on their and my setup, with mixed results.  Sometimes the shortcut for Next works, sometimes it does not.  I also find on question pages with Submit, the shortcut won't work, sometimes does after multiple attempts or sometimes by clicking on the slide to change focus (even though focus is still on the slide). 

Perhaps their are certain conditions that we may be missing that cause the shortcuts to fail?

Thanks for any insight.

is this fixed as we still face the error Ctrl+Alt+m (Mute/unmute audio) and Ctrl+Alt+t

Can anyone update me on this? I'm ready to publish a learning module, but going through it on Review none of the accessible keyboard shortcuts are working (yes, I have checked they are on!). I did put my own shortcuts in, but I find I need to disable them on one slide (I want the learners to look at a video before moving on) and am having issues with this...

Help!

Hello Samantha, and welcome to E-Learning Heroes. 😊

Thank you for reaching out and sharing what you are experiencing. 

The issue Becca referred to above sounds like what you may be experiencing since you mentioned having to disable the next button on a slide. The following is what our team is investigating:

Accessibility Shortcuts: CTRL + ALT + . shortcut key for the next button stops working on other slides if you use a trigger to disable the next button when the timeline starts

I wanted to share some information on how we define bugs and tackle them when they occur.

Thank you, Leslie. I think Saffy at Omniplex and I have found the issue. I had disabled the player 'next' and 'previous' slide triggers, which turns off the keyboard shortcuts visibility. So I have now done a bit of 'tweaking' and added back in the built-in slide triggers. Just testing today, but looks OK so far!

Mental note to self not to use so many slide layers next time!

I appreciate the update, Samantha. I'm glad that you're headed in the right direction now.

I thought that in the USA there were legal reuirments to provide Accesible copntrols. To treat soemthing like an enhancement request is not right for these issues.

Anyone find a way to ensure that the keystrokes for CC and calling up the list of keystrokes work consistently?  I'm having lots of issues with even those two now-a-days.

I'm not sure if it's the browser (though it seems to happen in all I test), or some setting in storyline (though it seems to happen regardless of toggling menu settings)... but it's really unfortunate to not be able to reference using shift+? with any certainty. It was a great step forward toward ensuring accessible content... and now... well I just am not sure what to do. Any tips or hints would be greatly appreciated! 

Edit: anyone else that is having trouble, do you use an emulator on a mac? I am wondering if there is some keyboard binding issues...