Forum Discussion
Screen readers and different text in text states?
Reopening what looks like a 2-year old discussion. As far as I can tell, using a screen reader with a Storyline project, the screen reader still doesn't read text in states at all, using tab/shift-tab/arrow keys, nada. Also, in case you were thinking that you'd get around this by using layers, the screen reader must read EVERYTHING on the base layer before it reads other layers, regardless of the tab order set. This requires some pretty goofy workarounds, namely, making a text box specifically for screen readers that contains all the text that is on either the state or the other layer, placing this text box on the base layer, and putting it just after the interactive element so if the person using the screen reader is using arrow keys to navigate, they will encounter it immediately after the button/hotspot is activated. It would be so golden if there were a way to incorporate ARIA or similar into a Storyline project so that when a state changed the accessibility tree was notified that there's something new that the screen reader needs to hear.
Thanks!
- Karin
Hi Karin which version of storyline are you using in 360 latest build, states can have different text and it is read by the screen reader. Also with layers if show a layer and objects on the layer are above objects on the base layer in the focus tab they will be read first.
WOW am I glad you let me know. This solves so many issues for us. Thank
you!!Karin
Hello! I have the latest version of 360, using NVDA, and Chrome. Any ideas why my different text in different states is not being read by the screen reader? I am reviewing in review - not preview.
Thanks for reaching out, Rachel!
It would be helpful to attach your file here or provide a screen recording of what you're experiencing so we can help troubleshoot. If you prefer to keep it private, here's a link to upload it, and I'll delete once done testing!
Looking forward to your response so we can continue working on this!
