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.
Sorry that you've been affected by this as well Joe, but you're in the right place for updates when we have them to share.
Hi Folks,
I am also facing the same issue in Windows 10, IE 11 using HTML5 it reads "--- select ---" but not the list with jaws 16.
SL version which i am using is "Storyline 3 Update5: 3.5.16.548.0" please confirm if you got any solution for this issue or any possible Substitute.
Hi Malkeet,
I'm really sorry this bug is plaguing you. I'm going to bring this up to our team again, and I'll share any updates I receive!
I've used this interaction before since documentation says it's accessible, and was intending to use it for a new course. I'll hold off until we hear this has been addressed, but posting this here so I am apprised of the updates.
You're in the right place, Catherine. As soon as this is sorted out, we'll share the good news here!
Hi Alyssa,
Just adding my voice to the conversation. We also need drop-down menus that will work with JAWS. Looking forward to seeing this fixed!
Karen
Thanks for sharing your experience, Karen. I'm going to add it to our report, and we'll keep this discussion posted as soon as we can!
Hi. We are having the same issue. We followed Articulate's own instructions – Rather than a matching drag-and-drop interaction, consider using a matching drop-down interaction instead since it’s keyboard-accessible. Problem is, JAWS does not read the actual items in the drop-down list. So, the user has no idea what they are selecting. We need a fix to this and we need it urgently!!
Agree! We are working to convert legacy interactions that aren't accessible to ones that are, and this is definitely a roadblock for us.
Hi Kathy and Karen,
I appreciate you for chiming in. I hear your frustration, and I will update the team on this bug’s continuing impact. It's in the best place to get the priority attention it deserves.
