Keyboard shortcuts are disabled after light box.

I have keyboard shortcuts defined with triggers on all my main slides - the triggers are defined in the slide master.

One of the triggers light boxes a "navigation instructions" slide.

If I close the light box using the red X on the top right, my shortcut keys no longer work on the base slide. However, if I click a button on the slide (to light box a different slide, for example), the shortcuts continue to work again.

This happens in Preview Entire Project as well as published to HTML and LMS.

Any ideas?

17 Replies
Ashley Terwilliger-Pollard

Hi JR,

I can't say that I've seen this behavior, but I'd like to know more about what your keyboard shortcuts for triggers are set up to do - and if during the second lightbox if you'd want/expect them to work? It may help if you're able to share a copy of the .story file here with us, and you can attach it using the paperclip icon. The forums have around a 20 mb limit for uploads, so you may want to strip it down to just a few slides.

Also, can you let us know what update of Storyline you're working on? We're currently on Update 6.

JR Lawhorne

Hi.  I'm on update 6.

I think the course itself must have the concept of "focus" within the browser window. When the course starts (when published to HTML), you aren't able to use short cuts at all. Also, if you close a light box with the red X, it seems like the slide underneath loses the "focus" just as when the course first starts.

The case where shortcuts don't work on the start of the course is not seen in Preview mode - only when published to HTML or LMS.

The light box case can be demonstrated in both preview and published.

I have attached a small file that demonstrates the behavior.

Ephraim Ross

Is there any resolution to this bug?I've just run into the same thing myself. I use a fair amount of keyboard shortcuts (accessibility focused), and whenever the learner clicks the "Next" button this steals the focus from the content and seems to break all of the shortcuts. If the learned clicks back into the frame, the shortcuts work.

Ashley Terwilliger-Pollard

Hi Ephraim, 

If they're clicking outside onto something else, that will change where the focus is and how those shortcuts will behave. Normally with the accessibility controls the user would be using the tab key to the next button, once they'd interacted with the content on the slide. 

If you're running into something that still feels like a bug, could you share a bit more about: 

  • What version of Storyline you're using?
  • How you're navigating through the slide? 
  • Is this strictly an issue in a lightbox?
  • What shortcuts are you using?

Any screencasts or examples you can share would also be helpful for our team to take a look at. 

Ephraim Ross

Thanks Ashley, I'll post a few slides of the lesson below temporarily so you can see what I'm describing in action.  I'm developing using the latest version of Storyline 360. 

I'm currently navigating between slides using the next and previous buttons, although I was hoping to start dedicating keyboard buttons to this role as well. If I'm understanding correctly, this is the crux of the issue. When a button on the player is clicked, this steals the focus from the content -- including any shortcuts?

If that's true, is there any workaround to allow users to click player controls without losing keyboard focus for shortcut keys? Does it make a different whether these shortcuts are built into the Master slide vs the Content slide?

To answer your other questions: It is not a lightbox issue at all -- but I thought it was likely the same issue at work as in this thread (keyboard shortcuts not working due to loss of focus). Apologies if that is not the case.

In the attached file, the A shortcut is used on the second slide. And numerical keys are used on the quiz slide.

I'd love to know if there's a way to make this work. I was trying to go the extra mile by creating keyboard shortcuts, but I'm wondering if I should rethink this approach.


Miriam Larson

I am having the same issue as Ephraim. I am using Storyline 3 and I had set the right and left keys on the numeric keypad to go to Next and Prev, respectively so they could be used for accessibility. Since downloading the most recent update (March 6th: 3.3.15007.0), these keys no longer work. Any suggestions?


Ephraim Ross

Miriam -- I think you might be right. I had not experienced this problem in my earlier testing. I was thinking I'd just missed it somehow, but it may be that it was just introduced in the past few weeks. I've just tested something I published prior to March 6th and I'm not seeing the same issue. Hopefully that means it's something Articulate can resolve quickly.

Alyssa Gomez

Hi Ephraim, thanks so much for sharing your file! I'd like to test it in an earlier update of Storyline 360 and compare that behavior to what I'm seeing in the latest update. I'll let you know as soon as I have more to share. 

Hi Miriam, do you have a sample file you can share with me? I'd be happy to test your file, as well. You can click here and attach the file to a new thread comment. Look for the Add Attachment button.

Alyssa Gomez

Hi there Ephraim! Thanks for your patience.

I tested your file in Storyline 360 Build 3.13.15006.0 (the latest update) and Build 3.12.14647.0 (February 1 update). 

In both tests, I was not able to use the keyboard shortcut unless I had first clicked on the slide stage. 

You mentioned that this functionality worked prior to March 6. Do you happen to have a link to the content published prior to that date?

Ephraim Ross

Hi Alyssa, I've unfortunately deleted the prior version from my account already. That said, it sounds like I must have made a mistake when testing earlier, because you're right that it's definitely not behaving the way I expected in the link you provided above.

Alyssa, do you know if there's a way to make keyboard shortcuts work while using the next/previous buttons? As far as I can tell, it is those two buttons taking the focus from the slide stage. I'd be happy with either a workaround or a potential bug fix.

Thanks so much for helping us look into this!