WCAG AA and Storyline HTML 5 output

I'm very interested in anyone who has successfully published their storyline course in html5 and then tested/made changes to ensure it passes WCAG AA (2.0) conformance criteria.

We have done a lot of work in this area but generally build with straight HTML/5 i.e. when we use authoring tools, we would generally rely on the tool itself and highlight for our clients any limitations of the tool - but in this instance we need to use Articulate Storyline and plan on editing the HTML where/if necessary to ensure it complies with WCAG AA / 2.0.

So if you've done similar, any problems that arose for you? Tips?

Hope you can offer some support.

3 Replies
Ashley Terwilliger

Hi Melissa,

This discussion is quite a bit older, but we may still be able to find you some help. Are there particular areas of accessibility that you're concerned about or have run into problems with? 

To get you started, I did want to share a link to our accessibility guidelines and FAQs below:

Also, this great article on 6 Best Practices for Designing Accessible Courses, and some more detail on how to design accessible courses in Storyline 360. 

Hope that's a good place for you to start - and just let us know what else you need!