When I mentioned earlier in the week that I had made a bunch of videos for my online East Asia course last semester, a colleague challenged me on twitter regarding whether the videos were captioned. I responded that the ones I was talking about were not part of my OER, but just short messages to my students announcing what was next, explaining how to use tools like Hypothesis, etc. He responded that even so, federal and state law and our university system’s policies require captioning of any course video.
I was not sure this is true, so I asked him to provide a reference to the statutes he thinks apply. He provided a link to a MinnState guideline document that seems to agree with his claim that the system I work within supports a broad interpretation of the law that seeks to require captioning of all videos, regardless of their purpose. Among the questions addressed in the document’s FAQ is an explanation that transcripts of videos are not sufficient, because the user experience is not identical. While I accept that this statement is true, I’m skeptical of its importance in all cases. For example, If I make a video version of a PowerPoint lecture based on a chapter of my OER textbook, the same basic content is presented in three different formats. My initial idea is to make the content accessible to students with different learning styles. I think, some students learn better by reading: they’ll use the textbook. Others may have time while commuting: a podcast might be useful to them. Others may miss one of my lectures of may really learn better watching a video: so I’ll make a video version of my lecture and post it online.
The idea is to make my course content more accessible. Requiring me to caption these lecture videos complicates the process of making them and adds time. Let’s be honest: increased complexity and time are disincentives. Not only for someone like me who wants to make videos, but even worse for instructors who are on the fence about the shift to online resources or looking for a reason to reject the idea. Moreover, the type of aggressive virtue-signaling language that sometimes accompanies arguments or mandates of accessibility can be very off-putting. Maybe it’s me, but I’d prefer to be helped to make my content more accessible rather than told if it’s not 100% right out of the gate I shouldn’t bother. And if I was paranoid (who me?) I might suspect that although the proponents of universal accessibility have their hearts in the right spot, putting steep barriers in the way of instructors seeking to make a change seems to play into the hands of textbook publishing corporations.
Don’t get me wrong. I’m going to try to make my videos with captions, even though that’s going to be more complicated and time-consuming. I’m going to try to find the least time-consuming and expensive way to do that and share what I find. If you know of any better, faster, cheaper ways, please let me know! Although I’m fairly comfortable with technology and have a lot of opinions I’m not shy about sharing, I’ve only been doing this OER and open ed stuff for about a year. Point out what I’m missing and I’ll work it in and make a video about it!
As I’ve begun looking at the tools available, there seem to be a several ways for me to type caption text into a video as I’m watching it. This isn’t optimal. If I’ve written copy and then made a video of it, the last thing I want to do is then retype it. I suppose I could cut and paste it a little bit at a time, but this is also a pain, especially if I’m captioning a lecture. So the best option seems to be finding a reasonably accurate, easily-correctable auto-captioning app. Again, there are a bunch of these available, but I’m not going to buy one in order to make my videos. Sorry. I paid for Camtasia, but there’s a limit to the amount of my own money I can afford to spend. I was disappointed to learn that Vimeo, the video-hosting service I’ve been using for years to avoid YouTube, allows you to add captions to videos but doesn’t have an automated process like YouTube’s. It supports automation tools like CaptionSync, but again, I’m not going to buy a subscription to an app that doesn’t even list its pricing online! So maybe it’s time to surrender to the dark side and stop paying $199 a year for an inferior tool.
Roughly six hours after writing the previous paragraph, I’ve removed over 150 videos from Vimeo, canceled my $199 per year “Pro” subscription, and loaded eleven lecture videos from my American Environmental History course onto YouTube. The auto-captioning seems to work remarkably well! Not perfectly, and I’ll need to spend a little time with each video, editing the captions. I’ve shifted the licensing on the videos from standard YouTube license to CC-BY, the Creative Commons Attribution open license that allows anyone to reuse or remix the videos. I don’t think it’s really possible to download the YouTube versions of the videos, so maybe I should load the originals up into Opendora (my system’s open archive) so that others who want to use the content can grab an mp4 file and mess with it.
My next step will be to see if it makes sense to load videos like the lectures I just added to YouTube into an app like MediaSpace in my university’s learning management sandbox. I’m not actually teaching the course those videos go with again this semester, and I’m rethinking a lot of design elements of the video lecture format, so I’ll need to ponder on that a bit in the next couple of weeks as I prepare for next semester. I’ll report on the process as I go, so thanks for reading and I’ll see you again next time.
2 thoughts on “Captioning Videos”
I wanted to chime in and thank you for captioning your videos (whether through Youtube or ?). I’m deaf so captions are very helpful and much appreciated.
P.S. Glad to see you’re diving into Obsidian. I use it too and find it fantastic.
Thanks, Ray! Actually, my original reason for switching from Vimeo to YouTube, about a year ago, was that the Vimeo captioning experience was too expensive and clunky, whereas YT just does it automatically, and fairly accurately.