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 Meagan,
Our team is still looking at the issue where JAWS doesn't read the alt text from Tab Order for objects with multiple states.
In the meantime, there are a few workarounds you could use:
- Manually change the alternate text of the states. (Edit state > Righ click object for each state > Size and position > Accessibility)
- Modify the alt text in the Tab Oder before adding a state to the object.
We'll let you know here as soon as we have additional updates!
If it is of any help, I've done many revisions with existing Storyline files over the past few months. I've noticed that if the object used customized states, that new state's alt text is read correctly. If it is a "native" state from Storyline, like "Selected" or "Visited", JAWS will ignore that state's alt text, and instead read what is found on the "Normal" state alt text. Due to interacting with the course to reveal information, I like to have alt text that indicates the user interacted with an object.
Ashley, are you suggesting to add alt text in the Tab Order window first, instead of "right-click"/Accessibility on each shape? Would that affect the alt text I readback for "Selected" or "Visited" states?
If you would like to see source files, I may be able to supply something.