Making an accessible course relying largely on human v/o and closed captions?
(For some reason, this question got flagged in the Storyline forum, so I just deleted it. This may be a better place for it.)
I've created a lot of Storyline courses with various types of closed captions or transcripts, and I've been experimenting with classic accessibility features on some draft courses, using tab order, alt text, etc. to work with screen readers.
But I'm about to create my first fully accessible course, meeting AODA standards for Ontario (WCAG 2.0, Level A). It's a soft skills course, not technical or software training.
All previous courses for this client have relied upon narration and closed captions. We'd like to keep using our favourite voice artist and narration, but I have concerns about making this work without audio clashing when screen readers enter the mix.
Has anyone out there ever made full v/o work in an accessible course?
My current concept for the course is to treat it as a podcast with a lot of visual elements that keep changing in order to engage most of our students who won't be using screen readers, plus accessible quizzes/knowledge checks.
Most screens would show relevant visuals and text excerpts, but the full "story" is carried by the narration (identical in the v/o script and captions). Students would need to keep audio turned on or keep captions visible to get all the content.
To avoid clashing screen reader content, none of the images or text on these slides would be made accessible to tab order or the screen reader. Text would be presented as an image, and alt text would not be used for on-screen content.
(Exception: the quizzes/knowledge check slides would have no v/o and would be designed to work with screen readers.)
This provincial course on the AODA is a series of talking head videos, plus some imagery: http://www.ohrc.on.ca/en/learning/working-together-code-and-aoda/part-1-introduction
I may emulate that approach using Storyline objects on each slide and/or create some mp4s and include them as auto-playing video.
It seems bizarre to design an accessible course by avoiding the usual techniques, so are there any pitfalls I should be aware of? Are there any other ways I can keep useful v/o, avoiding putting a lot of text on the screen, and still keep everything accessible and clear?