Storyline 360 Accessibility - Focus Order and keyboard navigation

Hi team, 

Storyline 360 Accessibility - Focus Order and keyboard navigation

I've added text (text box) to the "focus order" that I would like read by a screen reader but don't want keyboard access to it. However some of the text (text box) is being read as "clickable" and is being highlighted when using the tab key.  How can I overcome this?

30 Replies
Jessica Moormann

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?

Leslie McKerchie

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.