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
Thanks, Sam. I didn't want to mess with your document formatting, so here's the list of WCAG 2.1 criteria with notations on if it's supported or not applicable to Storyline. The only ones we don't have support for are 1.3.5 and 1.3.6, but we'll keep you posted if that changes!
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- jauscrickCommunity Member
Will there be any updates to this page regarding WCAG 2.1?
- SamClarkCommunity Member
Well thanks! This is all we need to respond.
It would be much more helpful to course authors if there were links to documentation that describes the supported features in detail. For example, I have no idea about learner keyboard shortcuts.
Perfect - happy to hear it Sam!
I'll let the team know you're hoping for some official documentation and as we add more support, we'll be sure to keep those things updated.
- SamClarkCommunity Member
Is there no documentation on the web for keyboard shortcuts?
Hi Sam,
Are you looking for specific shortcuts to use with Storyline and focused on accessibility? It may depend on the browser and any screen reader tools you're using, but keys like Tab, Enter, Space Up/Down arrows are all ones you can use with Storyline and a screen reader to navigate around.
You'll also find a mention in this article on designing accessible courses about how you could add in your own keyboard shortcuts for learners.
- SamClarkCommunity Member
HTML and HTML5 websites that offer keyboard shortcuts don't require a screen reader to do the shortcut. Tabs or special keys can step through or invoke specific links like: next page or previous page, pause, play.
So what I've gleaned is that Storyline's player doesn't have built-in keyboard shortcuts for player controls.
- WendyFarmerSuper Hero
Using the tab key will select the player controls Peek
- SamClarkCommunity Member
Is there any defacto standard keyboard shortcuts for Prev/Next Play/Pause?
- SamClarkCommunity Member
Hi Sam,
Wendy's correct - you can use the tab key (and Enter, Space, Up/Down) arrows to navigate around without a screen reader. You can also easily add in your own keyboard shortcuts if you'd like your learners to navigate with particular keys.
Related Content
- 10 months ago
- 11 months ago
- 9 months ago