Apple & Accessibility & FCPX – Forgotten Again

Today Apple have released some amazing videos about the great work they do with accessibility. And it is great work, don’t get me wrong. The fact that these abilities are built into the systems of Mac and iOS is perhaps the best sign that Apple is interested in more than just profits, they truly do see their goal of a strong bottom line as being enhanced by being a good corporate citizen. For that I applaud them.

I own a small business, and in that business I made videos for my clients. From commercials to industrials to little fun weird projects, I get to let my creativity flow and madness revel in ideas and explorations. It’s amazing fun, and I really do enjoy it.

Until I have to deliver a final project to a client.

Not because I’m unhappy with the work I’ve done, or because I think it could be better – it could always be better, but then it would never be done – or because I don’t want to leave the project. It’s because I have to deal with Closed Captions.

Actually, I don’t have to, I want to. I have several friends who are deaf or hearing impaired in some way, and while those who can use hearing aids in some format don’t need captions to understand what I’ve created, the deaf do. Badly.

Final Cut Pro is where I produce my video work. I’ve been using FCP since 2003, and FCPX since it was released in 2011. I made the switch to FCPX completely in 2013, and I love it. Except for captions, but  then, no version of FCP has been good with captions at all. Now that we’re in 2017 it’s disheartening to say the least. Way back in 2010 I wrote about how I create and manage captions and not much has changed, except I don’t ever produce a DVD and instead just deliver the .scc file with the MP4 and let the broadcast station deal with the mess on their ingest cycle. It’s pathetic and gross. And in many cases, it means that local production doesn’t get captioned because while I think it’s important, the FCC gives companies at my level and out, and most use it.

Captions can be just text at timecode, which is simple. In their most complex, they are styled, located text at timecode. That’s it. Nothing more. I work in text and titles and timecode every day in every video I do, so there is no reason that this simple function isn’t baked in at this point. Words at timecode. That’s all it is.

That Apple is making their systems and products accessible is great. Xcode grants programmers the ability to build accessible apps, and has from the beginning, which is even better as it makes a massive part of the ecosystem accessible.

That Final Cut Pro hasn’t ever and still doesn’t create closed captions is a smudge on that image.

