Forum Discussion

TimPhillips's avatar
TimPhillips
Community Member
8 years ago

WCAG 2.0: ARIA attributes and Storyline 360

Hi all - I am helping my team meet WCAG 2.0 requirements for a customer with courses created in Articulate Storyline 360. According to the WCAG VPAT for Storyline, the following standard is author c...
storyline 360
AlyssaGomez's avatar
AlyssaGomez
Staff
7 years ago

Great question, Jessi!

We've worked through all the WCAG 2.1 criteria for Storyline 360, which has more features such as closed captions and custom tab order. If accessibility is important for a course that you're building, especially WCAG 2.1 support, I would recommend using Storyline for its robust accessibility features instead of Studio. Would that be an option for you?

  • jauscrick's avatar
    jauscrick
    Community Member
    7 years ago

    Hi Alyssa,

    I actually do use Storyline and I meant to link this page: 

    https://articulate.com/support/article/articulate-storyline-and-web-content-accessibility-guidelines-wcag

    The page doesn't have the newest WCAG items included. Such as the ones Ashley listed above:

    1.3.4 Orientation (AA) - Supports
    1.3.5 Identify Input Purpose (AA) - Does Not Support
    1.3.6 Identify Purpose (AAA) - Does Not Support
    1.4.10 Reflow (AA) - Supports
    1.4.11 Non-Text Contrast (AA) - Supports
    1.4.12 Text Spacing (AA) - Not Applicable
    1.4.13 Content on Hover or Focus (AA) - Supports
    2.1.4 Character Key Shortcuts (A) - Supports
    2.2.6 Timeouts (AAA) - Supports
    2.3.3 Animation from Interactions (AAA) - Supports
    2.5.1 Pointer Gestures (A) - Supports
    2.5.2 Pointer Cancellation (A) - Supports
    2.5.3 Label in Name (A) - Supports
    2.5.4 Motion Actuation (A) - Not Applicable
    2.5.5 Target Size (AAA) - Supports
    2.5.6 Concurrent Input Mechanisms (AAA) - Supports
    4.1.3 Status Messages (AA) - Not Applicable