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

Hi Peter and Gregg

Gregg is totally correct that, from a WCAG2ICT perspective, we do not need to open up every item on which we have reached consensus. As a UI context "enthusiast" I totally accept that the agreed wording works very well here - and it does not need to be changed.

What Peter has written is, however, of great interest to the Mandate 376 folk as it is our intention to only add SCs to our "Applicability notes for WCAG 2.0 success criteria" table when a simple substitution of "UI context" for "web page" does not make the intent sufficiently clear. I do not think that 1.4.2 would need to be added to our table (and is not there currently).

Best regards

Mike
PS: During our WCAG2ICT work it has become clear that we will probably need to add more SCs to our table, thanks to the great insights that have come from the WCAG2ICT discussions (and that have been captured in the WCAG2ICT intent texts).

From: Gregg Vanderheiden [mailto:gv@trace.wisc.edu]
Sent: 13 July 2012 02:26
To: Peter Korn
Cc: public-wcag2ict-tf@w3.org
Subject: Re: Looking at SC 1.4.2 Audio Control with "UI Context"

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
--------------------------------------------------------
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<https://sites.google.com/site/wcag2ict/home/1-perceivable/14-make-it-easier-for-users-to-see-and-hear-content---including-separating-foreground-from-background/142-audio-control> 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<https://sites.google.com/site/wcag2ict/cross-cutting-issues-and-notes/user-interface-context/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><http://www.oracle.com/>
Peter Korn | Accessibility Principal
Phone: +1 650 5069522<tel:+1%20650%205069522>
500 Oracle Parkway | Redwood City, CA 94065
<green-for-email-sig_0.gif><http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment