20:58:42 RRSAgent has joined #wcag-teamc 20:58:42 logging to http://www.w3.org/2006/06/05-wcag-teamc-irc 20:58:46 rrsagent, make log world 20:58:50 rrsagent, do not start a new log 20:58:55 meeting: WCAG Team C 20:58:59 chair: Andi Snow-Weaver 20:59:04 scribe: Michael 20:59:10 agenda: http://lists.w3.org/Archives/Public/public-wcag-teamc/2006Jun/0012.html 20:59:18 Zakim has joined #wcag-teamc 20:59:24 zakim, list conferences 20:59:24 I see no active conferences 20:59:25 scheduled at this time are WAI_EOWG(tf)3:30PM, WAI_AUWG()3:00PM, WS_AddrWG()4:00PM 20:59:38 zakim, bye 20:59:38 Zakim has left #wcag-teamc 21:00:02 Becky has joined #wcag-teamc 21:04:39 present: Andi Snow-Weaver, Becky Gibson, Michael Cooper 21:04:47 topic: Annotated Checklists 21:07:33 present+ Cynthia Shelley 21:08:23 Might be difficult to understand when you have to implement all or some technology specific techniques based on baseline, situation... 21:09:31 Looks a lot like a normative doc (though we know it isn't), how is it kept current as techniques added? 21:09:44 Come to think of it, what is process to vet new techniques? 21:10:38 Sofia has joined #wcag-teamc 21:10:39 present+ Sofia Celic 21:12:53 Would like to see the different conformance levels in the doc 21:13:13 Discussed in the past having various queries to see various views of the stuff on the fly 21:13:45 Would be clearer if a table with checkboxes in a column 21:14:50 Would like to be able to check which "situation" is being used in a given situation, and only see the techniques relevant to that 21:15:50 Not sure if this should exist as a static document, only useful if dynamic and able to incorporate updates 21:17:26 Some of the dynamic abilities like technique submission from public really needed 21:23:15 topic: Comments 629-632 21:24:14 topic: Issue 624 21:27:59 state at Level 1 may not be doable or sufficiently important in all technologies 21:28:16 proposals at http://lists.w3.org/Archives/Public/public-wcag-teamc/2006Jun/0010.html 21:29:08 concern that a requirement about setting focus could go awry 21:29:57 resolution: reject issue with following wording 21:31:45 action: Becky to modify proposed wording from proposal to add focus and state issues 21:32:35 http://trace.wisc.edu/wcag_wiki/index.php?title=Main_Page#Group_Assignment_BY_GUIDELINE 21:33:27 Recommendations should be made to issue directly, using instructions at http://trace.wisc.edu/wcag_wiki/index.php?title=Main_Page#Group_Assignment_BY_GUIDELINE 21:33:48 topic: Issues 629-632 21:35:38 proposal at http://lists.w3.org/Archives/Public/public-wcag-teamc/2006Jun/0011.html 21:43:52 resolution: reject issue, but propose advisory techniques to help mitigate 21:44:15 action: Becky to propose wording to explain why issue rejected 21:44:59 action: everyone to review proposals by end of day Tuesday so Andi can create survey 21:45:55 http://www.w3.org/WAI/GL/2006/06/01-wai-wcag-minutes 21:51:33 topic: Issue 558 22:01:54 hold to next week 22:02:37 rrsagent, generate minutes 22:02:37 I have made the request to generate http://www.w3.org/2006/06/05-wcag-teamc-minutes.html Michael 22:02:46 Andi has left #wcag-teamc 22:02:57 action: becky to reseach teamb rationale on the 1.3 color SC for next week 22:03:07 rrsagent, generate minutes 22:03:07 I have made the request to generate http://www.w3.org/2006/06/05-wcag-teamc-minutes.html Michael 22:09:08 rrsagent, bye 22:09:08 I see 4 open action items saved in http://www.w3.org/2006/06/05-wcag-teamc-actions.rdf : 22:09:08 ACTION: Becky to modify proposed wording from proposal to add focus and state issues [1] 22:09:08 recorded in http://www.w3.org/2006/06/05-wcag-teamc-irc#T21-31-45 22:09:08 ACTION: Becky to propose wording to explain why issue rejected [2] 22:09:08 recorded in http://www.w3.org/2006/06/05-wcag-teamc-irc#T21-44-15 22:09:08 ACTION: everyone to review proposals by end of day Tuesday so Andi can create survey [3] 22:09:08 recorded in http://www.w3.org/2006/06/05-wcag-teamc-irc#T21-44-59 22:09:08 ACTION: becky to reseach teamb rationale on the 1.3 color SC for next week [4] 22:09:08 recorded in http://www.w3.org/2006/06/05-wcag-teamc-irc#T22-02-57