Forum Discussion
Screen Reader Accessibility for Button States
Hi there,
I'm having some trouble implementing accessibility for my Pick Many activities. Screen readers do not seem to recognize the difference between a Normal state and a Selected state of a bu...
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.
