Forum Discussion

KennyDyer-44519's avatar
KennyDyer-44519
Community Member
2 years ago
Solved

Screen Reader Not Reading Button States

Hey everyone, I noticed that after the last couple of Storyline 360 updates, my screen reader (JAWS and NVDA) no longer reads the alt text for button states. For example, I added "visited" for the a...
accessibility
storyline 360
  • KellyAuner's avatar
    KellyAuner
    3 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!

MarissaB's avatar
MarissaB
Community Member
6 months ago

Hello,

It looks like I've also run into this same issue. Do we know if this has been fixed? Or any proven workarounds? I did try adding a custom visited state with a trigger to change button states when clicked, but it didn't work. 

JoseTansengco's avatar
JoseTansengco
Staff
6 months ago

Hi MarissaB,

Sorry to hear that you ran into this issue. 

We don't have anything new to share about the status of this bug, but I've added your voice to the report so we can notify you as soon as a fix is released. As a workaround, you can try using images as replacements for your buttons, and the interaction should work as expected. The only downside is you'll lose the press animation that's only available to buttons.