W3C home > Mailing lists > Public > public-wcag2ict-tf@w3.org > July 2012

Re: Looking at SC 1.4.2 Audio Control with "UI Context"

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Fri, 13 Jul 2012 03:25:39 +0200
To: Peter Korn <peter.korn@oracle.com>
Cc: public-wcag2ict-tf@w3.org
Message-id: <B2BE7AA6-DDA5-4D12-A473-05C15174773F@trace.wisc.edu>
Hi Peter

Not sure why you are opening up the ones we have consensus on.  

We have said multiple times that we were not proposing that we change any of the things we had already reached consensus on.  

MAYBE when we are all done and doing a language consistency run we might

 -- but lets not open up anything that has consensus until we are all done with the ones still left to do. 

Gregg Vanderheiden Ph.D.
Director Trace R&D Center
Professor Industrial & Systems Engineering
and Biomedical Engineering
University of Wisconsin-Madison

Co-Director, Raising the Floor - International
and the Global Public Inclusive Infrastructure Project
http://Raisingthefloor.org   ---   http://GPII.net

On Jul 13, 2012, at 2:40 AM, Peter Korn wrote:

> Hi gang,
> SC 1.4.2 Audio Control was one we reached consensus on.  However, I thought it would be useful to look at it with the new UI Context definition, to help evaluate that definition and where we might use it.  My thoughts on this can be found at the Applying UI Context page in the first row, but to facilitate discussion, I reiterate them here.
> Looking only at software, and doing a direct definition substitution for "web page" with the existing SC text, we get:
> If any audio on a [set of user interface elements and the presented information, within a product, that can be accessed using only navigation commands] plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.
> Note: Since any [of the user interface elements or presented information that can be accessed using only navigation commands] that does not       meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. 
> This seems workable to me, but I think "software user interface" is a cleaner substitution for this SC. Unless we were doing a global (or near global) "UI Context" substitution for "web page", I think it is better to keep our consensus text for this SC.
> Thought?
> Peter
> -- 
> <oracle_sig_logo.gif>
> Peter Korn | Accessibility Principal
> Phone: +1 650 5069522 
> 500 Oracle Parkway | Redwood City, CA 94065 
> <green-for-email-sig_0.gif> Oracle is committed to developing practices and products that help protect the environment

Received on Friday, 13 July 2012 01:26:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:17:44 UTC