Agenda May 6 th

Time: 2100 UTC        (4 PM US Eastern)
Number:  +1-617-761-6200, passcode 9224 
irc.w3.org 6665, channel #wai-wcag

  
Agenda for this week

1. issues and action items: 
http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0216.html 
starting with the 2nd open issue (693 - adopting wording) 
then 774 then 776.
 

2.  assign action items for A,B,C, and D

A)  Issues 381 and 702 - Clarify examples for 3.1
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=381>
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=702>
Action item:  Rewrite the examples to make them clearer.
Guideline 3.1: http://www.w3.org/TR/2004/WD-WCAG20-20040311/#meaning


B) Issues 511 and 694 - Examples for Guideline 2.5
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=511>
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=694>
Action item: propose more examples for 2.5
<http://www.w3.org/TR/2004/WD-WCAG20-20040311/#minimize-error>
no longer use term "graceful recovery" but need more examples.  after have 
more examples, get back to kansas and verify that issue covered.

C) Issue 565 - What is meant by "user error"
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=565>
Action item:  propose clarification of "user error." do we want to  limit 
"user errors" to "processes or tasks"?  or some other way?  define it as 
anything that requires input?  clearly link to accessibility barrier and 
show that it is not just usability.
<http://www.w3.org/TR/2004/WD-WCAG20-20040311/#minimize-error>

D) action item: issues review for guideline 2.4 (~20 issues logged)


3. other topics/recent threads
human testability -
http://lists.w3.org/Archives/Public/w3c-wai-gl/2004AprJun/0187.html

guideline 3.2: 
http://lists.w3.org/Archives/Public/public-comments-wcag20/2004May/0002.html

Received on Wednesday, 5 May 2004 01:51:13 UTC