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!
Hi there,
This is great new. I wanted to ask, do we still need to add the word "visited" to the alt-text in order for the button to read as visited?
I just tested it without putting "visited" in the alt-text and the screen reader did not announce it as visited.
Hello LydiaMans-3120b,
Thanks for testing that out! The button only needs to have the Visited state in order for the screen reader to announce it as visited.
If it’s still not working on your end, would you be willing to share your Storyline file with us so we can take a closer look at your setup? You can also share it privately in a support case, and we’ll delete it as soon as we’re done testing.
