W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2010

Re: UAAG 2.0 guidelines for video

From: Janina Sajka <janina@rednote.net>
Date: Wed, 5 May 2010 17:04:05 -0400
To: Eric Carlson <eric.carlson@apple.com>
Cc: Philip Jägenstedt <philipj@opera.com>, jimallan@tsbvi.edu, Silvia Pfeiffer <silviapfeiffer1@gmail.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, WAI-UA list <w3c-wai-ua@w3.org>, John Foliot <jfoliot@stanford.edu>
Message-ID: <20100505210405.GI2329@sonata.rednote.net>
Eric Carlson writes:
> On May 4, 2010, at 8:47 PM, Philip Jägenstedt wrote:
> > Unless the browser has some way of knowing that the audio is speech, the only thing one can do is apply pitch correction for all audio. I know some version of WebKit does something like this, and would support a DOM attribute to give authors explicit control over it.
> > 
>   Indeed WebKit does pitch correction by default. We have an experimental DOM attribute, webkitPreservesPitch, that allows a script to turn it off [1].
Actually, a musician would have solid reasons to slow down audio
playback while preserving pitch. I don't see any particular reason why
we should be concerned whether audio is speech or something else. After
all, the user that doesn't want to modify the time-scale simply won't
bother--so no harm.

Of course a musician who wants to work with moded audio is likely to get
the highest quality tool available, which may well not be the browser.

Received on Wednesday, 5 May 2010 21:08:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:39 UTC