Forum Discussion
NVDA issues in Storyline 360
Hi Vic, Yes, this seems very similar to me. The frustrating thing is that there doesn't seem to be any workaround to the issue(s). Thank you for submitting a support case. I am using the same version of Storyline as you.
Rolling Storyline back to the December version (95 I think) seems to work but obviously it's not ideal 😕
Hey Vic,
I figured out our problem - We were using custom Previous/Next buttons on each page and the reader didn't like these. I took them out and everything worked. Not ideal and I let Storyline know it's a bug. But if we only use the previous/next buttons in the accessible player everything seems to work.
My guess is NVDA doesn't like all the extra Javascript event handlers. Not sure, but sounds like these issues have been around for a while with NVDA and JS event handlers are the culprit in most cases. Not sure how that might help you.
Hi TomSchultz-1340,
Thanks for bringing this to our attention. I see my teammate, Luiza, is working on your case. They'll be in touch shortly!
Actually, there are still some issues - a colleague tried putting text box "buttons" on another layer and calling them when the timeline starts which seemed to work for him and when I took his file, saved it from my storyline, published it from my storyline it worked as well.
However, when I tried to do the same thing in my file, it was problematic. Not sure what this suggests, however. It seems like it can't be my computer as I could save and publish his file from my computer and have it work, but if I tried using the same trick as him and publishing from a separate but identical copy of his file it didn't.
Not sure if there is just some inconsistency in all of this but I can't seem to find a consistent thread through all of these issues. Hopefully Articulate will have an answer.
I am on Windows 11 Pro, Version 10.0.16100 currently. (for Articulate's benefit)
