Browse Articles

Select a Product

null Support Directory

Browse all null articles. (Last Updated )

No articles found.

Search Results

No articles found.

Storyline 360: Accessibility Checker Covered Issues

Article Last Updated Feb 17, 2026

This article applies to:

When you create or edit a Storyline course, the accessibility checker scans your content for the issues listed below. You’ll see only the issues that apply to your course, along with guidance on how to fix them.

This list will be updated as support for additional issues is added.

Audio, Video, and Non-Text Content

Perceivable issues relate to whether learners can see or hear the content. These checks focus on text alternatives, captions, audio controls, and other features that help learners access information through sight or sound.

Custom alt text added

Objects should have custom alternative text (alt text).
1.1.1 Non-text Content (Level A)

Alt text is less than 150 characters

Alternative text (alt text) for objects shouldn't exceed the recommended limit of 150 characters.
Recommended

Captions added

Audio or video content should have closed captions.
1.2.2 Captions (Prerecorded) (Level A)

Generated captions reviewed

AI-generated captions should be reviewed for accuracy.
Recommended

Accessible video controls enabled

The accessible video controls should be enabled.
1.4.2 Audio Control (Level A)

Video autoplay disabled

Video content shouldn't be set to play automatically.
1.4.2 Audio Control (Level A)

Background audio pauses when video plays

The background audio should pause while learners watch video content on a slide.
1.4.7 Low or No Background Audio (Level AAA)

Background audio volume lowers when slide audio plays

The background audio volume should lower when the slide audio plays.
1.4.7 Low or No Background Audio (Level AAA)

Text, Layout, and Readability

These issues focus on how content is presented and how it adapts to different settings. The checks help ensure text, layout, and orientation remain usable when learners adjust text size, spacing, or device orientation, including when using assistive technologies.

Text styles defined

Text elements should have defined styles, such as heading levels.
1.3.1 Info and Relationships (Level A)

Text upgraded

Project should use upgraded text.
1.4.12 Text Spacing (Level AA)

Playback orientation unrestricted

The responsive playback settings shouldn't be restricted to a single orientation.
1.3.4 Orientation (Level AA)

Font is 12 points or larger

Font sizes should be 12 points or larger.
Recommended

Keyboard Access and Interactions

Operable issues focus on whether learners can use the content with different input methods. These checks help ensure content works with a keyboard and doesn’t rely on precise mouse or touch actions.

Interaction accessible

Projects should have drag-and-drop interactions that are accessible.
2.1.1 Keyboard (Level A)

Skip navigation shortcut enabled

The skip navigation shortcut should be enabled.
2.4.1 Bypass Blocks (Level A)

Clickable objects are 24 pixels wide by 24 pixels tall or larger

Interactive objects like buttons should meet the minimum size guidance of 24 pixels wide by 24 pixels tall.
2.5.8 Target Size (Minimum) (Level AA)

Timing, Motion, and Playback

These operable checks focus on content that moves, plays, or changes over time. They help ensure learners can pause, stop, or adjust playback and slide timing instead of being forced to keep up.

Slides advance by user

Slides should be set to advance by user.
2.2.1 Timing Adjustable (Level A)

Play/pause button enabled

The play/pause button should be enabled in the player properties.
2.2.2 Pause, Stop, Hide (Level A)

Playback speed control enabled

The course playback speed control should be enabled.
Recommended

Marker animations disabled

Markers shouldn't have animations.
2.3.3 Animation from Interactions (Level AAA)

Navigation, Structure, and Identification

Understandable issues help learners know where they are and what content each screen contains. These checks support clear structure, meaningful titles, and predictable navigation.

Slide title defined

Slide titles should have distinctive names.
4.1.2 Name, Role, Value (Level A)

Slide title distinctive

Each slide should have a distinctive title.
4.1.2 Name, Role, Value (Level A)

Scene title defined

Scene titles should have distinctive names.
4.1.2 Name, Role, Value (Level A)

Scene title distinctive

Each scene should have a distinctive title.
4.1.2 Name, Role, Value (Level A)

Player and Accessibility Controls

Robust issues focus on compatibility with assistive technologies and user settings. These checks help ensure learners can adjust and interact with content using a wide range of tools and preferences.

Accessibility controls enabled

The accessibility controls should be enabled.
1.4.4 Resize text (Level AA)