W3C home > Mailing lists > Public > public-html-media@w3.org > December 2013

RE: Action-219: Draft Response to MSE on Bug 23661

From: James Craig <jcraig@apple.com>
Date: Mon, 16 Dec 2013 15:58:46 -0800
Message-id: <6480CB36-776B-446A-B5E2-318F13C3B694@apple.com>
To: public-html-media@w3.org
I previously mentioned my objection on the accessibility task force list:

On Dec 12, 2013, at 9:47 AM, James Craig <jcraig@apple.com> wrote:

> Since [synchronizing videos (including sign language videos)] is already possible with mediagroup, why is this change necessary? Sign language videos are often the test case examples for mediagroup. 

Here's an demo of mediagroup in WebKit/Safari.

WWDC 2012 synchronized video demo. Explanation starts around 3:30 (example even uses the sign language use case); demo starts around 10:30 and the corny banter between Beth and Vicki is quite entertaining. Demo ends around 16:00 when they start talking about the fullscreen API.
https://developer.apple.com/videos/wwdc/2012/?id=604

The video being used is this one of Bohemian Rhapsody, signed by Stephen Torrence. The video has its own caption track for ASL, which is not a 1:1 mapping to the English captions of the original Queen song, and demonstrates why these can and should be achieved using separate media elements synced using mediagroup. This ASL track is an alternative for another video, but it also has its own media alternatives (captions), which would conflict with main video captions if these were included as two video tracks in the same video element.
http://www.youtube.com/watch?v=sjln9OMOw-0

James
Received on Monday, 16 December 2013 23:59:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:33:01 UTC