When navigating through quiz questions (in Storyline) using JAWS, tabbing works. However, JAWS would also say that if I want to change my answer, I can use the up and down arrow keys. Issue: It does not work. The arrow keys will not move As a result, I would tab through all the elements of the page until I get to the my new selection and press enter. JAWS' instruction to use up and down arrow keys is misleading. Tabbing through the entire page just to change my answer is also cumbersome.
Thanks so much for bringing this to our attention. I'm seeing the same thing you're describing in Storyline 360 with JAWS 18--JAWS says to use the up and down arrows to change the selection, but the up and down arrows don't change the focus. You have to use the Tab key to change the selection. To be sure, what version of Storyline are you using?
I'm going to meet with my team to take a closer look, so that we can verify this is a bug. Sometimes my team catches errors in my logic and we don’t have a bug after all. Of course if that’s the case, I’ll let you know!
I really appreciate you bringing this up, and I'll notify you as soon as I have more information to share!
Thanks for checking in, Tina! Nothing new to share, yet.
We’ll continue to keep an eye on this bug to evaluate how many customers are impacted and what impact it has on courses. The number of customers and depth of impact are two of the elements that help us prioritize bugs and fixes.
Thanks for checking in, Kenneth. No updates yet, but you're in the right place. As soon as we get more information, we'll share it here. I appreciate you letting us know this is affecting your Storyline 3 projects!
Same exact problem. On a True/False question for example, JAWS reads "True radio button not checked. To change the selection, press up or down arrow." The arrow keys do not work. Also, if I hit the space bar to select, "True," it visibly fills in the radio button but upon asking JAWS to re-read the (now checked) radio button, Jaws still reads that the "True radio button is not checked."
I need to make my projects accessible and this presents a huge problem.
Thanks for reaching out and describing what you are experiencing with your course.
As for the link shared above, you can find it here if you'd like to check out that conversation.
We do still have an open issue regarding JAWS says to use up/down arrow to move to/from answer choices on a Freeform PickOne slide. Are you using a Freeform Pick One slide in your project as well? This is an issue our team is working on.
For the second issue you mentioned, we corrected an issue where JAWS 18 kept reading "not checked" even after making a selection to a question in the HTML5 version of the content. This was corrected in Update 3 of Storyline 3.
Hi, I see the misleading up and down arrow navigation to change answers was raised a year ago, for storyline 2, 3, 360. I'm buildign a course in storyline 3 with accessibility requirements. One is a really long time for this issue to be still not resolved?
JAWS says to use up/down arrow to move to/from an answer choice, but that functionality isn't working correctly. Our team is looking into a solution, and you're in the right place to stay up-to-date on our progress.
I hope this is fixed soon. We have over 100 modules that need to be accessible and they all have quizzes using radio buttons. I figured out that I can use a workaround, by adding in the triggers that allow selections to be made using the up and down keys but that will take a huge amount of time to do in 120+ modules.
Jessi, not that this is a fix, but we created an instructional message/note that is setup to be accessible via triggers. If a person has self identified or if the system is triggered that the keyboard/tab key are the means of navigation, the message appears. The message tells the learner if you are using a screen reader, please use the tab key along with the spacebar/enter key when making a selection. To ignore using the up/down arrows.
Jessi, what action did you use on your trigger workaround. I am needing to make our quiz pages accessible.
We are required to have accessible courses also, and sent our course to a firm for an accessibility review. Using Storyline 360 quiz templates we had the some of the same issue:
Radio button group should allow arrow keys to navigate within the group, not the TAB key. (WCAG 2.1.1)
Radio button on quiz pages were not properly grouped with a label. (WCAG 1.3.1)
Our team is continuing to work on accessibility improvements to resolve known bugs such as this one and provide a better accessibility experience for learners. We're moving along well in that work, and the way Storyline is designed, we're able to make incremental improvements but will continue to aim higher to deliver more accessibility updates in a faster timeframe.
We'll keep you posted on those issues and updates in discussions such as this one!
We are facing the same issue for quizzes we developed in Storyline 360, the radio buttons can be selected through the tab but not the arrow keys. Any update on this?
As Ashley mentioned, we are continuing to work on accessibility enhancements for Storyline that will include fixes to issues like this. While I don't have an exact ETA on these updates, we are working hard to bring these improvements to Storyline.
We will be sure to keep you posted with any new updates we can share to this thread!
27 Replies
Hi there Tina,
Thanks so much for bringing this to our attention. I'm seeing the same thing you're describing in Storyline 360 with JAWS 18--JAWS says to use the up and down arrows to change the selection, but the up and down arrows don't change the focus. You have to use the Tab key to change the selection. To be sure, what version of Storyline are you using?
I'm going to meet with my team to take a closer look, so that we can verify this is a bug. Sometimes my team catches errors in my logic and we don’t have a bug after all. Of course if that’s the case, I’ll let you know!
I really appreciate you bringing this up, and I'll notify you as soon as I have more information to share!
Hi Alyssa,
Thanks for the reply. I am using Storyline 2.
Looking forward to your feedback.
Thanks,
Tina
Thanks, Tina. I'll be sure to add that version of Storyline to the report.
Hi Alyssa,
Any feedback or new information to share?
Thanks.
Thanks for checking in, Tina! Nothing new to share, yet.
We’ll continue to keep an eye on this bug to evaluate how many customers are impacted and what impact it has on courses. The number of customers and depth of impact are two of the elements that help us prioritize bugs and fixes.
Here's some more detail about how we tackle bugs. I'm really sorry that I can't say if this issue will be fixed, but you're in the right place to stay updated on this bug's progress!
Hi, everyone. I am having the exact same issue and it is impacting my ability to deliver a course to a client. Any word on how to resolve this?
Hi Brandi,
This issue is still with our team for Storyline 2 and Alyssa also reported it for Storyline 360.
We'll keep folks posted in this discussion with an update on either of these.
Hey everyone! I came across this same issue in Storyline 3. Are there any updates on this bug?
Thanks for checking in, Kenneth. No updates yet, but you're in the right place. As soon as we get more information, we'll share it here. I appreciate you letting us know this is affecting your Storyline 3 projects!
I am having a similar issue with selecting arrows as a trigger to change a variable. I really want this to work with a Makey Makey microcontroller.
Hey Bonnie!
Thanks for chiming in here and also starting a new discussion thread. We can keep the conversation going in your new thread, if you'd like!
The link to that discussion thread is broken.
Same exact problem. On a True/False question for example, JAWS reads "True radio button not checked. To change the selection, press up or down arrow." The arrow keys do not work. Also, if I hit the space bar to select, "True," it visibly fills in the radio button but upon asking JAWS to re-read the (now checked) radio button, Jaws still reads that the "True radio button is not checked."
I need to make my projects accessible and this presents a huge problem.
Using Storyline 3.
Hi Susan,
Thanks for reaching out and describing what you are experiencing with your course.
As for the link shared above, you can find it here if you'd like to check out that conversation.
We do still have an open issue regarding JAWS says to use up/down arrow to move to/from answer choices on a Freeform PickOne slide. Are you using a Freeform Pick One slide in your project as well? This is an issue our team is working on.
For the second issue you mentioned, we corrected an issue where JAWS 18 kept reading "not checked" even after making a selection to a question in the HTML5 version of the content. This was corrected in Update 3 of Storyline 3.
What update are you currently using?
Update 5 (August 2018)
Thanks Susan.
Would you be able to share your .story file with our team here so that we can take a closer look?
Hi, I see the misleading up and down arrow navigation to change answers was raised a year ago, for storyline 2, 3, 360. I'm buildign a course in storyline 3 with accessibility requirements. One is a really long time for this issue to be still not resolved?
Any updates? Thank you.
Welcome, Paula, and I'm so sorry you've come across this roadblock.
No updates yet on the first issue Leslie described above, but I promise we'll keep everyone here in the know on any new information. Here's an inside look at how we tackle bugs once they're reported!
If you don't mind sharing your .story file, we're always happy to test it to see if there's something we can suggest in the meantime!
Any update on this??
Thanks for checking in, Stephanie.
JAWS says to use up/down arrow to move to/from an answer choice, but that functionality isn't working correctly. Our team is looking into a solution, and you're in the right place to stay up-to-date on our progress.
I hope this is fixed soon. We have over 100 modules that need to be accessible and they all have quizzes using radio buttons. I figured out that I can use a workaround, by adding in the triggers that allow selections to be made using the up and down keys but that will take a huge amount of time to do in 120+ modules.
Jessi, not that this is a fix, but we created an instructional message/note that is setup to be accessible via triggers. If a person has self identified or if the system is triggered that the keyboard/tab key are the means of navigation, the message appears. The message tells the learner if you are using a screen reader, please use the tab key along with the spacebar/enter key when making a selection. To ignore using the up/down arrows.
Jessi, what action did you use on your trigger workaround. I am needing to make our quiz pages accessible.
We are required to have accessible courses also, and sent our course to a firm for an accessibility review. Using Storyline 360 quiz templates we had the some of the same issue:
Hi Jessi, Jackie and Monica,
Our team is continuing to work on accessibility improvements to resolve known bugs such as this one and provide a better accessibility experience for learners. We're moving along well in that work, and the way Storyline is designed, we're able to make incremental improvements but will continue to aim higher to deliver more accessibility updates in a faster timeframe.
We'll keep you posted on those issues and updates in discussions such as this one!
Hi Ashley,
We are facing the same issue for quizzes we developed in Storyline 360, the radio buttons can be selected through the tab but not the arrow keys. Any update on this?
Thanks,
Subrata
Hi Arpana,
As Ashley mentioned, we are continuing to work on accessibility enhancements for Storyline that will include fixes to issues like this. While I don't have an exact ETA on these updates, we are working hard to bring these improvements to Storyline.
We will be sure to keep you posted with any new updates we can share to this thread!
This discussion is closed. You can start a new discussion or contact Articulate Support.