Buttons automatically triggering when using tab-navigation

Hello Collin and welcome to E-Learning Heroes :)

Sorry to hear that you've run into an issue with this.

Are you using Storyline 360? We did have an issue that was corrected in an update:

We fixed several issues with triggers in HTML5 output, including on-click triggers that would automatically execute when using keyboard navigation to tab between objects, key-press triggers that wouldn't jump to the next slide when they were assigned to data-entry fields, and inconsistent hover triggers.

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

Hi Leslie,

Yes! That seemed to fix the problem. I must have missed the update. Thank you so much!

Best,
Collin

Awesome. Glad that did the trick for you and thank you for popping back in with an update :)

All of a sudden I'm experiencing the same behavior that Collin originally posted about. My Articulate products are all updated and current. 

Any suggestions?

Thanks!

Hi Janet,

I have a few questions to help me get to the bottom of this:

• Are you using Storyline 360?
• Does this happen when you're previewing in Storyline, or after the file is published?
• Do you have a sample file you can share here so we can take a closer look?

Hi Alyssa! 

• Using Storyline 360
• This occurs after the file is published
• I do have a sample project which I can post here in just a bit. 

Thanks!

Thanks, Janet. I'll be standing by!

Hi Alyssa, I updated my copy of Articulate this morning. I am no longer, thankfully, having issues. 

<sigh> I spent a lot of time testing that thing too. So am glad it's working correctly but annoyed that I took the time to troubleshoot the issue. :-)

While we are discussing tabbing behavior though, I have noticed that when I tab through my slide, and activate a layer, the focus can remain on items on the base layer even when I'm now on the layer. And I can tab through everything (depending on tab order) that's on that base layer before getting to the active layer.

How can I ensure that my focus goes immediately to the active layer, and that anything that is NOT on that active layer can't be tabbed to? Does that make sense?

Great to hear that, Janet. Thanks for the update!

Hey Janet,

I see you updated your response to include another question about tabbing on a layer. To ensure the focus goes immediately to the active layer, you'll want to enable the 'Hide objects on base layer' setting in Slide Layer Properties.

And if you still want objects on the base layer to appear in the slide layer, you'll want to copy them from the base layer and paste them on the slide layer.

Let me know if that helps!

Thanks Alyssa! I will try that out and let you know if there are still any issues.

I love that Storyline has so many layers (no pun intended!) but that complexity does keep me on my toes sometimes.

I hear you, Janet! We're all learning new things everyday. 😁

Hello!

My team and I are experiencing this bug in both Storyline v3.15.15453.0 as well as the (currently) latest update to 360. It consistently manifests itself once we publish.

Depending on the computer we test this on, the bug seems to either:

- Activate an element as soon as it has been tabbed to, but cease this behavior once "Spacebar" has been pressed at least once. (Jumping slides seems to bring this behavior back.)

- Activate an element as soon as it has been tabbed to, but only after having pressed "Spacebar" at least once in the session.

I have attached a crude Storyline file that I can confirm causes this issue when published.

Once again I would like to stress that we have tested this on both the lasted update as of today, as well as a slightly older one.

Thanks!

Hi Kolton,

Thanks for including this sample file. I published it with the latest version of Storyline 360 and tested in on Tempshare.

Could you also test this link and let me know if you're seeing the same tabbing issues you were seeing before?

Hey Alyssa,

Sorry to get back to you so late. The link works just fine on my end. I am wondering now if the bug is persistent in the storyline file itself, even if published on a newer version. Either way, we are doing a bunch of testing to try and isolate the issue on our end, so I will update you with what I find.

As a secondary thing, just to make sure we are publishing with the same settings, we are using HTML5 with Flash fallback, for LMS, on SCORM 1.2.

Interesting to note, though, is that we did try to do Flash with HTML5 fallback, which seemed to work at first, but instead caused a lot of issues with our alt-text not being read properly.

Hi Kolton and welcome to E-Learning Heroes :)

If you take a look at our version history here for Storyline 360, there has been another update since the one you shared above and that could be the difference in what you are seeing.

Thanks Leslie,

Looking at that link it was clear that not all of our development machines were running the latest build. (3.15.15581.0) Making sure we were all updated seems to have fixed the issue.

Thanks for your patience!

Thanks for circling back to let us know the update helped, Kolton! ☺️We'll be here if you need anything else!