Forum Discussion
Screen Reader Not Reading Button States
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!
Any updates on this? Does this behavior only apply to buttons?
Hi RebeccaSiahaan-!
Sorry to hear you've also run into this setback!
This Storyline bug affects the visited States of buttons, as well as shapes. Causing intermittent dictation by the JAWS and NVDA screen readers. I don't have any updates to share at the moment, but I've included your voice in the bug report. We'll be sure to notify you as soon as a fix is in place.
Thank you for your patience. I'm sorry if this has been slowing you down!
Ok. Thank you! I'm trying to pinpoint guidance for my team as to when we can leverage states to signify something to screen reader users and when we won't be able to. For instance, does this impact inserted images (.png, .jpg, etc.)? I could swear I recently heard NVDA read states - maybe it was just an intermittent thing.
