Trigger Glitch: When the user presses a key, only works after clicking on an object
Nov 14, 2019
After Storyline updated the trigger panel in the 11/05/2019 update to group triggers together, it is now forcing keyboard triggers to be assigned to an object "after clicking on ___." . I use keyboard hotkeys for vision-impaired users (N to go to the next slide, etc.).
Blind users can't be asked to click on the slide with a mouse before pressing a key. Can you please request this glitch be fixed quickly? Thank you much.
9 Replies
Hi Alan!
Thank you for bringing this to our attention, and explaining how you are using the new trigger panel! This trigger feature is intended to require users to view the content on a slide before moving to the next slide. The term "click" also includes tabbing through the course. Here is an example.
Since this feature is working as intended, I'd suggest sharing your use in the form of a feature request. I'll share your comments with our team as well to see if I can offer any additional workarounds in the meantime.
As always, we are appreciative that this community steps forward to share how different features will impact their courses! Thanks for taking the time to share your comments!
Thanks for the response, Lauren. The addition of "after clicking on this slide" in the latest update is confusing, but I see that it should still work for unsighted users only using the keyboard. Thank you for taking the time to make the video and the explanation.
Hello Alan!
I'm happy to return to this discussion with an update!
We've fixed the issue you experienced where the: Key press triggers not working unless slide is clicked / in-focus.
Be sure to install the latest Storyline 360 update (Build 3.50.24668.0) to take advantage of all the recent features and fixes.
Thanks for your patience while we investigated this! If the problem reappears, please let us know, or you can always work directly with our support engineers here.
Great! I appreciate the terminology being clarified, with the addition of "in-focus." I think that will remove a lot of confusion for people setting up keyboard triggers.
Thanks!
@Becca, this issue resurfaced with the lastest SL build 3.50.24832.0. The user is forced to click some object before the pressed key fires an action. In my example, I have to click some object before the key combination CTRL + C is invoked. Please see attached screenshot.
Hello Artur!
I'm happy to help! I've tested this on my end using the same trigger, and I can see the layer without clicking on an object. I'm using Storyline 360 (Build 3.50.24832.0) as well.
Do you see this with every project, even a new project? It would be helpful to take a look at your file if you don't mind! You can upload it privately in a support case. We'll let you know as soon as we receive it! Also, we'll delete the project after troubleshooting.
I came to this tread because I saw the the keyboard trigger requesting I set an object to be clicked. After reading Becca's comment about the slide just having to be 'in-focus' and not 'clicked', it helped me to understand what was happening.
I setup a test to play/pause the timeline by pressing P and it works without having to click anything. I feel updating the language used in storyline from 'clicked' to 'in-focus' could help other from thinking they've hit an issue.
Hi. I'm working on a slide that simulates a screen reader. When the user clicks on a text entry field, for example, a piece of media plays. Works just fine for someone using a mouse but doesn't work for someone navigating using the Tab key. The only event based on focus is "loses focus," is there a workaround for triggers based on keyboard navigation?
Hello Olga,
Happy to chime in!
Unfortunately, there isn't a keyboard event equivalent to the 'When user clicks' mouse event in Storyline 360. Tabbing is mainly used for screen reader functionality and not for triggering interactions on a slide.
I'll let other members of the community chime so they can share how they were able to address design requirements similar to yours!