Articulate Storyline and Web Content Accessibility Guidelines (WCAG)

Article Last Updated Jun 17, 2016

This article applies to:

It’s our goal to help people with disabilities interact as fully as possible with the courses you create in Articulate Storyline.

The following table outlines the many ways we’ve optimized Storyline to meet WCAG 2.0 requirements, Levels A and AA. The design decisions you make while building courses in Storyline also impact WCAG compliance. We’ve noted those cases in the table below and have provided guidance on how to make WCAG-compliant authoring decisions where appropriate.

WCAG RequirementLevelStoryline Support

1.1.1 Non-text Content

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.

A

Supported. ALT tags can be defined as text alternatives.

1.2.1 Audio-only and Video-only (Prerecorded)

An alternative for time-based media is provided.

A

Supported. Text boxes timed to the audio or video can be used throughout the course.

1.2.2 Captions (Prerecorded)

Captions are provided for all prerecorded audio content in synchronized media.

A

Supported. We recommend that authors use triggers to display a caption text box synchronized with the media. The display of the text box is controlled by a variable on the slide master.

1.2.3 Audio Description or Media Alternative (Prerecorded)

A

Author controlled.

1.2.4 Captions (Live)

AA

Not applicable.

1.2.5 Audio Description (Prerecorded)

In synchronized media.

AA

Author controlled.

1.3.1 Info and Relationships

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

Author controlled.

1.3.2 Meaningful Sequence

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

A

Supported. A custom order for the screen reader can be defined by the author.

1.3.3 Sensory Characteristics

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

A

Author controlled.

1.4.1 Use of Color

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

A

Author controlled.

1.4.2 Audio Control

If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.

A

Supported. The screen reader can access the player audio controls.

1.4.3 Contrast (Minimum)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large text, incidental text, or logotypes.

AA

Author controlled.

1.4.4 Resize Text

Text can be resized without assistive technology up to 200 percent.

AA

Author controlled. Author sets the font size for slide text and player controls.

1.4.5 Images of Text

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text.

AA

Author controlled.

2.1.1 Keyboard

A

Supported. If you include drag-and-drop or hotspot interactions, provide an alternate, keyboard-controlled interaction.

2.1.2 No Keyboard Trap

A

Supported.

2.2.1 Timing Adjustable

A

Supported.

2.2.2 Pause, Stop, Hide

A

Supported.

2.3.1 Three Flashes or Below Threshold

A

Supported.

2.4.1 Bypass Blocks

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

A

Supported. Navigation can be skipped to access the content immediately.

2.4.2 Page Titled

A

Author controlled.

2.4.3 Focus Order

If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

A

Supported. A custom order for the screen reader can be defined by the author.

2.4.4 Link Purpose (In Context)

A

Author controlled.

2.4.5 Multiple Ways

More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.

AA

Supported. The menu player feature can be utilized to achieve this requirement.

2.4.6 Headings and Labels

Headings and labels describe topic or purpose.

AA

Author controlled.

2.4.7 Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

AA

Supported. A rectangle indicating focus is displayed when tabbing from item to item.

3.1.1 Language of Page

A

Supported. Language identifier is in the published output for screen readers.

3.1.2 Language of Parts

AA

Author controlled.

3.2.1 On Focus

When any component receives focus, it does not initiate a change of context.

A

Supported.

3.2.2 On Input

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

A

Author controlled.

3.2.3 Consistent Navigation

AA

Author controlled.

3.2.4 Consistent Identification

AA

Author controlled.

3.3.1 Error Identification

A

Author controlled. Examples: Automatic warnings for questions left blank, number validation for numeric entries, email address validation, etc.

3.3.2 Labels or Instructions

Labels or instructions are provided when content requires user input.

A

Author controlled. Ensure labels are appropriately used in markup and on-screen.

3.3.3 Error Suggestion

AA

Author controlled.

3.3.4 Error Prevention (Legal, Financial, Data)

AA

Author controlled and specific to the LMS in use.

4.1.1 Parsing

A

Author controlled.

4.1.2 Name, Role, Value

A

Author controlled.