Forum Discussion
Accessibility and screen readers
I'm working through and testing accessiliby for screen readers for the first time in Storyline360.
There's some things that I can't make sense of. I am testing uisng NVDA, it insists on including ...
Hi Lauren, I see this is still an active conversation. We completed a module for an external vendor, and they have come back saying there were a few accessibility issues when using a screen reader. Was hoping someone may be able to give us some guidance. We just tested in NVDA and have confirmed the issues. We have done all the focus order, removed extraneous shapes etc within storyline, so not sure what else we should do.
Here are a few examples of the issues we are experiencing:
- When they click on a button to see a text box, the text box is saying "blank" and you have to press the down arrow to continue to the actual text (we also have heard "clickable main landmark"
- When selecting some slide titles, the screen reader is saying "blank"
- When on slide titles in the menu, the screen reader is reading the incorrect title or "none"
- On our custom calculation slide the dynamic text is not being read for example "$ calculation"
Another issue is if you try to arrow down on the open side menu, it is not reading the slide names.
Hoping you might be able to guide us.
Since the file was paid for by an external vendor, I was hoping I could provide you the storyline file privately. Please let me know if this is a possibility and next steps.
I will second that these issues are present on many of my Storyline projects. They are seemingly random as well; sometimes these issues appear and sometimes they don't and there is no visible reason as to why.
