Accessibility issues when trying to test on review link

Jan 20, 2021

Hello! 

I am having problems when trying to test the accessibility of storyline projects with the NVDA screen reader. My coworker is also experiencing these weird bugs. Is anyone else having those issues?

It seems the screen reader will not read the texts automatically like it usually does. It tends to read the title of the slide and then won't read the content or say that the slide is empty. And then when tabbing to the buttons it will read the text on the button instead of the alt text. Sometimes it doesn't read the button text at all and just says "button".

Everything that needs to be accessible in the files has been flagged for it and put in the correct order. 

We tested the NVDA reader on other Web pages and it is working fine.

Last week, I didn't notice these problems.

Thank you and have a nice day,

Jocelyne

2 Replies
Shraddha Manjrekar

Yes.. We are also facing similar issues.

NVDA screen reader does NOT read the content correctly.

The issues faced are:

  1. Content is skipped - The question text is skipped by the screen reader and directly jumps to the options.
  2. The slide name is not read(skipped by the screen reader).
  3. The content of the first screen is read in one go till the end.
  4. At times, the state of radio buttons/checkboxes is read twice.
  5. 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.
  6. 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.

 

 

Lauren Connelly

Hello Jocelyne and Shraddha!

I'm happy to help! The published output in Review 360 doesn't currently meet accessibility guidelines and it's not currently on the roadmap. Instead, you'll want to publish for Web or LMS. 

Please don't hesitate to reach out to our Support Team if you're running into any issues with publishing to Web or LMS.