19:49:08 RRSAgent has joined #au 19:49:09 logging to http://www.w3.org/2009/07/20-au-irc 19:49:15 Zakim, this will be AUWG 19:49:15 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 49 minutes ago 19:49:20 Meeting: WAI AU 19:50:28 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2009JulSep/0010.html 19:50:41 Regrets: Ann M. 19:58:38 jeanne has joined #au 19:59:47 WAI_AUWG()3:00PM has now started 19:59:54 +Jeanne 20:00:26 +??P1 20:02:07 zakim, ??P1 is really Jan 20:02:07 +Jan; got it 20:02:52 +Tim_Boland 20:03:33 +[IPcaller] 20:04:10 zakim, [IPcaller] is really Jutta 20:04:10 +Jutta; got it 20:04:15 +Greg_Pisocky 20:04:51 ARonksley has joined #au 20:04:56 Greg has joined #au 20:05:07 CHair: Jutta Treviranus 20:05:11 Chair: Jutta Treviranus 20:06:48 +Joshue 20:07:15 Greg can scribe 20:07:42 zakim, Joshue is really ARonksley 20:07:42 +ARonksley; got it 20:07:48 Scribe: Greg 20:08:17 http://lists.w3.org/Archives/Public/w3c-wai-au/2009JulSep/0010.html 20:08:48 Topic: Real-time publishing Note 20:09:16 jtrevir has joined #au 20:09:21 New editors draft: http://www.w3.org/WAI/AU/2009/ED-ATAG20-20090717/ 20:09:37 First item on agenda, take a look at Real Time publishing Note on the new editors draft 20:09:37 Real-time publishing: ATAG 2.0 applies to authoring tools with workflows that involve real-time publishing of web content (e.g., some collaborative tools). For these authoring tools, conformance to Part B of ATAG 2.0 may involve some combination of real-time accessibility supports and additional accessibility supports available after the real-time authoring session (e.g., the ability to add... 20:09:39 ...captions for audio that was initially published in real-time). For more information, see the Techniques - Appendix E: Real-time content production. 20:10:48 JR: Used to say real time authoring tools did not have to look at B, just A. This was considered a loophole, so here is the reworked content. 20:14:09 -Jutta 20:14:32 +??P5 20:15:00 zakim, ??P5 is really Jutta 20:15:00 +Jutta; got it 20:16:22 JS: Any problem addressing real time issues in Part A? 20:16:42 JR: Then agreed, the issue is Part B 20:17:31 JS above should be JR 20:18:58 Resolution: To use wording: Real-time publishing: ATAG 2.0 applies to authoring tools with workflows that involve real-time publishing of web content (e.g., some collaborative tools). For these authoring tools, conformance to Part B of ATAG 2.0 may involve some combination of real-time accessibility supports and additional accessibility supports available after the real-time authoring... 20:19:00 ...session (e.g., the ability to add captions for audio that was initially published in real-time). For more information, see the Techniques - Appendix E: Real-time content production. 20:19:16 Topic: Conformance Claim section 20:20:27 JR: Required Components of an ATAG 2.0 Conformance Claim... 20:25:51 All: Claimant name and affiliation.: No objections. 20:26:06 All: Conformance level satisfied.: No objections. 20:26:21 All: Authoring tool information:: No objections. 20:26:33 All: Included Technologies: No objections. 20:26:43 All: Excluded Technologies: No objections. 20:26:55 All: Declarations: No objections. 20:27:13 That completes the conformance section 20:27:29 Topic: B.2.1.X proposal 20:27:37 -ARonksley 20:27:37 Proposal on Decision Support by JT 20:28:29 -Tim_Boland 20:29:37 +ARonksley 20:30:21 Add another success criteria to B.2.1.x 20:31:19 http://www.w3.org/WAI/AU/2009/ED-ATAG20-20090717/#principle-support-author 20:31:45 JT: Any objections to adding as a success criteria? 20:31:57 Techs: http://www.w3.org/WAI/AU/2009/ED-ATAG20-TECHS-20090717/#principle-support-author 20:32:30 -Jutta 20:33:01 +??P3 20:33:14 GP: How to determine what is the most accessible way 20:33:49 JT: Doesn't need to be "most accessible way"..just accessible vs not accessible 20:34:07 GP: OK as long as techniques are not ranked over each other 20:35:24 JT: Guidance can take various forms but its about ensuring authors can make informed choices 20:35:47 JR: Objectins? 20:36:16 Resolution: Add in new success criteria B.2.1.X Decision Support. 20:36:49 GP: Back on previous question... 20:37:29 GP: Would it be sufficient to have a mode where an author could turn off "onerous" 20:38:17 JR: Doesn't need to be oneours...not a requirement to force author behaviour 20:38:28 GP: But user might not want prompts etc 20:38:46 JT: Right it might just be extra text 20:39:11 GP: User jusdt wants to drop in images...because know where they go.... 20:39:26 GP: I see prompt...dialog...etc. in the examples in the techniques 20:39:43 JT: OK we need to modify that text to include less obtrusive choices] 20:39:48 -ARonksley 20:40:39 JR: Could we just keep it yellow until we get the tech examples woked out?> 20:40:43 GP: OK 20:40:58 JT: Example from iPhone dev kit.... 20:41:14 JR: Can you send a screenshot? 20:41:16 JT: Yes 20:41:31 Action JT: Screenshot of iphone dev enviro showing inobtrusive info 20:41:39 Created ACTION-174 - Screenshot of iphone dev enviro showing inobtrusive info [on Jutta Treviranus - due 2009-07-27]. 20:41:59 GP: I like the idea...but don't want to require authors to use it at a partilar time in every case 20:42:03 JT: Of course not 20:42:44 + +200000aaaa 20:44:12 -Greg_Pisocky 20:44:18 -??P3 20:44:37 JR: Please look at new approach in the techniques document 20:44:38 - +200000aaaa 20:46:23 -Jan 20:46:28 -Jeanne 20:46:30 WAI_AUWG()3:00PM has ended 20:46:31 Attendees were Jeanne, Jan, Tim_Boland, Jutta, Greg_Pisocky, ARonksley, +200000aaaa 20:47:03 RRSAgent, make minutes 20:47:03 I have made the request to generate http://www.w3.org/2009/07/20-au-minutes.html Jan 20:47:08 RRSAgent, set logs public 20:47:14 Zakim, bye 20:47:14 Zakim has left #au 20:47:23 RRSAgent, bye 20:47:23 I see 1 open action item saved in http://www.w3.org/2009/07/20-au-actions.rdf : 20:47:23 ACTION: JT to Screenshot of iphone dev enviro showing inobtrusive info [1] 20:47:23 recorded in http://www.w3.org/2009/07/20-au-irc#T20-41-31