FW: associating video and audio transcripts…

See http://lists.w3.org/Archives/Public/www-tag/2015Apr/0066.html

You will remember that the Media TF discussed this proposal with some A11Y experts at our April F2F meeting:
http://www.w3.org/2015/04/15-html-media-minutes.html#item11 

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329


-----Original Message-----
From: chaals@yandex-team.ru [mailto:chaals@yandex-team.ru] 
Sent: Thursday, April 30, 2015 12:08 PM
To: Public TAG List
Subject: associating video and audio transcripts…

Hi,

Bcc: HTML accessibility Task Force.

the HTML Task Force is working on the problem of how to associate a transcript for a video (in particular, although in principle it can apply to audio) with a given video.

There are a handful of use cases, including providing multilingual transcripts, providing a transcript that has timing information and is used as a navigation device with the video then being moved to match the relevant point in the transcript, having a transcript *without* timing information, having a transcript in some horrid proprietary format, and having a transcript in a nice standards-based format in the same page as the video element to which it applies.

More information is at http://www.w3.org/WAI/PF/HTML/wiki/Full_Transcript ... including ideas that we don't think will work out, as well as a proposed design, which is roughly

* Have an element as a child of the video element able to unambiguously point to a transcript.
* Allow it to be repeated, e.g. for transcripts in different languages

Optionally, also create a transcript element as a container for transcripts. The main rationale for this is to assist players which want to identify a transcript provided as part of a page, and load them into an interactive region - avoiding the problem of marking a heading and not knowing where the transcript actually ends.

We're not very fussy about what element is chosen to link to a transcript, we just want a workable agreement. But we do want the TAG's opinion on whether there is something architecturally wrong with our "preferred approach" that another approach would handle better.

We would appreciate eventual feedback to public-html-a11y@ and in the meantime if we can help by participating in discussions within the TAG please let us know.

cheers

Chaals (co-coordinator of the TF)

--
Charles McCathie Nevile - web standards - CTO Office, Yandex chaals@yandex-team.ru - - - Find more at http://yandex.com

Received on Thursday, 7 May 2015 16:16:11 UTC