W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Review of Web Audio Processing: Use Cases and Requirements

From: olivier Thereaux <olivier.thereaux@bbc.co.uk>
Date: Fri, 29 Jun 2012 10:42:29 +0100
Cc: WAI Liaison <wai-liaison@w3.org>
Message-Id: <99456369-08DD-4C03-98F0-74A40AA33393@bbc.co.uk>
To: Michael Cooper <cooper@w3.org>, Audio Working Group <public-audio@w3.org>
Hello Michael,

General comments for now - I will go into details when entering issues into our tracker.

On 27 Jun 2012, at 20:04, Michael Cooper wrote:
> I haven't proposed use cases but do think
> we need to develop a use case that explains a user with a screen reader
> and who depends on audio cues from the operating system, who is also
> interacting with Web application audio as proposed in the other use cases.

This sounds like a good opportunity to truly enrich our use case #8:
https://dvcs.w3.org/hg/audio/raw-file/tip/reqs/Overview.html#uc-8--ui-dom-sounds

Making the UC about a strong need to use and control UI audio cues will make it more interesting.

> Are there issues with needing to provide a way for limits e.g., on total
> volume when multiple tracks layered, or is this handled by audio
> equipment? 

> Need a requirement to provide ways to avoid triggering audio-sensitive
> epileptic seizures.

These are interesting needs, and we need to have a good think about safeguards and whether/how to implement them. I like to think in terms of "enabling developers to do the right thing" rather than "adding limitations against such mistakes" so the answer to your concerns might reside in developer guidelines? Or are we seeing a need for user preference at the (browser) implementation level?

Olivier



Received on Friday, 29 June 2012 09:42:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 29 June 2012 09:42:51 GMT