27 Replies
Kara Campbell

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?

Erin Flage

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. 

Alyssa Gomez

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. 

Erin Flage

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. 

Joe Waddington

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!

Kathy Kenyon

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!!