Forum Discussion
Problems with keyboard shortcuts (Browser and Storyline Accessability)
I am currently working on a Storyline project that relies heavily on keyboard inputs.
That works fine except for two keyboard shortcuts:
- The first one is caused by the Storyline Accessability shortcuts:
on a German keyboard SHIFT + ß is meant to be ?, but opens up the Storyline infobox, which describes all available shortcuts. Can I somehow disable all those predefined shortcuts within Storyline? - The second one might be a bit more difficult to solve:
again on a German Keyboard, in Firefox SHIFT + # is meant to be ', but opens a search-box on the left bottom of the browser.
I did a little research and found that this JavaScript can stop the Browser to open up that search box:
<script>
var isShiftHold = false;$(document).keydown(function (e) {
if (e.which == 16)
isShiftHold = true;
ShortcutManager(e);
});function ShortcutManager(e){
This works fine when I test it as a HTML file, but it does not work if I simply create a JavaScript trigger within Storyline. I even tried putting the code in the story.html output file.
if (isShiftHold && e.which == 163) {
e.preventDefault(); //prevent browser from the default behavior
}
}
</script>
Where should I put that code to make it work? Or is there another solution to this?
Hi Stefan,
I see that you’ve reached out to our Support Engineers, and are working with my teammate, Ian. You’re in great hands! We’ll continue the conversation in your support case.
For your code that is jQuery so you will need to load that library at the same time.
Thank you Phil. That solved the Firefox issue.
Concerning the predefined storyline shortcuts (SHIFT + ß) I am in contact with Ian, who is - as Kelly already implied - doing a fantastic job. If we find a solution, I'll be happy to share it here.
Hi,
We are facing challenges in accessibility where the scores are not read out using screen reader. Since the scores are dynamically changing every time, we are unable to give proper naming for the scores. So I request to look into this issue seriously and revert back at the earliest. we have to launch this course on Monday. Kindly do the needful actions.
Variables are read by screen readers are they in the correct place in the focus order? You may need to raise a support case.
Thanks for the prompt response, The user will be getting 50,40 or 30 at the end. This course going to be launched for blind people. Unfortunately, users are unable to read their scores using screen reader (NVDA). Kindly let us know whom we need to contact for the solution.
Doesn’t really answer the question is it in the correct place in the focus order you could posts screenshots or a sample slide
Sent from my iPhone
