Forum Discussion
Screen Reader Not Reading Button States
- 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!
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.
Related Content
- 2 months ago
- 11 months ago