W3C home > Mailing lists > Public > public-html-a11y@w3.org > April 2010

Re: a11y TF CfC on resolution to support "Media Multitrack API" change proposal for HTML issue 9

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Sat, 3 Apr 2010 17:44:47 +1100
Message-ID: <r2s2c0e02831004022344ub1b3d329r28868e7838714284@mail.gmail.com>
To: David Bolter <david.bolter@gmail.com>
Cc: "Michael(tm) Smith" <mike@w3.org>, public-html-a11y@w3.org
This is a very good question and it possibly has some relationship to
a discussion about cue ranges that we still need to have.

I like the idea of realising cue ranges in this way, but I think it
may be a larger discussion that involves capturing all the
requirements for cue ranges and discussing all the different
possibilities of realising them.

Were you interested in getting a callback/handler on the captions to
also get access to the caption text from JavaScript? Or just to call a
specific handles at every caption start, e.g. to display related


On Thu, Apr 1, 2010 at 11:14 AM, David Bolter <david.bolter@gmail.com> wrote:
> This looks good to me. Is having something like a callback/handler (e.g.
> onCaption) that gets called when each caption is displayed outside the scope
> of this proposal?
> cheers,
> David
> On 30/03/10 5:55 AM, Michael(tm) Smith wrote:
>> This is a call for consensus within the HTML a11y task force to
>> record a resolution supporting the following Change Proposal:
>>   Media Multitrack API
>>   http://www.w3.org/WAI/PF/HTML/wiki/Media_MultitrackAPI
>> The "Media Multitrack API" change proposal relates to HTML WG issue 9:
>>   http://www.w3.org/html/wg/tracker/issues/9
>> To quote from the proposal's Summary section:
>>   This is a proposal for introduction of a JavaScript API for
>>   HTML5 media elements that allows Web authors to determine the
>>   data that is available from a media resource. It exposes the
>>   tracks that the resource contains, the type of data it is (e.g.
>>   audio/vorbis, text/srt, video/theora), the role this data plays
>>   (e.g. audio description, caption, sign language), and the actual
>>   language it is in (RFC3066 language code). It also enables
>>   control over the activation state of the track.
>> If you have comments about the resolution to support this
>> proposal, please send them by e-mail to this list prior to this
>> Thursday's task-force telcon.
>>   --Mike
Received on Saturday, 3 April 2010 06:45:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:34 UTC