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!
The post about screen readers not recognizing the assigned state of shapes is 6 years old and still a problem. I am currently working on shapes that function as buttons with normal and visited states and screen readers are still not recognizing the states. Any chance of this being addressed finally? It makes the functionality inaccessible for some people.
Hi Heather (and anybody else this might help). A solution that can *sometimes* work, is to ensure that the default state of the element is defined in the Focus Order panel.
For example, the buttons Normal state text. I'm not sure why this has an impact, but it does. I can then have a custom state, and append the word "viewed" or "completed" to the ALT text in that state and it will be picked up by a screen reader.
There are still some sets of buttons that refuse to work, and I can't fathom why, as the set-up is identical.