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 John,
Good to see that the statement I was quoting is back in your post now. Your explanation is indeed a plausible rearrangement of your original words, except for a few confusing elements:
1) In your explanation today, you said “that would require a custom design (if possible) to meet conformance”. I can’t say it was clear from your original post that you were talking about a custom design by the Articulate software engineers. However, if that’s what you meant, wouldn’t that also apply to the second criterion I mentioned (3.1.2 Language of Parts)? It’s just strange, in this case, because you gave a different rationale for not supporting that criterion, which was that it is “a specific scenario that is not common”.
2) If the fact that it’s not currently supported is the explanation of why you originally said it “would require a custom design, which we could not support”, isn’t this also the case for each and every feature request submitted for Storyline 360? If so, why would you mention it in relation to this specific request? And I'm not sure if your statement intended to indicate that each and every feature request/"custom design" is something that you "could not support", but that is how your explanation is coming across. Can you please clarify?
3) Your original post said "Yes, Storyline 360 meets AA conformance due to the details of these criteria". Could you please explain to me how Storyline 360 conforms to AA accessibility guidelines, when Storyline does not currently support Criteria 1.3.5 (Identify Input Purpose) and 3.1.2 (Language of Parts)? This is the critical part of your original statement that I am still confused about.
Lastly, you mentioned that the feature request submitted by Leslie is to “support autocompletion in text entry fields”. As per my explanations above, the request is actually for Storyline 360 to support the declaration/identification of the input purpose of text entry fields (which in turn allows screen readers to determine their purpose and allows browsers to auto fill fields accurately). Could you please clarify the exact wording of the feature request that has been recorded at your end, just so that we are all clear on what is actually being requested? The reason the wording is important is because 'supporting auto-completion' sounds like just a nice-to-have, whereas identifying input purpose on text-entry fields is critical to WCAG 2.1 AA compliance.