11 thoughts on “Apple & Accessibility & FCPX – Forgotten Again

  1. I’m sorry, but as the last remaining lifer in what passes for the captioning business, captioning is not “simple.” Captioning comprises vastly more than the tiny list of attributes you claim here are an exhaustive such list (“That’s it”), which wouldn’t even suffice to describe subtitling, let alone captioning.

    Captioning should not be farmed out to amateurs, which, first of all, is what’s already happening at your level of production and, second of all, would become the norm if included in Final Cut Pro.

    What even extremely intelligent and ostensibly seasoned and informed professionals in various broadcasting industries know about captioning would fill a thimble with room left over for a hazelnut. You don’t want these people captioning your work.

    And, while we’re here, I have firsthand knowledge of how little Apple cares to learn about captioning. I have been procrastinating writing my “Apple to captioning: Drop dead” post for three or more years.

    You can contact me privately for a list of still-viable captioners. There might be three on a good day.

  2. sorry, i don’t really get it… afaik, closed captioning is either baked into a video or it is not. maybe i’m wrong but most standard containers like .mp4 or .mov don’t have close captioning as a metadata. so you either make your subtitles in photoshop or you use a text generator (or customize one in motion). or use a third party program or plugin in fcpx ( like this one : http://sugarfx.tv/info/subtitles_SUGARfx.html ) i don’t see how this is much more work than using a dedicated function. afaik, making subtitles in premiere, davinci or acidis also. pretty pita.

    sure, it’d be nice to have a dedicated function to make it things but it’ll always be tedious work unless you get an AI that can understand dialogue with 100% accuracy.

    getting more plugins is one of the downsides of fcpx costing a quartet of what it used to – but i’d rather have them bake in less obscure missing functions (like fx for audio lanes, a global mixer, conversion of files from version 10.0-10.1, easing keyframes, color curves, …) before putting work there

  3. Oh bull. I have captions on most of the time to watch and see what’s out there and I compare them with what’s on screen. That most are lazy transcriptions with poor timing is a huge part of the problem. That most captions today cover visuals that are intrinsic to the video is nearly criminal, and if I had the tools to put the text on the screen where I want it, in the font I want, at a readable size, I could do amazing storytelling without needing to rely on someone else. I like directing and editing, and knowing, exactly, how something will appear for one of my viewers. I have no problem putting the time into making good captions, but I can’t waste my time when it’s a process that literally takes days extra and looks bad.

    And it is simply text at timecode. What that text can be is far more complex than a transcript, but I never said it couldn’t be. I know it is. But the actual caption? Text at timecode. End of story.

  4. I agree, Apple has laid exceptional foundations within the OS and even within their apps, yet they’re missing some key features that make creating Universally Designed content harder that it ought to be. The CC issue you highlight is one of them, but I’ll add a couple more and still not be finished.

    Adding Descriptive Audio Content (DAC) is fairly straight forward but having an explicitly designated DAC audio track setting with a single click would not just make things easier it would also encourage people to do it even on simple projects. For example, a prompt on export that warns no CC or DAC detected. Same for iMovie.

    Pages, Keynote or Numbers could also do with having simplified Universal Design tools such as an accessibility inspector that provides feedback on “accessibility errors” as one is creating a document, sadly they don’t even have a accessibility checker for these apps at the moment.

    Apple’s App and content stores need a badge/filter that allow people to find for Universally Designed content. Such a mechanism would allow users to find apps that have, at a minimum, passed through Xcode’s “Accessibility Inspector” successfully. Making accessibility discoverable by being able to find content that has CC, DAC or apps that allow voiceover to function fully is needed now for users and could also reward people who have created such content.

    Apple please make accessibility simple and fun for the creators as well as the users.

  5. It’s not just closed captions. There’s no support for subtitles (import/export of .srt files, for example), which is an astonishing anyone doing international video work. Sure you can create a title generator at timecode, but if you need translations you have to go through it manually.

  6. No, closed captions are not baked in. If you don’t understand how caption tracks work, the easiest explanation is that they are a visual equivalent to a different language track. You can select to turn them on, then they are displayed, they are not baked into place. Titles are baked into the visuals. Closed captions are not.

    And yes, it’d be nice. It would’ve been nice when FCP was $1,000 on it’s own (I paid for it then) it would be nice as a plug in (it’s not) and it would be nice as an export option that worked (it doesn’t).

    I’m not adverse to paying a reasonable fee for something that works well and is easy to use, but there’s NOTHING out there that does it well for less than a grand, and that one thing that is close is a friggin nightmare.

  7. Yep. I focus on CC because I have literally done translation stuff once in 18 years, but yes, you are right, and it’s a nightmare.

  8. I would say that most of the bad CC we see out there is done by people in another country or by some automated system that is trying to caption from the vocals because networks and content producers are cheapskates. Doubt that auto CC will never work properly considering the lousy state of vocal mixing on TV shows that I watch these days. Multi-channel surround sound has been the standard for many years now, why can’t people mix it so that we can hear the vocals?

    As to CC in FCP, yes at the most basic level it is “text at timecode”, but practically it’s much messier than that. I have a friend with a captioning business here in Austin, and she has shown me some of the finer points that must be addressed if you want CC that is accurate, properly timed and properly placed. It’s not rocket science, but it is time consuming. Putting CC in the hands of every single FCP user would not improve anything and would most likely make it worse since most of them would do it as an afterthought or slap dash it in because a client demanded it. Plus considering that CC is now Federally regulated in various ways, it’s probably best for most editors to leave it to the specialists and avoid any entanglements.

  9. That’s the thinking that stopped titling from being in NLEs for the first few years. Yes, some people will do shitty closed captions. They won’t get work because of it, and that will either inspire them to do better or get help, or get out of the business. Yes, it’s work to do them, but right now it’s more work to do CC than it is to produce the entirety of the rest of the video, from concept to script to shoot to edit. It’s a disaster of a mess because no one has fought to rethink how they are made and what they do. This is where Apple excel, and I fully expect them to step it up. Putting accessibility in the hands of those who produce is a great thing. Building the tools so that it’s easy to do it well is part of that gig. Naysayers, which is what you’re being, see the goal as insurmountable, and it’s so not.

    Hell, check out Clips, and see what they are doing with words on screen at times now. That’s moving in the right direction, but nowhere near completely what we need.

  10. Agreed. It’s insane that something as basic as this isn’t part of FCPX. Yes, captions can be complicated, and doing them right is more of an art than a science.

    But when even YouTube can generate passable captions (and its built-in tool is remarkably good), it’s inexcusable that Apple still doesn’t support this.

    FWIW, I use Aegisub (http://www.aegisub.org) to generate SRT files—t’s pretty darn great for the price (free), and the workflow is reasonably fast once you get used to it.

  11. Absolutely. The “only professionals can do it” mindset is utter bullshit. Professionals will do a professional job, but that doesn’t mean non-professionals should ignore captions or subtitles entirely.

    It’s inexcusable that Apple still doesn’t support a feature that even YouTube bakes in. (FWIW, their tool does a perfectly acceptable job generating .srt files, as does the free Aegisub.)

    Now that Premiere finally has caption creation built in, maybe Apple will finally decide to check this feature box as well.

Comments are closed.