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

Agenda Addenda ====================

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Thu, 27 Oct 2005 11:49:25 -0500
To: <w3c-wai-gl@w3.org>
Message-ID: <008101c5db16$638d5f60$8c17a8c0@NC6000BAK>
The following items will also be discussed today

We reached consensus at the F2F on these but we wanted to discuss and double
check them today because they are deletions etc. 

*	Guideline 1.2 L3 SC3 - audio descriptions (live multimedia).
Proposal to delete this success criterion 

*	RATIONALE: because it is almost impossible to do unless the live
multimedia is scripted so you know when people are not talking so you can
speak audio descriptions.  In that case we are only talking about live plays
or something and that was not seen as a major enough type of content on the
Web for us to have a success criteria all about it.

*	Guideline 1.3 L3 SC2 -   OK to go?
*	Guideline 1.4 L1 SC1 - remove. 

*	Rationale: if you conform to other success criteria (1.1 and 1.3)
then there are no further requirements. we're assuming that user agents
should or could change color of text and background for contrast as long as
the text is programmatically determined.

*	Guideline
<http://trace.wisc.edu/wcag_wiki/index.php?title=Proposed_Guide_to_3.1_L3_SC
1>  3.1 L3 SC1 proposal to delete, 

*	Rationale:  SC2 covers everything but very common words that are in
a standard dictionary. people with cognitive disabilities would be better
off using a dictionary that is tuned for them or that they are at least used
to than having each author specifying a different dictionary. it is better
for the user to pick the dictionary - something they are used to.

*	Guideline
<http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_3.2_L3_SC1>  3.2
L3 SC1 - proposal to combine with 3.2 L2 SC3
*	Guideline
<http://trace.wisc.edu/wcag_wiki/index.php?title=Guide_to_4.2_L2_SC_1>  4.2
L2 SC1 - proposal to delete.

*	Rationale:  moved to a general technique for 4.2 L1 sc6. Also, the
implication of the wording is that accessibility conventions would need to
be used even if they are not appropriate (e.g., "accesskey").   


Gregg & John




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

 

 
Received on Thursday, 27 October 2005 16:49:34 GMT

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