Forum Discussion
NVDA issues in Storyline 360
Have you found anything out about this? We are also having major issues with NVDA reader (and JAWS - but client is testing with NVDA) not doing several things.
- Not reading from top of slide (skipping into the middle of a paragraph or staying on "next" button)
- Even if the reader starts at the top sometimes it skips text on the page (and I have triple-checked all focus orders and they are accurate). I have also made sure I have a font hierarchy with headings and normal text throughout hierarchically.
- I understand the reader saying "blank" is a planned response, but it is not consistent throughout our pages and I can't tell why.
- NVDA reader suggests text is clickable when it isn't. For example, I had a text HTML link at the end of a paragraph (5 words) but the reader says the whole paragraph is clickable. I have tried new text boxes, tried putting the text into notepad to "take away" any background stuff and then reinserted text, tried the 'clear formatting' eraser. Nothing seems to change it
- I have a clear text hierarchy with using H1, etc. for the different levels.
- I have tried using accessible text - doesn't change anything
- Tried putting new text boxes in
- Made triply sure focus order is correct
None of these things change the end product significantly and I can't tell why. The client can live with NVDA saying "blank" at bland spaces (which NVDA says is expected behavior) but they want to make sure the reader starts at the top of each page and I have tried many things and can't determine why it won't do that.
I have not found much online or in the forums about this except this post - has there been any update on these items?
Tom, I think you are having the same problem as me... Does this sound like what is happening? I've opened a support case.
Possible accessibility bug in latest Storyline update (3.96.33815.0) | Articulate - Community
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.