I am working 360 and was wanting to create an accessible module, where a screen reader is used and also when the learner hits the left or right arrow key it takes them to the next/previous slide.
I have put the respective triggers in and to a point it works fine.
However if there is an element on the screen that the learner selects with either enter or spacebar or even presses enter by accident sometimes when they arrive on the next slide and press the tab key to go through the slide, the tab key starts selecting certain elements on the slide.
Thanks for sharing your file. I took a look and used the tab key and then the enter key to make a selection on your slide about how I wanted to navigate. After that, I could continue to use the arrow keys to navigate left and right. Using the tab key again started to highlight items on the slide, but that's expected based on the accessibility features of Storyline.
Let me know if I'm misunderstanding the problem you're running into! A quick screen recording of what's happening may help. Can you take a Peek of the problem? You can include the "Share" link here in your reply!
For our material, we've narrowed it down to the following: if a user presses the Enter key when the focus is on a button that has a "jump to slide" action within a trigger, that next slide then has the following characteristic -- a tab key will move from tab-item to tab-item correctly but if that tab-item has a trigger which activates based on "when the user clicks" then that trigger will activate. Seems that the tab key is simulating a mouse-click at that point.
So, in our case, we typically have two buttons on each screen in our navigation section that fall into this category: a replay button (user clicks, jumps to same slide) and a next button (user clicks, jumps to next slide). The result is that if a user employs only the keyboard to navigate (tab and enter), they will run into this problem on the second slide because they used the enter button on the first slide to activate the Next button. If they use the tab key but not the enter key (say, use the mouse to click the Next button), they won't get this behavior until such time as they use the enter key to activate the Next button. For example, first use the Enter key on slide 10, then slide 11 will exhibit this behavior.
At this point, I'm wondering if there is a work-around or whether we could publish in an older version of the software (we are getting this behavior even on old material re-published in our latest version of Articulate).
Thanks Tina - what version of Articulate are you using? Also, did you mean to share your file here (You mentioned testing on certain slides so I wasn't sure!), as it did not come through to the forum reply. I'd love to take a look...I'm more of a visual problem solver. 😉
Also, any screen recording of what you're seeing and where the tab focus is would help too. If you're using Articulate 360, can you take a Peek of the problem? You can include the "Share" link here in your reply!
Glad to hear Jonathan was able to help you out! I see the bug report that he shared with our team as well, so we'll keep an eye on that to update you here in ELH and as a part of your Support case.
Hi All, here is a screen recording of what's happening, all I did was press enter on the first slide you see rather than clicking the red start button I tab to it and press enter, from then on I am just pressing TAB and you will see it jumps slide just by pressing tab. I did find a work around to this by reverting back to using the play next and back buttons and it seems to work, however we would prefer to use custom next and back buttons on the screen.
Good news and just in time! Articulate Storyline 360 Update 12 is now available. The issue you reported on this case is one of the issues that we fixed. You can find a list of all the new features and bug fixes that we've added to Storyline 360 here.
I know this is an old thread but I am still having this issue with SL3 Update 6: 3.6.18134.0. I cannot activate hyperlinks when tabbing through and JAWS is not reading properly.
Thanks for reaching out, and smart move to open a case for this. I see you're working with Anna on our Support team to see if we can narrow down the cause.
14 Replies
Hi Martin,
Thanks for sharing your file. I took a look and used the tab key and then the enter key to make a selection on your slide about how I wanted to navigate. After that, I could continue to use the arrow keys to navigate left and right. Using the tab key again started to highlight items on the slide, but that's expected based on the accessibility features of Storyline.
Let me know if I'm misunderstanding the problem you're running into! A quick screen recording of what's happening may help. Can you take a Peek of the problem? You can include the "Share" link here in your reply!
Hi Martin, Ashley,
We're having the same issue.
For our material, we've narrowed it down to the following: if a user presses the Enter key when the focus is on a button that has a "jump to slide" action within a trigger, that next slide then has the following characteristic -- a tab key will move from tab-item to tab-item correctly but if that tab-item has a trigger which activates based on "when the user clicks" then that trigger will activate. Seems that the tab key is simulating a mouse-click at that point.
So, in our case, we typically have two buttons on each screen in our navigation section that fall into this category: a replay button (user clicks, jumps to same slide) and a next button (user clicks, jumps to next slide). The result is that if a user employs only the keyboard to navigate (tab and enter), they will run into this problem on the second slide because they used the enter button on the first slide to activate the Next button. If they use the tab key but not the enter key (say, use the mouse to click the Next button), they won't get this behavior until such time as they use the enter key to activate the Next button. For example, first use the Enter key on slide 10, then slide 11 will exhibit this behavior.
At this point, I'm wondering if there is a work-around or whether we could publish in an older version of the software (we are getting this behavior even on old material re-published in our latest version of Articulate).
Thanks! Tina
Thanks Tina - what version of Articulate are you using? Also, did you mean to share your file here (You mentioned testing on certain slides so I wasn't sure!), as it did not come through to the forum reply. I'd love to take a look...I'm more of a visual problem solver. 😉
Also, any screen recording of what you're seeing and where the tab focus is would help too. If you're using Articulate 360, can you take a Peek of the problem? You can include the "Share" link here in your reply!
Hi Ashley,
Your support staff Jonathan Reque was able to reproduce the issue and has taken out a Case #01231042 for resolution.
Thanks!
Glad to hear Jonathan was able to help you out! I see the bug report that he shared with our team as well, so we'll keep an eye on that to update you here in ELH and as a part of your Support case.
Hi All, here is a screen recording of what's happening, all I did was press enter on the first slide you see rather than clicking the red start button I tab to it and press enter, from then on I am just pressing TAB and you will see it jumps slide just by pressing tab. I did find a work around to this by reverting back to using the play next and back buttons and it seems to work, however we would prefer to use custom next and back buttons on the screen.
Thank you for posting this, Tina and Martin. I am having the same issue in several lessons I am currently working to update.
Hi all,
Good news and just in time! Articulate Storyline 360 Update 12 is now available. The issue you reported on this case is one of the issues that we fixed. You can find a list of all the new features and bug fixes that we've added to Storyline 360 here.
Here's how to install updates for your Articulate 360 apps.
thx!
Hi all
Good news, looks like the update has fixed the problem, thanks for your help everyone.
Martin
Hi Ashley,
does the solution also apply for SL3?
Hi Martin! The latest version of Storyline 3 will definitely include that fix. Are you seeing issues with your keyboard navigation in your projects?
I know this is an old thread but I am still having this issue with SL3 Update 6: 3.6.18134.0. I cannot activate hyperlinks when tabbing through and JAWS is not reading properly.
Hello, Derek!
Thanks for reaching out, and smart move to open a case for this. I see you're working with Anna on our Support team to see if we can narrow down the cause.
If you're able to share the .story file with her for testing, here is the unique upload link for your case. We'll run some tests and let you know what we find!
This discussion is closed. You can start a new discussion or contact Articulate Support.