Forum Discussion
Text NOT read by screen reader NVDA
Hi All,
We have a few activities like MCSS, MCMS, etc having accessibility. The focus order and alt text are correctly added for these. However, the NVDA screen reader does NOT read the content correctly.
The issues faced are:
- Content is skipped - The question text is skipped by the screen reader and directly jumps to the options.
- The slide name is not read(skipped by the screen reader).
- The content of the first screen is read in one go till the end.
- At times, the state of radio buttons/checkboxes is read twice.
- The results are weird/not consistent in NVDA on different machines - We tested on 10 different machines and the results were not the same for all.
- While using the articulate review link the user is stuck at the "Sign In" option at the top left.
The issues are random - not consistent.
Note:
- NVDA version: 2020.3
- The content is correctly read in JAWS.
Here is the articulate review link of one of the activity: https://360.articulate.com/review/content/f5d1c7c8-1556-4edb-a282-ccf627442a89/review
Quick help will be highly appreciated.
Thanks in advance
Shraddha
18 Replies
Hello,
I'm experiencing these same issues in which NVDA screen reader (version 2022.2) skips the content on each of the slides and only reads the player navigation buttons. Doing a search led me to this discussion. I am using Storyline build 3.66.28355.0.On slides where there is a multiple choice question, it doesn't read the question and goes straight to the response options. I am using the tab key to go from one section to the next. I tried using the up/down arrow keys, which helped, but it only reads one line at a time, and often doesn't read the entire line.
I have checked focus order and it is correct. I am viewing the course using our LMS--not Review.
Any help would be appreciated. I'm attaching the file for your testing.
Hi Martin,
Thanks for sharing a copy of your published course. Would you mind sharing a copy of your project file here or in private by opening a support case so we can take a look at how your slides are setup?
Here are some of the things that we'll be checking in your project file to troubleshoot the behavior:
- The focus order of your slides. The question text box should be one of the items that is listed here.
- The Slide Master layout that your question slides use.
Looking forward to your response!
We really require in depth video tutorials on accessibility experiences for different slide designs and interactions. We too are now on hold of releasing modules due to accessibility issues. Its hit and miss. NVDA reader does not always read the text, and still skips it at times even though the focus On settings are correctly lined up. Also how it works using video players in a slide compared to the timeline player. This is hit and miss.
@Darren: good feedback.
We have some accessibility webinars on the training site currently. We'll be doing more soon. One of the goals is to walk through how things should work with keyboard navigation and interactivity.
Outside of technical glitches, I think a common challenge is that many users don't know how to use the assistive technology like NVDA or JAWS in the same way an everyday use would. And, not all of the tech works the same way or it does have issues reading content (happens with websites, too, not just published courses).
And there is a balance between what the tools give you and what and how you need to build the content.
Hi there, I am using NVDA 2023.2 and facing similar issues (NVDA does not read texts on the slide, despite the accessibility text box being ticked. However, it does read the menu side bar, resource title, and the navigation buttons such as play, captions,...). I have published the course in our LMS, Review 360, and view it in Preview.
I wonder if there are any workaround or solutions to this issue yet? Thank you.
Hi Paige,
Happy to chime in!
For text boxes, you'll want to use the screen reader's navigation keys (e.g., Down and Up arrows) to cycle through all text. You can check out this article for more information:
Simply using the tab key jumps the learner from one interactive object to another, skipping text and images.
If you're experiencing something else entirely, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
