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...
KurikoAWow, they really deleted a reply ? Let's hope it was just an error and not intentionally.
Concerning the input field with 'Enter your name', when you publish to Scorm and put your course on a LMS, you never need an input field for that as you can get the username from Scorm. Nevertheless it is good to be aware of. A proper accessibility mode or accessibilty checker in Storyline that you can set to WCAG 2.1 AA or any newer or older version to highlight/define elements that are NOT accessible, becomes more and more a need.
Hi MathNotermans! No reply was deleted. I think the new platform and threaded replies may have created a moment of confusion. I appreciate you popping in to help here and it reminded me that we DO have an accessibility checker on the public feature roadmap for Storyline.
Great that an accessibility checker is on the roadmap. I do hope you can choose WCAG criteria to test on. As in the roadmap it only states: "key WCAG guidelines". And Articulate might have an other opinion on "key" then clients have.
