Forum Discussion
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 controlled: 4.1.2 Name, Role, Value.
How is this controlled/changed/edited, and how could we ensure this is changed through the tool and not through manually changing any of the output (published files/code)?
For example: how would we change the values for the following attributes for aria-describedby="unspoken" or aria-labelledby="label-1-0-5"?
36 Replies
Hey Tim,
You've got quite the task on your hand, so I'm happy to help break it down further.
I'd start by taking a look at the description of standard 4.1.2 here.
It's a lot to go through, but in short, as the Storyline author you'd want to look at using alt text or on-screen text, especially for interactive objects like text entry. Doing so will ensure that learners with assistive technologies know what that field is for.
Also, as I understand it, ARIA is a subset of standards within WCAG 2.0. WCAG 2.0 and ARIA are not one in the same, and Storyline currently supports the WCAG 2.0 standards.
So if I tab to a hidden button and have alt descriptive text on that hidden button, the screen reader (i.e. JAWS) would read the descriptive text ? Is this correct?
I meant a transparent button not hidden
Hi there Joe,
Yes, that's right! Be sure the button appears on the slide tab order, and JAWS will read the alt text when you tab to the button.
Where is the WCAG VPAT for Sl 360?
Hi Sam,
This article outlines how we’ve optimized Storyline 2 and later to support WCAG 2.0 criteria, Levels A and AA.
You may also find this video tutorial helpful on how to make Storyline 360 courses that support Section 508 and WCAG accessibility guidelines using closed captions, tables, alt text, custom tab order, and more.
Is Articulate planning on including the checklist of compatibility with WCAG 2.1? Other authoring tools have already published theirs.
https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/
WCAG 2.1 was released January 2017 almost 2 years ago.
We're working on a number of accessibility enhancements for Storyline and making great progress. To help with that, we've been consulting our customers about specific needs and have identified a range of improvements we can make, although I don't have specifics to share yet, I'll let them know about your concerns for support of WCAG 2.1.
The WCAG 2.1 statement 1.3.4 on Portrait and Landscape support: SL has that now. Others maybe not yet, and others are up to the author. Statement 1.4.10 Reflow: SL has that now.
Then there are areas I'm not familiar with: 2.1.4 Character Key Shortcuts, 2.5.1 Pointer Gestures, many more. It isn't terrible not to support all these points. How can I get a list of what is supported?
We have to respond to an RFP with WCAG 2.1 compliance.
We've put a table into Word of the 2.1 points and done our best guess as to what is supported.
Would you take a look at the attached document to let us know if we've overstated anything?
