19:49:44 RRSAgent has joined #au 19:49:44 logging to http://www.w3.org/2008/10/06-au-irc 19:49:49 Zakim, this will be AUWG 19:49:49 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 49 minutes ago 19:49:54 Meeting: WAI AU 19:50:08 Regrets: Roberto S., Jeanne S. 19:58:35 Regrets: Ann M. 20:01:04 zakim, code? 20:01:04 the conference code is 2894 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), Jan 20:01:15 AndrewRonksley has joined #au 20:01:54 WAI_AUWG()3:00PM has now started 20:02:01 +[IPcaller] 20:02:14 + +1.561.582.aaaa 20:02:15 zakim, [IPcaller] is really Jan 20:02:15 +Jan; got it 20:02:31 +Greg_Pisocky 20:02:55 zakim, +1.561.582.aaaa is really SueAnnN 20:02:55 +SueAnnN; got it 20:03:22 Sueann has joined #au 20:03:35 Greg has joined #au 20:03:51 Hi everyone 20:04:40 +??P9 20:05:06 zakim, ??P9 is really AndrewR 20:05:06 +AndrewR; got it 20:07:17 +Treviranus 20:09:58 Chair: Treviranus 20:10:34 Greg can scribe 20:10:36 Scribe: Greg 20:11:13 Publication Update 20:11:31 Results delayed due to illness 20:11:40 http://lists.w3.org/Archives/Public/w3c-wai-au/2008JulSep/att-0103/00-part 20:11:56 Action items from last call 20:11:56 Sorry, couldn't find user - items 20:12:09 +Tim_Boland 20:12:10 http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/0002.html 20:14:54 New proposed wording for Relationship to the Web Content Accessibility Guidelines (WCAG) 20:15:24 http://www.w3.org/WAI/AU/2008/WD-ATAG20-20080929/WD-ATAG20-20080929#def-Acc-Auth-Practice 20:23:36 ATAG 2.0 points to the WCAG 2.0 success criteria in order to define the ATAG 2.0 concept of "accessible authoring practices", which authoring tools are required to support in various ways. 20:24:08 Tim has joined #au 20:24:14 ATAG 2.0 points to the WCAG 2.0 success criteria in order to define the ATAG 2.0 concept of "accessible authoring practices", which authoring tools are required to support in various ways. 20:32:03 Web content accessibility problem: An aspect of Web content that violates a WCAG 2.0 success criteria. Each success criteria has an associated Level. 20:33:11 Web content accessibility problem: An aspect of Web content that violates a WCAG 2.0 success criteria. Each WCAG 2.0 success criteria has an associated Level. 20:33:54 Action: JR Use new text in relationship with WCAG section 20:33:54 Created ACTION-25 - Use new text in relationship with WCAG section [on Jan Richards - due 2008-10-13]. 20:37:34 ATAG 2.0 Conformance Claims are supported by WCAG conforming examples of Web content produced by the authoring tool (e.g., samples of automatically-generated content) 20:40:20 Jan and Jean to come up with rationale text for Part A 20:40:44 This is a W3C Public Working Draft. This draft integrates changes made 20:40:45 as a result of comments received on the 10 March 2008 Public Working 20:40:47 Draft and also includes changes intended to keep the document harmonized 20:40:48 with WCAG 2.0. Substantial changes include: 20:40:50 (1) Refocusing Part A ("Make the authoring tool user interface 20:40:51 accessible") on requirements that apply most specifically to Web content 20:40:53 authoring tools and away from generic accessibility guidelines. Instead, 20:40:54 ATAG 2.0 will continue to require WCAG conformance for Web-based 20:40:56 authoring tools and will add a requirement to follow standards and/or 20:40:57 platform conventions that benefit accessibility for non-Web-based tools. 20:40:59 This change will let the Working Group keep a focus on authoring tools 20:41:01 and avoid the need to repeat operating system specific information that 20:41:02 is already available elsewhere. 20:41:03 (2) Replacing the concept of "Web Content Accessibility Benchmark" with 20:41:05 a more straightforward relationship with WCAG 2.0. This has been made 20:41:06 possible by the progression of WCAG 2.0 to Candidate Recommendation 20:41:08 status on 30 April 2008. 20:41:09 The Working Group seeks feedback on the following points for this draft: 20:41:11 - Does the refocused Part A provide developers with sufficient guidance 20:41:12 on what must be done to ensure accessibility of authoring tools to 20:41:14 authors with disabilities? 20:41:17 - Does the more direct relationship with WCAG 2.0 make the ATAG 2.0 20:41:18 requirements more clear? 20:41:20 - Are there any other areas in which the guidelines may be lacking? 20:43:13 +1 20:43:21 +1 20:43:30 +1 20:43:42 JT, SN: OK 20:44:38 Agenda Setting for the F2F 20:45:16 Split scan document and issue along am and pm lines 20:47:50 All: Decide to put issue discussions at TPAC in the afternoon and do the document walkthrough in the morning. 20:49:03 Pisocky registered 20:49:51 http://www.w3.org/WAI/AU/2008/10f2f 20:49:53 http://www.w3.org/2002/09/wbs/35125/TPAC2008/ 20:52:51 Tracker issues discussion deferred until next week 20:53:09 Will continue to meet once a week until the face to face 20:53:33 Action: All to register for TPAC and if joining remote - send approx. schedule for joining. 20:53:33 Sorry, couldn't find user - All 20:53:50 -Tim_Boland 20:53:53 -SueAnnN 20:53:54 Meeting next Monday 20:53:54 -Treviranus 20:54:01 -Jan 20:54:02 -Greg_Pisocky 20:54:06 -AndrewR 20:54:08 WAI_AUWG()3:00PM has ended 20:54:10 Attendees were Jan, Greg_Pisocky, SueAnnN, AndrewR, Treviranus, Tim_Boland 20:54:11 RRSAgent, make minutes 20:54:11 I have made the request to generate http://www.w3.org/2008/10/06-au-minutes.html Jan 20:54:19 RRSAgent, set logs public 20:54:26 Zakim, bye 20:54:26 Zakim has left #au 20:54:33 RRSAgent, bye 20:54:33 I see 2 open action items saved in http://www.w3.org/2008/10/06-au-actions.rdf : 20:54:33 ACTION: JR Use new text in relationship with WCAG section [1] 20:54:33 recorded in http://www.w3.org/2008/10/06-au-irc#T20-33-54 20:54:33 ACTION: All to register for TPAC and if joining remote - send approx. schedule for joining. [2] 20:54:33 recorded in http://www.w3.org/2008/10/06-au-irc#T20-53-33