Tabbing and disabled buttons

Hi Greg,

Thanks for reaching out here and sharing your .story file, I do see that this has been reported to our QA team for review in regards to navigating with your keyboard. In the meantime, you may want to look at hiding the button until elements of the slide have occurred to allow them to proceed. You could always include a "fake" button in the meantime, that when the real button's state changes, that "fake" one goes to a state of hidden or disappears based on the timeline. 

Hi Henri,

I see that it's still an open issue in Storyline 2, but had yet to be reported in Storyline 360. Are you also using the custom buttons on your slide? I'll let you know how much test goes as well and report it to our team if I can see the same behavior occur! 

Hi Henri, 

Thanks again for reaching out here - I saw the same behavior in Storyline 3 and Storyline 360 so I've reported it to my team for additional investigation. In the meantime, I found a built in next button that was set to disabled wasn't accessible with the enter key whereas a custom button was accessible. 

Depending on priority and risk, some bugs can be fixed quickly, while others take longer to resolve. Here's more information on how we identify and tackle bugs.

I’ll let you know as soon as we have an update on this issue. Thanks so much again for letting us know about this, and I’m sorry if it’s slowing you down.

I can't believe that this was raised 2 years ago and it is still an issue. Please tell me a solution is about to be released!?!

Hello,

I have the same problem:
The button displays a layer when I press Enter whereas the button is disabled.
To correct this, I have added a condition in the trigger: if the state ot my_button is different of disabled.

I am dealing with the same issue. Also, I created a slide with multiple layers with custom buttons to navigate to these layers, but users can tab to buttons from other layers which causes many issues when they press ENTER. I would love for Articulate to come up with a solution already. Currently all items on a single slide will appear on the same Tab Order list regardless if they are on different layers or not.

I would also be interested in seeing an update that would allow audio files to play over several slides.

Hi Henry and Ryan,

Thanks for chiming in to share how this bug is impacting you. We are tracking and I've shared this with my team.

Ryan, 

With regards to your audio request, I invite you to share your idea and use-case here.

Hey, folks! We just released update 17 for Storyline 360 – check out all the new features and fixes here!

One of the fixes addresses an issue where disabled buttons would sometimes trigger with keyboard navigation.

Enjoy everything this update has to offer by launching the Articulate 360 desktop app on your computer and then clicking on Storyline's Update button. It's that simple! Let us know if you have any questions 🌟

Hey again, everybody. I'm excited to let you know that we just released update 5 for Storyline 3! It includes new features and fixes - check them all out here.

This is the same fix that Katie mentions above, but for Storyline 3: disabled buttons should no longer be accessible through keyboard navigation.

Here’s where you can download and install the latest version of Storyline 3. Let me know how you make out!

Hi, this is still happening for me in SL360 with the latest update August 18, 2020 (Build 3.43.22859.0).

Has this bug crept back in?