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

Re: [media] raising bugs in W3C bug tracker for LC

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 29 Sep 2010 19:15:55 -0700
Cc: 'Sean Hayes' <Sean.Hayes@microsoft.com>, 'HTML Accessibility Task Force' <public-html-a11y@w3.org>
Message-id: <EBA6BCCE-7ED8-4088-A839-7AC8AB2477F8@apple.com>
To: John Foliot <jfoliot@stanford.edu>

On Sep 29, 2010, at 6:15 PM, John Foliot wrote:

> Sean Hayes wrote:
>> 
>> As a result of this exercise, I think we need to check the
>> spec and possibly open additional bugs on:
>> 
>> Providing visible indication that descriptions and captions are
>> available.
>> 
>> Allowing the user to independently adjust the volumes of the audio
>> description and original soundtracks.
>> 
>> Allowing the user to control playback timing in order to have more
>> time to understand the material, read a lengthy description or caption
>>   (I think this one is mostly covered by
>> http://dev.w3.org/html5/spec/video.html#dom-media-playbackrate but we
>> need possibly to add some text for when the timed text itself can
>> control the playback rate)
>> 
>> Support the isolation of speech from other background sounds in AV media
>> 
>> Support user control over the visual presentation of caption text.
> 
> Further to our Media sub-team call of today, the following bugs have been
> filed:
> 
> [Bug 10839] New: Providing visible indication that descriptions and
> captions are available.
> [Bug 10840] New: Allow the user to independently adjust the  volumes of
> the audio description and original soundtracks.
> [Bug 10841] New: We require a method to allow the user to control
> playback timing in order to have more time to understand the material.
> [Bug 10842] New: Support the isolation of speech from other  background
> sounds in AV media
> [Bug 10843] New: Support user control over the visual presentation  of
> caption text.

Should some of these perhaps be issues for UAAG instead of HTML5? HTML5 does not generally make requirements on browser UI (other than whatever is necessary inside Web content for interop purposes). There are no requirements on what built-in media controls look like, for example.

Alternatively, perhaps some of these should have parallel requests for appropriate scripting APIs, for the case of custom video controls.

Regards,
Maciej
Received on Thursday, 30 September 2010 02:17:03 UTC

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