Storyline and Web Content Accessibility Guidelines (WCAG)

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.

-------------------

Upon my review of your application against Lectora, Captivate, Camtasia the Articulate method for providing closed captions is free hand and can not guarantee that it will always be ADA Complaint.  As well, it does not export or import standard caption file formats.

As a result, our team has been using Camtasia a forced restrictive application that prevents mistakes when implementing CC for ADA Compliance.  The following link is how Camtasia can state it is ADA complaint.

Personally, I found it frustrating attempting to implement the Articulate Storyline 2 method as it actually causes double work because it can not import an existing ADA complaint CC file.

Does the Articulate Storyline 2 Team have something in the works or is this not on the radar?

All the best,

Kevin

 

2 Replies
Steve Flowers

Camtasia's captioning method is among the best I've seen. Though I don't mind using CaptionHorse in a pinch.

I've gotten used to captioning in Storyline. I don't add captions directly to the slide itself, instead using a %caption% reference in a single object and updating the caption variable using a set of triggers. It's a little slower than Camtasia's method. But I don't have problems with accuracy. I typically size my captions to a single line at 3 to 4 seconds. I'll probably drop back to 3 to 7 seconds and max 2 lines 1/3 to 1/2 slide width for my next captioning adventure. Half the work:)

The biggest drawback is what you've pointed to. The captions aren't portable. So the work is locked away inside of Storyline.