Forum Discussion
Screen Reader Accessibility for 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 Ashley,
We have tried the work arounds stated above and neither work with JAWS, NVDA or VoiceOver. The alternate states do not read, even when additional alt text is added. The alt text on a state does not show in the tab order, either. Adding an additional shape on top and using a trigger/variable to set it (say, as a visited state) would work, but would also make tabbing through with JAWS (or any screen reader), a pain because there is no way to prevent the initial state from being read. Just wanted to share what we are experiencing.