Storyline 360 Accessibility - Focus Order and keyboard navigation

Hi Maki,

Thank you for the link to your project file.

You mentioned that your colleague has a support case on this specific issue. Would you be able to share the case number with me so that I can take a look and follow along? I don't want to duplicate the efforts of the support team.

Hi, Leslie,

I can get the FireFox case number tomorrow (my colleague is out). Sorry for the two places. I thought my post was not being seen so I started a new discussion.

Thanks,

Maki

No worries, Maki. I look forward to hearing back from you so we can connect all the dots and help.

Hello, Leslie,

Here is the case number: 02981395. The engineer has logged it as a possible software bug, and they are looking into it.

Thanks, Maki. I appreciate the update and I'm happy to see that you are still working with Cleo directly.

Has there been any progress on this? This is basically a stop work issue for us if I cannot verify that non-button type items that are in the tab order are accessible with the keyboard.

Hi, Jessica! Are you referring to the specific FireFox issue? If so, I believe the engineers at Articulate are working on it. Have you been able to replicate? It seems to happen when there are videos embedded. 

It's in Chrome as well. Nothing is accessible with the tab key unless it is a clickable item (even if it is in the focus order). I'm using NVDA for my screenreader.

Here is a sample. Buttons are accessible - even if there is no trigger attached. But any other object is not accessible using NVDA and the tab keys. It skips over them unless there is a trigger attached to them. This sample has no videos:

https://360.articulate.com/review/content/fac5246a-89d3-4440-afa4-e6d4895726e7/review

I have two buttons (one with a trigger, one without) both are 'tabable.'

I have a textbox - not tabable.

Shape with text - not tabable.

Transparent shape (with alt text) - not tabable.

Transparent shape attached to a trigger (with alt text) - tabable.

I need all objects that I put in the focus order to be accessible by screen readers. So all of the above should be accessible with the tab key. Is this a recent change?

Hi Jessica,

I appreciate you chiming in and sharing what you are currently experiencing.

Prior to January 2020, screen reader users and keyboard-only users tabbed to every object on each slide. That method was technically accessible, but it was tedious. So we optimized slide navigation to make it more familiar to screen reader users and reduce the number of keystrokes required for keyboard-only users.

• Screen Reader Users:
  • Learners use their screen reader navigation keys (e.g., Down and Up arrows) to move through all text and interactive objects on the slide, listening to each item along the way.
• Keyboard-only Users:
  • Since keyboard-only users can see text and images, these objects get skipped when tabbing through the slide content. This reduces the number of keystrokes needed to navigate the slide.