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

Re: [media] Moving forward with captions / subtitles

From: Eric Carlson <eric.carlson@apple.com>
Date: Thu, 18 Feb 2010 21:43:19 -0800
Cc: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Geoff Freed <geoff_freed@wgbh.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-id: <90F4F935-78D7-4A0D-BBA9-ECA9ABD067A2@apple.com>
To: philipj@opera.com

On Feb 17, 2010, at 9:49 PM, philipj@opera.com wrote:

> On Thu, 18 Feb 2010 00:31:17 +0800, Eric Carlson <eric.carlson@apple.com>
>>  Some questions and thoughts, in no particular order:
>> +  I assume that if I use our track API to examine the track tracks in a trackgroup, the one chosen from among a group of alternates is enabled, and the others are not?
> What does enabled mean here? Since the MediaTracks API doesn't reflects
> the concept of groups, the mapping is open for debate. I think we should
> either reflect groups in some way, or we should simply expose all tracks
> in all groups (enabled or not) and setting .enabled=true on a track should
> implicitly disable the others in the same group.
  We should definitely expose all tracks, whether or not they are in a group. We could expose group, but what could a script do with it?

>> + I also assume that if I set the enabled property on one track in a group all of the others are automatically disabled?
> Yes.
>> + Do we enable the first track in a group if none match?
> I don't think so, but we haven't discussed the track selection algorithm
> much at all. I suppose it should first find the the first track with the
> enabled="" attribute in each group and enable that. But do we also want an
> enabled attribute on the group itself that performs selection based on
> media type, language, role etc?
The whole point of <trackgroup> is to mark some number of tracks that are alternates of one another, so the *user agent* can choose which one is most appropriate to enable based on conditions on the user's machine (user preferences, machine characteristics, etc). If we are just going to allow the user to specify which one is enabled, why bother with the grouping at all?

In other words, it is the job of the content author to describe each tracks in a group so the UA can pick the best one for the user. If the content author wants to choose which one is enable, they should not use a <trackgroup>.

Received on Friday, 19 February 2010 05:43:56 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:09 UTC