Storyline 360 Accessibility - Focus Order and keyboard navigation

Hello, Lauren,

Yes, we tested with screenreaders, too--same experience (JAWS, NVDA). I posted this on a thread by itself--https://community.articulate.com/discussions/articulate-storyline/firefox-keyboard-accessibility-issue--and the file is accessible there. My colleague also has a support case in on this. The invisible tab stops are not in the Focus Order.

Sorry, I did not copy that link correctly. https://community.articulate.com/discussions/articulate-storyline/firefox-keyboard-accessibility-issue

Maybe this works better.

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.