Tabbing/WCAG Accessibility

Dec 19, 2018

I have been working on two accessible courses and while I'm having no issues tabbing/adjusting the tab order as needed on the course slides themselves, I cannot seem to tab IN to the content from an LMS. For example, if I load my file to scormcloud, I can tab into the course and out of the course to the browser address bar ONLY if I'm using Chrome. If using Firefox, IE, or Edge, the course will load and I can tab within the course, but once I cycle out to the browser address bar, I can't get back into the course. This is also happening in a different LMS, not just scormcloud. Has anyone else experienced this? Tabbing is a basic necessity for WCAG and this seems to render storyline useless if I can only offer my course in Chrome. Any advice you can offer is greatly appreciated!

 

Additional information as needed:

My next and back buttons are custom. I am using the "classic" player (which doesn't really matter since all the controls are "off" and its just operating as a container) and I have a custom menu built (this was another work-around due to not being able to tab out of the course AT ALL to start, even in Chrome... but for whatever reason when I combined a custom menu with the classic player, I could tab out). 

 

Thanks!

Alana

4 Replies
Ashley Terwilliger-Pollard

Hi Alana,

I'm sorry you're having such trouble with the tab order but I'm glad you reached out! I was able to see the same issue in a sample file I created. If you want to take a look I made two versions, this one with the modern player and this one with the classic player.  Does that setup match what you're using? 

I'm going to share this with my team as a possible bug and I'll share any updates here as soon as I can! 

Ashley Terwilliger-Pollard

Hi Alana,

Sorry about that! Our links to courses are set to expire after a period of time to help clean up our systems of customer content. 

The issue is still open for investigation with our Engineers so I'll post here as soon as I have updated information to share. We haven't seen a lot of similar reports of this issue, so it may be browser-specific too. 

This discussion is closed. You can start a new discussion or contact Articulate Support.