Forum Discussion
Drop down list not read in JAWS
There is a drop down activity we built using the Drop down matching template but we found that the list within the dropped was not read in JAWS we tested it using both JAWS version 16 and 18. The activity was created using Storyline 360. Is there a solution kindly let us know.
Do I dare ask? How is the fix coming? Because I'm joining the boat and its starting to look a little crowded...;)
So sorry you ran into that, and we're seeing the same thing. I've reported this to my team so we can begin looking at next steps. Thanks for bringing this to our attention, and I'll keep you posted on any updates I receive!
Any update on this?
I'm experiencing the same findings with Storyline 3 and NVDA. Was not a problem with Storyline 2.
Good to know, Douglas. Thanks for sharing your findings with us--I'll add this to our report.
Hi Alyssa,
I am currently trying to replace a matching drag-and-drop question with a matching drop-down question as per the advice in this article: https://articulate.com/support/article/Storyline-3-How-to-Design-an-Accessible-Course
"Rather than a matching drag-and-drop interaction, consider using a matching drop-down interaction instead since it’s keyboard-accessible."
But I am having the same issue as stated above - JAWS doesn't read anything in the drop-down menu. Any news on when this will be fixed / is there is a work around?
Really sorry you're running into this problem too, Kara. We're still working on this bug, and I'll certainly keep you posted on any updates I receive. I don't have any workarounds to offer at this time, but I'll be sure to let you know if we discover one!
Is there any update on this? This is causing us a big issue for us.
We just got done upgrading an entire course to Matching Drop-down and republished in SL3 to overcome accessibility issues we encountered with our SL2 output due to accessibility issues and then to have this is not encouraging. Not too mention other issues we have with SL3.
Hi Erin,
Really sorry you're still encountering this issue. Rest assured it's a priority for us, as well. While we're still working on this bug, I did want to mention that we just released a number of new features and fixes in Storyline 3 yesterday. If you haven't had a chance to download that update yet, you can do so right here.
Thank you for the news that there is an Update for SL3. I'm excited to get it installed and test it out.
I am also facing same problem, I have updated my storyline yesterday, but the problem is still there.
Thanks for letting us know this bug is affecting you, Ajay. The fix for this bug was not included in the latest Storyline 3 update. We're still working through it, and we'll let you know as soon as it's fixed.
Alyssa - not to be a pain, but what is the progress on this bug? We have an active user that uses JAWS and is unable to complete the required activities. We purposely used matching drop down questions instead of drag and drop for accessibility. It has been over 5 months since this was reported.
Hi Erin,
Thanks for checking in! I'm so sorry that this bug is still plaguing you--I'm going to nudge my team on this one again. I know this is causing a headache for your user, so I'll be sure to keep you posted on our progress.
Just tested this -
IE &Chrome using Flash - reads "--- select ---" but not the list
IE & Chrome using HTML5 - doens't read anything from the drop-down and the controls for the drop-down get hosed (can't use arrows to navigate - arrows take to other parts of the player or browser) JAWS starts reading from browser control areas (I think, i wasn't sure where it was, but it wasn't in the course)
Hope this gets fixed soon!
