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...
Confirming other peoples findings. Custom states with different ALT text defined will be read by the screen reader (I'm using JAWS). Storyline defined states, for example "Disabled","Selected" etc will just read the ALT defined on "Normal" state.
Creating a custom state such as "_disabled" will allow you to define an ALT of "xxx disabled" but then you lose built in features, such as setting a button to "Disabled" stops the button triggers being executed.
This issue has been around for so long looking at this forum post. The software might be able to claim compliance, but issues like this one are significant. Create a button group of 6 buttons, and you have no way of letting a screen reader know which buttons are selected and not selected unless you use a custom "_selected" state.
I put together a quick test using JAWS and just demonstrating the states.
