WARNING: Accessibility bug in Storyline (WCAG/508 compliance)
Nov 05, 2016
For those of you who think you have created an accessible course in Storyline, I urge you to test your published courses using a screen reader. There are two important bugs you need to be aware of as they may have caused you to breach your contractual obligations in relation to WCAG 2.0/Section 508 compliance (not to mention being extremely frustrating for your learners who rely on screen readers).
Bug #1: If you add Alt text to a button after adding a state, the Alt text doesn't work.
Bug #2: If you update Alt text on a button after adding a state, the Alt text doesn't work.
I've created a video demonstrating these bugs. Click the image below to watch it.
Articulate are aware of these bugs. While we await a bug fix, the only workaround is to do the following:
- Ensure you add Alt text before adding states.
- Do not attempt to duplicate a button and then update the Alt text on the subsequent buttons. Create all buttons from scratch.
- If you need to update the Alt text on a button at a later stage, ensure you delete the button and recreate it (and all its states and triggers) again from scratch.
This workaround is extremely tedious and time-consuming, but at least it's better than finding out that your course is not accessibility compliant!
Please test your published courses using a screen reader (you can download a free one here) and reply to this post if these bugs have impacted on any of your work. Hopefully we can get them bumped up the bug priority list!
This discussion is closed. You can start a new discussion or contact Articulate Support.