Storyline 360 not compliant with WCAG 2.1 AA accessibility guidelines

Hello Kuriko,

I'd be happy to answer the questions that you have here.

Q: Could you please clarify if the report is now outdated and if any recent improvements to the software allow it to meet criteria 1.3.5 and 3.1.2?

A: The link to the pdf report you've shared is outdated. You can find the current version on our website: Articulate Storyline 360 Accessibility Conformance Report

We do highlight these two exceptions as you mention: Notes: Storyline 360 output supports or partially supports all applicable WCAG 2.1 Level AA criteria, except 1.3.5 Identify Input Purpose and 3.1.2 Language of Parts.

Q: Is Storyline 360 compliant with WCAG 2.1 AA?

A: Yes Storyline 360 meets AA conformance due to the details of these criteria. The first one would be a custom design, which we could not support, and the second one is a specific scenario that is not common.

1.3.5 Identify Input Purpose
Storyline 360 does not support programmatic input-field identification or auto-filling forms.

3.1.2 Language of Parts
You can set the course language, which can be programmatically determined. However, objects in the same course cannot be set for different languages.

As Phil indicated, authors make decisions to create courses to meet accessibility conformance and we are continuing to make improvements.

Thanks for reaching out!