Forum Discussion
Storyline 360 not compliant with WCAG 2.1 AA accessibility guidelines
I see that Articulate claims on this page that "Storyline 360 supports WCAG 2.1 Level AA, including screen readers, keyboard navigation, visible focus indicators, and more."
I'm confused though, b...
Hi Kuriko,
It sounds like the option for a custom design was not helpful in this instance, and I'll take responsibility for that thought.
As John shared, the title of the feature request is "Add support for auto-filling or autocomplete text entry fields from browser." You are correct, the input purpose is required for auto-completion, and those details are included.
You can create Storyline 360 courses that conform to WCAG, as Phil explained above:
I believe the compliance depends on which elements you use, you can create compliant courses but cannot use some elements. Which is the same in most tools and even building a web page.
If you'd like to discuss this further, I'd be happy to connect with you directly. We can continue the conversation and lessen the confusion caused here.
Hi Leslie,
I believe it’s important for us to keep the discussion within this public thread, so that other Articulate users can benefit from the information, not just me.
Thanks for taking accountability for the confusing statements provided by John earlier in this thread. If you advised him to write the statement “Yes Storyline 360 meets AA conformance due to the details of these criteria”, can you please clarify now what was meant by this?
Yes, Phil Mayor’s response above made perfect sense! However, the key issue here is that Articulate has not made it clear to Storyline users that ‘Enter your name’ text entry fields are one of the elements you cannot use if you want your course to be accessibility-compliant. In fact, Articulate’s approach is quite the opposite—by promoting ‘Enter your name’ text entry fields (here, here, here and here) and at the same time claiming that "Storyline 360 supports WCAG 2.1 Level AA" (in this obsolete article which I notice has still not been unpublished/redirected, even after I brought this to your attention 3 weeks ago). Can you see how these mixed messages from Articulate could be deemed misleading and unhelpful to users seeking compliance with Level AA accessibility?
I understand that your team did not intend to mislead users. I understand that they were simply following your advice, as the in-house Accessibility Specialist at Articulate, and that you truly did believe that Storyline was meeting WCAG 2.1 AA apart from what you believed to be two rarely used scenarios. However, now that I have explained in this thread what Criterion 1.3.5 actually relates to, and highlighted that this accessibility issue does in fact affect a large number of users, I’m hoping you can take some positive action to put things right now, and prioritise this issue that has previously been minimised.
Firstly, I would like to see the title of the feature request changed to “Allow purpose declaration on text entry fields (for accessibility compliance)”. As I mentioned in my last post, naming the feature request around auto-filling fields sounds too much like a ‘nice-to-have’, rather than the important accessibility issue that it is. Auto-filling is one outcome of implementing this feature, not the feature itself.
Secondly, can you please provide the full description of the feature request here, as it’s recorded in your system? I’d like to confirm that it’s an accurate description of the issue—just since there's been so much confusion around the definition of this criterion from your team, including yourself.
Thirdly, can you please explain your prioritisation system for feature requests, and clarify where this one sits within that priority list?
Lastly, as an interim solution until this feature request is implemented, the very least Articulate can do is be transparent with users about the fact that ‘Enter your name’ text entry fields are one of the elements you cannot use in your course if you require compliance with accessibility guidelines. This can easily be done by adding this tip to your 'How to design an accessible course' page. Can you please confirm how much time your team needs in order to do this?
