I have a question on WCAG accessibility in Storyline. We have been using Storyline for years to build elearning courses. We have previouly used Slide masters to build custom menus (ie. back/next, audio play/pause buttons, menu, resources, etc).
My question is "Can courses developed in this way not using the default Articulate Storyline player controls be WCAG 2.1 Level AA accessible?".
I'd love to hear the community's thoughts on whether this is possible given how Storyline exports to HTML5.
Additionally, I'd like to share this article on the WCAG Guidelines that Storyline 360 Supports. If the navigation is consistent and navigable, I'm sure you can meet conformance. Have you tested one of your courses with a keyboard or screen reader? If so, can you share so that we can better understand and assist?
I understand you're looking for community input on this. I'm curious to hear what they will share!
It really depends you should have a seekbar and a method to switch off the audio. Also the skip navigation feature will not be available. IT is possible and achievable the player just makes it easier
Thanks Luciana... I don't have anything to share at this stage but will share when we get to that stage.
I reviewed the "How to design an Accessible Course" link you provided... its a great resource! Most of these items in this article I will address in my course design without question. There are two elements mentioned in this article which I'm curious as to whether I could replicate in a Storyline project with a custom-built interface. They are:
1. Allow Learners to Skip Player Navigation Elements - If you've built custom navigation elements (ie. back/next, play/pause, menu, etc), can you also create a skip navigation button that functions similar to the one turned on by default for the default Storyline player controls?
2. Increase the Player Font Size - If you've built custom navigation elements, can you also create this custom functionality?
5 Replies
Glad to hear you're looking to create a course that conforms to WCAG in Storyline 360!
I'd like to share an article that can help you get started as you are developing:
I understand you're looking for community input on this. I'm curious to hear what they will share!
It really depends you should have a seekbar and a method to switch off the audio. Also the skip navigation feature will not be available. IT is possible and achievable the player just makes it easier
Thanks Luciana... I don't have anything to share at this stage but will share when we get to that stage.
I reviewed the "How to design an Accessible Course" link you provided... its a great resource! Most of these items in this article I will address in my course design without question. There are two elements mentioned in this article which I'm curious as to whether I could replicate in a Storyline project with a custom-built interface. They are:
1. Allow Learners to Skip Player Navigation Elements - If you've built custom navigation elements (ie. back/next, play/pause, menu, etc), can you also create a skip navigation button that functions similar to the one turned on by default for the default Storyline player controls?
2. Increase the Player Font Size - If you've built custom navigation elements, can you also create this custom functionality?
Kind regards,
Matthew.
Number 2 will still work, number 1 will not
Sent from my iPhone
Thanks for all your input Phil... I really appreciate the quick responses!
M