19:51:15 RRSAgent has joined #au 19:51:15 logging to http://www.w3.org/2011/06/13-au-irc 19:51:20 Zakim, this will be AUWG 19:51:21 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 51 minutes ago 19:51:27 Meeting: WAI AU 19:51:38 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2011AprJun/0074.html 19:54:58 regrets: Cherie E. 19:55:06 regrets: Cherie E., Allessandro M. 19:59:25 sure. I will do it probably on Wednesday. Maybe tomorrow. 20:00:19 WAI_AUWG()3:00PM has now started 20:00:26 +[Microsoft] 20:00:55 +??P3 20:01:17 +Jeanne 20:01:39 s/ sure. I will do it probably on Wednesday. Maybe tomorrow. // 20:01:53 zakim, [Microsoft] is really Alex 20:01:53 +Alex; got it 20:02:31 zakim, ??P3 is really Jan 20:02:31 +Jan; got it 20:04:05 Chair: Jutta Treviranus 20:04:14 Scribe: Jan 20:05:44 + +1.571.765.aaaa 20:06:20 zakim, aaaa is really Greg 20:06:20 +Greg; got it 20:07:13 Greg has joined #au 20:07:15 +??P6 20:08:12 zakim, ??P6 is really Jutta 20:08:12 +Jutta; got it 20:08:33 zakim, who's here? 20:08:33 On the phone I see Alex, Jan, Jeanne, Greg, Jutta 20:08:34 On IRC I see Greg, RRSAgent, Zakim, Jan, jeanne, trackbot 20:11:07 + +1.561.200.aabb 20:11:38 zakim, aabb is really Sueann 20:11:38 +Sueann; got it 20:12:00 Topic: 1. The survey for reviewing the AA comments 20:12:21 Topic: B.2.5 - GL41 20:12:45 JR: Has a proposal 20:12:54 Topic: B.3.2 - WCAGWG27 20:14:31 Resolution: Accept response to B.3.2 - WCAGWG27 20:14:39 Topic: B.3.2 - MS57 20:16:27 +Tim_Boland 20:17:44 JT: B.3.2.4 At Least as Prominent: Accessible content support features are at least as prominent as features related to other types of web content problems (e.g., invalid markup, syntax errors, spelling and grammar errors). 20:18:51 JT: B.3.2.4 At Least as Prominent: Accessible content support features are at least as prominent as features related to other types of web content problems (i.e., invalid markup, syntax errors, spelling and grammar errors). 20:21:13 JT: B.3.2.4 At Least as Prominent: Accessible content support features are at least as prominent as features related to either invalid markup, syntax errors, spelling or grammar errors. 20:22:34 Resolution: Accept new wording " B.3.2.4 At Least as Prominent: Accessible content support features are at least as prominent as features related to either invalid markup, syntax errors, spelling or grammar errors." 20:22:49 Action JR: Change wording to resolved for B.3.2.4 20:22:50 Created ACTION-347 - Change wording to resolved for B.3.2.4 [on Jan Richards - due 2011-06-20]. 20:22:58 Topic: B.3.2 - MS58 20:23:14 AL: Resolved above. 20:23:22 Topic: B.3.2 - GL19 20:23:51 Resolution: Accept response to B.3.2 - GL19 20:24:01 Topic: B.3.2 - OC31 20:24:21 JR: Resolved above. 20:24:28 Topic: B.3.4 - MS59 20:48:31 1. Explain use of "range" 20:48:33 NEW DEFINITON: "Range": 20:48:35 More than one item within a set that is also more than one item. See also "Range" in the (informative) Introduction. 20:48:36 NEW SECTION IN THE (INFORMATIVE) INTRODUCTION: 20:48:38 ATAG 2.0 uses the term "range" in several success criteria in which absolute measurements may not be practical (e.g. the set of all help documentation examples, the set of all templates, etc.). While the strict testable requirement is the definition "More than one item within a set that is also more than one item", implementers are strongly encouraged to implement the success criteria more widely. 20:48:57 OLDER VERSION 20:49:34 NEW DEFINITON: "Range": 20:49:35 More than one item within a multi-item set. 20:49:37 (Informative) Note: ATAG 2.0 uses the term "range" in several success criteria in which absolute measurements may not be practical (e.g. the set of all help documentation examples, the set of all templates, etc.). While the strict testable requirement is the definition "More than one item within a multi-item set ", implementers are strongly encouraged to implement the success criteria more... 20:49:38 ...broadly. 20:55:42 source: http://lists.w3.org/Archives/Public/w3c-wai-au/2011AprJun/0061.html 20:56:21 JT: But it would be just as a unacceptable to show inaccessible step as bad xyntax in example 20:56:38 GP: But it could be a different point in timeline 20:57:15 JT: Right, so then examples of breaking accessibility at publishing 20:57:22 GP: How do you test that? 20:57:33 JT: Test what? 20:58:11 -Tim_Boland 20:58:18 GP: How do you know you've done that...lots of actions having to do with images....at some point you need accessibility demonstrated other times not important 20:58:35 GP: Sampling wouldn't work... 20:58:43 JT: Not suggesting sampling 20:59:37 JT: Proposing to turn it around and to say don't do harm 21:00:15 JR: So the class of documentation at the end 21:00:49 JT: Or some things that heppen in the middle...like images of text in some context 21:04:18 -Jeanne 21:04:20 -Sueann 21:04:20 -Alex 21:04:20 -Jutta 21:04:23 -Greg 21:05:11 Action: JR to attempt to propose text taking into account context of inaccessible examples and testing practicality. 21:05:11 Created ACTION-348 - Attempt to propose text taking into account context of inaccessible examples and testing practicality. [on Jan Richards - due 2011-06-20]. 21:05:17 -Jan 21:05:19 WAI_AUWG()3:00PM has ended 21:05:21 Attendees were Jeanne, Alex, Jan, +1.571.765.aaaa, Greg, Jutta, +1.561.200.aabb, Sueann, Tim_Boland 21:10:05 RRSAgent, make minutes 21:10:05 I have made the request to generate http://www.w3.org/2011/06/13-au-minutes.html Jan 21:10:11 RRSAgent, set logs public 21:10:15 Zakim, bye 21:10:15 Zakim has left #au 21:10:20 RRSAgent, bye 21:10:20 I see 2 open action items saved in http://www.w3.org/2011/06/13-au-actions.rdf : 21:10:20 ACTION: JR to Change wording to resolved for B.3.2.4 [1] 21:10:20 recorded in http://www.w3.org/2011/06/13-au-irc#T20-22-49 21:10:20 ACTION: JR to attempt to propose text taking into account context of inaccessible examples and testing practicality. [2] 21:10:20 recorded in http://www.w3.org/2011/06/13-au-irc#T21-05-11