Forum Discussion
Screen Reader Not Reading Button States
Hey everyone, I noticed that after the last couple of Storyline 360 updates, my screen reader (JAWS and NVDA) no longer reads the alt text for button states. For example, I added "visited" for the alt text under the button's Visited state. This used to work fine but now the screen reader does not read the "visited" alt text and just reads the alt text for the normal state. My screen readers are up-to-date. Has anyone else experienced this?
Hello Kenny,
Sorry to hear that you ran into this snag.
We are currently tracking a known issue where the visited state of buttons or shapes is announced/read intermittently by JAWS or NVDA. I've added this ELH post to the bug report so we can notify you as soon as any new updates are shared. Just to confirm if you are being affected by this bug, would you mind replacing the button in your course with an image file that has similar states and 'alt text' and let me know if your screen readers will now read the states correctly?
Hey Jose,
Thanks for confirming this issue. I did import an image file and the JAWS screen reader did state "visited" on the Visited state whereas the button does not.
Hi Kenny,
Thanks for sharing what you see on your end! Unfortunately, this confirms that you're also experiencing the reported bug. We'll let you know when this is fixed and the button's Visited state is read as expected.
In the meantime, I'm sharing this information on how we tackle bugs.
Thank you, Kenny!
Creating a custom visited state and adding a trigger to change buttons to this state when clicked seemed to work for me.
Hello,
Just checking in to see if this bug has been resolved? I seem to be experiencing the same issue with a few slides in one of my files. Or does anyone know of any work arounds?
Thanks!
Hello Hannah,
Thanks for checking in. I don't have any updates regarding this bug yet. Have you tried Mzwandile's workaround above to see if it will also work for you?
You can also connect with us in a case and share your Storyline project privately so that our Customer Support Engineers can provide targeted help.
Hello was this ever resolved? I'm having this problem for the first time today.
