Forum Discussion
NVDA reading middle of paragraph on selected item
Hi everyone, I am building a course that must adhere to WCAG and accessibility standards. Doing some testing using NVDA and having some difficulties with text boxes being read beginning in the m...
Hello everyone!
I have some great news to share! We just released another update for Storyline 360. In Update 81, we've included important fixes and new features.
One of the bugs we've fixed is:
- NVDA skipped elements on layers and lightboxes and announced invalid-answer messages twice
Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let me know if you need additional help!
Hey Nicole! The issue remains. Honestly, i make almost everything text-wise on a slide to be not seen by screenreaders and put all that same text OFF the slide as well. It seems stupid - why wouldn't storyline read the text on slide. But it does a better job of reading everything off slide in full for some reason.
A workaround that works for me consistently - Either breaking up the text into two text boxes or if that doesn't make sense I add another text box to go before the text that explains the item. So if the screenreader isn't reading a question. I'll add a text box that says "Question 1" and then make the focus order read "question 1" and then the text for the question.
Note - if you run into this issue with bullets - make sure the bullets are not tabbed in at all - I typically take away all bullets then put the bullets back in.
Sorry for the long response but I have tons of workarounds to make screenreaders read properly at this point so let me know if you're having any other issues - happy to take a look!
Thank you so much for the quick reply! I've tried so many work arounds to no success. But I hadn't thought about putting it off screen! I will try that one!
Hopefully Articulate can add this to the bug list and find a solution in order to make the tool more accessible.
Thanks again! Fingers crossed that this works for me.
