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!

KellyAuner's avatar
KellyAuner
Staff
12 months ago

Hi Vic,

Thanks for reaching out!

I'm sorry to hear you're experiencing this issue. Currently, I don't have an update on this bug. MzwandileMas281 shared a workaround which was to create a custom visited state and add a trigger to change buttons to the state when clicked.

Please let me know if that helps! I've added you to the bug report so we'll update you as soon as we have news of a fix.

Vic's avatar
Vic
Community Member
12 months ago

I tried a custom visited state and it did not work - same problem. :(
For this interaction I am also not able to use images for the buttons for various reasons.