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

LaurenConnelly
Staff
5 years ago
Hi Ludovic!

I've noticed the same issue that you mentioned! The state isn't read off when the button changes to the visited state. We've logged this as a bug so that our Engineering team can begin investigating.

I'm so sorry this is affecting your course! I'll link this discussion to the report and we'll make sure to post in this thread when we have a fix.
LaurenConnelly
Staff
5 years ago
Hi everyone!

I just wanted to share that we've released more accessibility enhancements today in Storyline 360 Update 41 (Build 3.41.22450.0)!

You can see all the fixes and feature released here! Thank you everyone for taking the time to address these bugs. It's always exciting to release a fix.
KatieRiggio
Staff
5 years ago
Another great update! 📣

Update 11 for Storyline 3 is live: We fixed the issue where JAWS would only read alt text of the Normal state.

Tour the release notes for more details

Take these steps to update Storyline 3 and see the latest enhancements

As always, we're here for any questions!
shimz
Community Member
4 years ago
Hi there,

Can anybody guide me how accessibility feature works with button states and layers on slides? for screen readers?

I could'nt see my selected state in focus order of the slide.

please help. Thanks in advance
RenGomez
Staff
4 years ago
Hi Shim,

Happy to help clarify here. Different states of an object aren't included in the Focus Order since screen readers automatically announce states for interactive objects. This article shares more:

Storyline 360: Slide Content Is More Accessible

Interactive objects are correctly identified to assistive technologies and function as expected. For example, screen readers properly announce radio buttons with their labels and current states.

Can you share more about what questions you have on layer objects? You'll notice they appear on the focus order and are read by a screen reader when the layer is visited.
- shimz
  Community Member
  4 years ago
  Yes, I saw layers text in focus order.
  
  Thanks.
- shimz
  Community Member
  4 years ago
  Just a quick question.
  Do we have to alt text for the onscreen text as well for the screen reader
  to read or is it for only images and objects?
  I have attached the picture here.
- shimz
  Community Member
  4 years ago
  I am working on a course to make it accessible.
  I am adjusting focus order now for the screen readers.
  I made my learning outcomes with button states. When the learner selects
  button(Outcome 1) the text would appear.
  So, my question is that I was looking at focus order where I didn't find my
  text of learning outcomes. So I am really confused, Should it be there or
  not? How will the screen reader find it?
  HELP! See the attached screenshot.
  Thanks
  - LaurenConnelly
    Staff
    4 years ago
    Hello shim!
    
    I'm happy to clarify! You don't need to add alt text for onscreen text, but every image should have alt text. The text box should be displayed in the Focus Order. If you're using a custom Focus Order, you might need to add the text box to the list. Here's how to do that.
MariaCS
Staff
4 years ago
Hi, Shim.

As Lauren explained before, the onscreen text doesn't need alt text.

Susan also brought up the subject of alt text for different states. This can be accomplished through the Size and Position window when editing the different states:

Storyline 360: Adding Alternate Text for Screen Readers - Using the Size and Position Window

Let me know if this helps!
MariaCS
Staff
4 years ago
Hi, Susan.

I did a test with the alt text on two different states, and here's a short (less than 1 minute) recording of what I experience with JAWS.

Let me know if this answers your question!
- SusanNabonne304
  Community Member
  4 years ago
  Thanks for taking the time to do this. I was not clear in my comment. I meant AUTOMATICALLY with editing the alt text for the state. In other words, it does not seem to read the built in state such as "visited, or "selected"
  - LaurenConnelly
    Staff
    4 years ago
    Hello Susan!
    
    That is correct. The states aren't automatically added in the alt text for each state. I'm happy to share this with my team in the form of a feature request. I'll update you in this discussion when it's added to our feature roadmap.
MouginCatherine
Community Member
3 years ago
Hello,

The alt text in visited state is read, only if you have also changed the alt text in the normal state. It is a bit strange.
EphraGraham-e1e
Community Member
3 years ago
Hi there,

I'm not sure if this issue is still active but I am having trouble getting both JAWs and NVDA to recognize the visited state of buttons. It is my understanding that the reader should recognize and say "visited..." and then the name of the button (or something like that). Unfortunately, this is not happening. Is there a recommended workaround? Perhaps adding the word "visited" to the alt text for the visited state of each button. This is not ideal but I need a workaround in order to complete the course I am developing.

I welcome any and all suggestions.

Thanks for reading.
WilbertMariano1
Staff
3 years ago
Hi Ephra,

I see that you were working with Renato, one of our Support Engineers, and he sent an email yesterday regarding the details of this issue.

We've reported it and promise to notify this discussion with any changes.
- EphraGraham-e1e
  Community Member
  3 years ago
  Sounds great; thanks so much.
  
  Ephra