Forum Discussion

RiaFernandez's avatar
RiaFernandez
Community Member
9 years ago
Solved

Screen Reader Accessibility for Button States

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 bu...
storyline 360
  • KellyAuner's avatar
    KellyAuner
    4 months ago

    Hi, all!

    I have some great news to share! We just released a new version of Storyline 360 (Update 103), which included a fix for the issue where screen readers didn't always announce the visited state of buttons or shapes.

    To take advantage of this update, simply launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find step-by-step instructions here.

    Please let us know if you have any questions by posting here or reaching out to our Support Engineers directly. We'll be happy to help!

JackieWaskew168's avatar
JackieWaskew168
Community Member
6 years ago

Hi Susan, we are experiencing the same issue and opened a case. JAWS reads any custom state we create and apply alt text to, but it does not read the alt text of the built-in state (aside from the normal state). So if we use the Visited state, add alt text, apply a trigger to change it to visited once clicked, tab to trigger it, tab back and only the normal state alt text reads. However the same steps work successfully for custom states.

  • SusanNabonne304's avatar
    SusanNabonne304
    Community Member
    6 years ago

    Thanks Jackie. Sorry you are having the same issue but I am glad I am not alone. Looking forward to Storyline being fully accessible.