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

Re: Media--Technical Implications of Our User Requirements

From: Janina Sajka <janina@rednote.net>
Date: Mon, 19 Jul 2010 13:59:33 -0400
To: public-html-a11y@w3.org
Message-ID: <20100719175933.GE2478@sonata.rednote.net>
Philippe Le Hegaret writes:
> On Mon, 2010-07-19 at 16:41 +0200, Philip Jägenstedt wrote:
> > >          + 3.1 Access to interactive controls / menus
> > > An API providing access to:
> > >
> > > volume (for each available audio track)
> > 
> > .volume
> 
> Is there a need to have simultaneous playing of audio tracks? If
> not, .volume is good enough indeed.
> 

This topic was discussed, but not resolved at last Wednesday's call.


In broadcast, were these audio description originates, there's the media
resource track, and there's the described track which has pre-mixed
description with audio from the primary audio resource.

While it would be possible to continue this practice, there's user
argument to disentangle these in order to enhance functionality, e.g.
allow descriptions to go to just one output device like headphones) while the primary
resource's audio goes to a different device (which the description
consumer can also hear).

Separating the two makes for less data to download--but requires client
side mixing.

Janina

> Philippe
> 
> 

-- 

Janina Sajka,	Phone:	+1.443.300.2200
		sip:janina@asterisk.rednote.net

Chair, Open Accessibility	janina@a11y.org	
Linux Foundation		http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative	http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)
Received on Monday, 19 July 2010 18:00:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:13 GMT