8 Replies
Leslie McKerchie

Hi E,

You can check out our documentation here on adding Alternate Text.

I also recorded a brief gif showing how you can right click on the object as well:

It looks like your email signature came through when you replied via email. You can remove that if needed by clicking ‘Edit’ beneath your response. Here’s a quick Peek video if you need help.

David Sprouse CU

I've recently done a pretty thorough WCAG 2.0 A and AA review on Storyline 360 (SL) and found, like similar course dev tools from other vendors, SL lacks considerably in meeting the letter of the WCAG guidelines. I should qualify that the results are better than others I have tested.

The approach used by SL to address many of the WCAG guidelines  is to apply alt text to most content objects. 

In the case of headings (see 1.3.1, 2.4.6, 4.1.1), a reasonable work-around might be to force the alt text to state what the screen-reader user expects. For instance, for H1 headings set the alt text to read "heading level 1: [course_heading]" where course_heading is the actual heading text displayed on the slide. For H2 headings include "heading level 2:" in the alt tag, etc.

See an attached example of how my team is applying this.

 

 

Laurence Lewis

Adding alt text or an aria-label so screen readers announce the heading level does not fix the issue that screen reader users cannot use expected navigation functions, such as; jumping to heading using the 'H' key or skim reading. It also does not enable a screen reader user to view a list of heading, links, button etc.