Accessibility - Player buttons

Jul 05, 2016


I am creating a course which has default player, and need to be accessible by pressing the tab button on keyboard.

I am having a issue that if I remove the default Prev & Next buttons from 1st page of the course and if I tab to navigate through the slide the tab order works correct and goes through the slide content and then on the player navigation buttons (Prev, Next, Audio, Menu, Glossary, Resources).

But when I go to next slide it goes through the content on screen and then to Prev & Next buttons but don't go to Menu, Resources and Glossary tabs on the top right of the player.

If I enable the Prev & Next button on 1st page then there are no issue the navigation works as intended.

Is there any solution to remove the Prev & Next button from 1st page and then by using the tab key on 2nd page take me to Menu/Glossary/Resources/Notes tab of the player?

Attached the output and source files for reference


7 Replies
Terry Springer

I created a test file of my own and had the same results. I even changed the state of the buttons to hidden and it still didn't work. It must be a bug.

All the courses I create are accessible by keyboard. I avoid using the Prev and Next buttons in the player and create my own custom buttons. That way I have more control over the tabbing order.

I revised your file. You'll notice that I changed the tabbing order so Next is selected before Prev. That creates one less tab the person has to make before selecting the next button to advance to the next slide.

Christie Pollick

Hi, Mayuresh -- After some additional thought, I wanted to stop in to mention that your issue sounds similar to something that has already been reported to our QA team for review. In the ticket details, the following steps are noted:

  • Go to Slide View > Slide Properties and under Slide Navigation Controls enable Previous and Next button.
  • Insert a 2nd Slide.
  • Disable Slide Navigation Controls (Prev, Next Button or both) on the 2nd Slide.
  • Go to Player > Features > Under Player tabs, disable or move the "Menu" to upper right.
  • Preview the entire project.

If this were functioning as desired, when pressing the Tab key, the yellow box (accessibility feature) should navigate through the Player Tabs (Resources, Menu, etc) on all Slides. But what's actually happening is that once Player menu is customized/disabled and Previous and Next buttons are disabled, the accessibility feature no longer works on the Player tabs (2nd Slide). The Yellow box no longer picks up the Resources, Menu, etc.

I wanted to stop in to let you know that I will be doing some additional testing on your file as soon as possible, and I'll reply here with my findings as soon as I can to confirm this is the same issue. Your patience is appreciated! 


Christie Pollick

Hi, Mayuresh -- Thanks so much and from what I have been able to determine when testing, this does appear to be the same issue. And while I am not able to share a time frame for a potential resolution, I wanted to let you know that your thread will be added to the ticket, and any updates will be shared here as they are received! 

Ashley Terwilliger-Pollard

Hi all,

I wanted to provide an update here, as Storyline 2 Update 10 was just released, and included a number of fixes which you can see in the release notes available here. The item you all may be particularly interested in is how it fixed issue where you couldn't tab through player elements when the menu and prev/next buttons were disabled. You can download the latest update here, and after downloading and installing the latest update you’ll want to republish any existing content to ensure that the updates and fixes are applied.

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

This discussion is closed. You can start a new discussion or contact Articulate Support.