Hi there, I'm having some trouble implementing accessibility for my Pick Many activities. Screen readers do not seem to recognize the difference between a Normal state and a Selected state of a button I have a multiple choice question where the user can select more than one answer. I've made Normal state alt texts (Option 1, Option 2, Option 3, Option 4) and I've made Selected state alt texts (Option 1 Selected, Option 2 Selected, Option 3 Selected, Option 4 Selected). This way, a visually impaired user can know which answers he/she has already chosen before selecting the Next/Submit button. It doesn't work though and the screen reader just reads the normal alt texts. Is there a solution around this? Thanks!

Hi, Cristina. Thanks for checking in! While I don't have an update on this problem just yet, we promise to keep this discussion updated as soon as new information is available. Thanks for bearing with us, and let us know if we can be of any other help!

Hi Yuna, Do you mean a multiple response or select all that apply type question? By selecting that question type (or creating one), Storyline allows the keyboard user to select multiple answers, just like a person using the mouse (only difference is their click to select comes from a keyboard click). Our team likes to add alt text before a question like this to let a learner get some context surrounding the question (question type, number of answer, etc.). I've attached a quick video that shows what I mean (sorry for the audio quality with JAWS, but this should give you an idea). This is a plain Multiple Response type graded question.

Hi there Ria, Thanks so much for letting us know what's going on. Are you using Storyline 360? We do have an issue on our radar where changing the Alt Text within states retains the original Alt Text for JAWS. I'm really sorry this is giving you headaches, and I'm glad you reached out. Knowing how many people this affects really helps us prioritize issues. For now, try using shapes instead of buttons. For example, insert a rounded rectangle, and style it to look similar to the buttons you have already created. Add Alt Text to both the Normal and Selected states, and you should be good to go. I hope this helps, and please reach out if you need any more help!

Hi Ria and Matthew, As Alyssa mentioned, there is a bug on QA's radar about JAWS not narrating objects' states accurately. I'm sorry it's creating problems for both of you! I'd like to help each of you come up with the best workaround for your specific situations. Any chance you can attach your .story files to this thread? Or, you can create a case here, and be sure to include your .story files. Thanks for your patience!

Hi all, I have a similar problem for checkboxes: the screen reader cannot read the selected status of checkboxes. If I try this workaround, the box is not shown selected, futhermore the text in selected status is overlying the normal status. What can I do to make readble the selected status, without creating multiple checkboxes and textboxes handled with triggers?

Screen Reader Accessibility for Button States

CristinaColquho
Community Member
6 years ago
Hi all, checking in to see if this bug has been addressed yet?
SamHill
Super Hero
6 years ago
Confirming other peoples findings. Custom states with different ALT text defined will be read by the screen reader (I'm using JAWS). Storyline defined states, for example "Disabled","Selected" etc will just read the ALT defined on "Normal" state.

Creating a custom state such as "_disabled" will allow you to define an ALT of "xxx disabled" but then you lose built in features, such as setting a button to "Disabled" stops the button triggers being executed.

This issue has been around for so long looking at this forum post. The software might be able to claim compliance, but issues like this one are significant. Create a button group of 6 buttons, and you have no way of letting a screen reader know which buttons are selected and not selected unless you use a custom "_selected" state.

I put together a quick test using JAWS and just demonstrating the states.
2019-09-06_10-15-58.mp458.4 MB
LaurenConnelly
Staff
6 years ago
Hello Sam!

Thank you for sharing your findings with us! We appreciate hearing the multiple ways this feature could elevate courses and your learners experience. This is an issue that we've been looking into for awhile, like you mentioned.

We are dedicated to making it a simpler task to author accessible courses using Storyline. When we hear of any new updates, we'll report back. As of now, here is what we are working on!
SusanNabonne304
Community Member
6 years ago
Hi,

Is there any update to the bug fix? I am having the same struggle.
yunabuhrman-e58
Community Member
6 years ago
Not sure if this is the same issue discussed here, but I have a "select many" free form question. What do I need to do to have the user select multiple answers using the keyboard? For example, if I want to select A, C, and D and then click Submit, how would I do that?

thanks so much
LaurenConnelly
Staff
6 years ago
Hi Yuna!

I've built a quick course to give you an idea of how to accomplish that!
PickManyTabOrder.story2.3 MB
karenforkish
Community Member
6 years ago
Joining this thread to be sure to hear of any updates when using ALT text on the built-in selected state.

Thank you!
LauraBooth
Community Member
6 years ago
I am also joining this thread for updates on this issue!

Thanks
KatieRiggio
Staff
6 years ago
Great news, everyone!

To circle back on Ashley's post, I'm excited to share that we just released Update 34 for Storyline 360. It addresses the issue where JAWS did not read the alt text from Tab Order for objects with multiple states.

To see all the enhancements this version has to offer, follow these steps to update your software. Please let us know what you think!
CristinaColquho
Community Member
6 years ago
Thank you, Katie! Does this update also apply to Storyline 3?