tutorial on 508 compliance?

I would love (love!) to see a tutorial on how to use the 508 features in the new Storyline software. All the video tutorials you folks post are really helpful and since Storyline is said to be 508 compliant, you would be doing some of us a big favor if you showed us how to use it in making 508-compliant e-learning courses, from interactivity, accessibility tags, quizzes, etc.

This is a really important topic for those of us who provide e-learning to federal agencies or would like to do so. I think the trend will be for other agencies, state, private, etc, to move toward accessibility for users in the future.

I don't agree with the regulations, i.e., everybody has to be able to use all training materials even if they would be unable to perform the job for which the training is provided. But I, and others, have to live with them.

Tutorials would be a huge, huge help. (Did I state that strongly enough?)   

64 Replies
Helledk Wittrup-Jensen

Hi everybody.

I watched the tutorial on how to turn on the Alt Text on objects and found it very helpful. But when I tried it in Storyline I found that you dont have the possibility to type an alternative text for markers because the Size box is not under Format. So how do I change the Alt Text for markers? And if this is not possible, how do I follow the 508 compliance and use markers at the same time? I want a blind person to know what the marker do when he tabs to it. Hope you understand.


Ashley Terwilliger-Pollard

Hi Rick,

Jeanette is no longer with Articulate (we still keep her tutorials as they are awesome!) but I don't know that there would be a particular tutorial on achieving 508 compliance, as full compliance of Section 508 will vary by organization. Thus, additional steps beyond what our documentation provides may be necessary (e.g., accounting for video captioning, interactive scenarios, etc.). This article and the methods described there provide guidance on how to create a Section 508 compliant course. 

The information on Storyline's 508 compliance is available here, and this table breaks down individual elements that meet the requirements. 

Russell Holbrook

Brian Batt said:

Hi everyone,

Storyline’s Flash-based output is 508 compliant.  However, content published for HTML5 and the Articulate Mobile Player is not.  Please review the following article for more information:


You can also include alt text that will be read by the screen reading software:


Although Storyline content is 508 compliant, you can take your content a step farther by adding on-demand Closed Captioning by using layers and triggers:


If you really want to understand accessibility, my advice is to install JAWS and take the content for a test drive:


Once you get a feel for how a person will actually use the content in a screen reader or JAWS environment, you'll be able to develop better courses.

Russell Holbrook


I am preparing to utilize Storyline for learners who are government employees.  With Section 508 in mind, what type of font and its size should be utilized?  As I plan for the design, what additional guidelines should be followed to ensure that the visual aspects are compliant with Section 508?

Have you found any additional training or resources on Section 508 that I could tap into?

I found information on eLearning Guild's website to be very useful.


Mike Song

I too am working towards 508 compliance. Question: People are saying that we need to create an alternative branching page for some with disabilities. Would an alternative layer also work? I ask because I set my courses for 70% completion and adding slides messes up the completion.

Question 2: Also - my designs are really 5 videos triggered by a Storyline player navigation page with 5 buttons on it. I always pop a full transcription into the notes section. What exactly are the rules for video? Am I sunk or saved?

Raphy Abano

How's everyone going?

I actually do need some help with accessibility standards for a course that I'm working on. I attached a sample page from one of the courses. Here's a description of what happens:

- This course has 2 "paths": One is for the normal learners, and the other is those with visual disabilities.

- VisionDis is a variable that controls which path is shown (Path 1 or 2).

On Path 1, the user can navigate normally (either by clicking or tabbing through with the focus box).

On Path 2, while the audio is playing, the user's focus box tabs through Menu and Closed Captions only, but then they can go to the play/pause/stop/previous/next buttons when the audio is done.

These work the way I want it to inside Storyline, but on the published html file, here's what happens:

- There are instances that I cannot tab my way back to the screen if I'm on Menu/Closed Captions.

- Our QA person who checked this using JAWS couldn't press on the play button.

- The tabs don't seem to get read (or it doesn't read all the time).


I'm not sure if this has anything to do with our JAWS reader being on trial mode, to be honest.


I guess I'm just looking for some additional direction on how to make this function better on Path 2. I know I can probably assign buttons on the keyboard for the course buttons, but any recommendation on how to make this more user-accessible would be great!

Victoria Morgan

Hi Lauren, 

Yes talking about the correct and incorrect layers. Attached is the new focus order that I adjusted and am hopeful that resolved the issue, but would appreciate your assistance or insight in what would resolve the reader not catching the pop ups. Thank you!