Forum Discussion
Storyline 360 not compliant with WCAG 2.1 AA accessibility guidelines
Hello everyone,
I have some great news to share! We just released another update for Storyline 360. In Update 100,we have included essential fixes and new features. One of the new features we’ve included is:
- Improve the accessibility of your content. Get actionable feedback based on key WCAG guidelines to instantly identify barriers like missing closed captions and disabled course playback speed.
Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You’ll find our step-by-step instructions here.
Please let me know if you need additional help.
Hi Luciana,
I see you’ve marked this thread as ‘Solved’. However, your post doesn’t confirm whether Storyline 360 now has the capacity to declare the purpose of a text entry field so that it can meet WCAG criterion 1.35? This was the point of my original post, and three years ago, Leslie from your team escalated this as a feature request. Has this feature now been added? You can read about this request in more detail in the following post within this thread:
https://community.articulate.com/discussions/discuss/storyline-360-not-compliant-with-wcag-2-1-aa-accessibility-guidelines/829728/replies/829738
If this feature has now been added, that’s great. But it wasn’t one of the features mentioned in your latest post, so could you please clarify this, and explain the steps for how we can now declare the purpose on a text entry field?
If this feature hasn’t yet been added, please unmark this thread as ‘Solved’ as this means that the point of this thread hasn’t yet been addressed. That is, if Storyline 360 doesn’t have the capacity to meet WCAG criterion 1.3.5, then it still can’t claim to support web content accessibility guidelines.
Hi KurikoA! Sorry if this update caused any confusion! We highlighted this discussion to share the news about the Accessibility Checker, and when we post updates like this, we typically use the "Mark as Solution" feature so it appears at the top of the thread for better visibility.
That said, we haven't modified text entry fields specifically in this update. I’m happy to remove the "Mark as Solution" tag to eliminate any confusion.
