Forum Discussion
Tabbing and disabled buttons
Hi all,
I am having problems with accessibility in my courses and think it may be a bug. I have slides which need to be locked until certain activities are completed. To do this I have disabled my custom built 'next' buttons until certain events are triggered. One problem however is when the user presses the TAB key to cycle through selectable elements on the screen they can navigate to the next button, hit enter, and proceed to the next slide. This occurs even when the button is disabled and the mouse click doesn't work (as intended).
I have attached a simple .story file so you can publish it and see an example. You should never be able to access slide 3 but the bug allows you to. I also know you can prevent elements from being accessed with the tab button and this is currently how I have had to set my projects up (though this is not desired).
Any help would be much appreciated :)
17 Replies
Hi Nick!
We don't a regression logged in Storyline 360 Update 43 (Build 3.43.22859.0). Would you mind sharing your file with our team so that we can begin troubleshooting? You can connect with our Support Engineers here.
Thank you for bringing this to our attention!
I can verify this bug is still an issue in latest version. You don't need a shared file to verify, just add an element (shape, text box, whatever).
Add a trigger to Go to Next slide if the element is clicked.
Set the element's default state to disabled.When you test, you correctly won't be able to click the element (cause it's disabled), but you can tab to the element and then press enter to 'click' the 'disabled' button and advance to the next slide.
Not the first time a fix has been applied, only to be omitted and overlooked in future versions.Hi Shane,
So sorry you're hitting this snag, and thanks for sharing the steps you took to recreate the issue!
Here’s a quick recording of my experience in Storyline 360 Update 3.49.24347.0 after following those steps. I used a button in my test, which has the Disabled state built-in.
A few questions to help us find a fix:
- Does the problem happen during preview, in the published output, or both?
- Is it project-specific?
Would you be willing to share the troublesome file with us? It’ll greatly help our team verify whether that bug is affecting your course or if something else is happening. Simply use this case link.
Thanks Becca,
attached is a video demonstrating the bug occurring on my end.
Not overly keen on sharing the project file publicly from a confidentiality standpoint.
If you email me privately, I can share.
Thanks,Shane.
Hey Shane,
I understand, and I've opened a case with our Support Engineers on your behalf and included your video—appreciate you sharing that!
You should have an email from me sitting in your inbox! It includes an upload link so you can upload any files privately there.
Please let me know if you don’t see an email in your inbox, and I’ll be happy to send it again!
Hi,
This is still an issue in SL360, with any custom button, it only works correctly if using the inbuilt buttons.
Thanks,
Emily
HI Emily,
Sorry to hear that you ran into this snag.
Since the issue discussed in this thread have already been fixed in previous versions of Storyline, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
