W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2005

RE: 2.2 L3 SC2 rewording

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Thu, 17 Nov 2005 14:51:26 -0600
To: "'Gregg Vanderheiden'" <gv@trace.wisc.edu>, <w3c-wai-gl@w3.org>
Message-ID: <012501c5ebb8$ae3780b0$ee8cfea9@NC6000BAK>
Cleaned up it looks like

 

*	Interruptions, such as updated content, can be postponed or
suppressed by the user, except those involving an emergency
<http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_2.2_L3_SC2#emergen
cydef> . 


Key terms 


emergency 

a sudden, unexpected situation or occurrence that requires immediate action
to preserve health, safety or property 

 

 

  _____  

From: Gregg Vanderheiden [mailto:gv@trace.wisc.edu] 
Sent: Thursday, November 17, 2005 2:45 PM
To: w3c-wai-gl@w3.org
Subject: 2.2 L3 SC2 rewording

 

 

The following appears to be editorial (wording) but it is to a success
criterion so I am posting to the list

 

 

WAS

Non-emergency interruptions, such as updated content, can be postponed or
suppressed by the user.

 

non-emergency interruption : an interruption that is not a sudden,
unexpected situation or occurrence that requires immediate action to
preserve health, safety or property

 

 

NEW PROPOSED (From F2F but no recorded resolution)

<proposed>The user can postpone or suppress all interruptions, except those
involving emergencies.</proposed>

 

rationale: gets us out of using "non-emergency" in SC so we can define
"emergency" instead

 

 

 


Gregg

------------------------

Gregg C Vanderheiden Ph.D. 
Professor - Depts of Ind. Engr. & BioMed Engr.
Director - Trace R & D Center 
University of Wisconsin-Madison 
< <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848  
For a list of our list discussions http://trace.wisc.edu/lists/

 <http://trace.wisc.edu:8080/mailman/listinfo/>  

 

 
Received on Thursday, 17 November 2005 20:51:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:40 GMT