20:50:29 RRSAgent has joined #au 20:50:29 logging to http://www.w3.org/2011/03/07-au-irc 20:50:39 AleMiele has joined #au 20:50:45 Zakim, this will be AUWG 20:50:45 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 50 minutes ago 20:50:49 Meeting: WAI AU 20:51:00 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0072.html 20:51:14 Chair: Jutta Treviranus 20:51:35 Regrets: Cherie, AndrewR, AlastairC 20:59:33 WAI_AUWG()3:00PM has now started 20:59:40 +Jeanne 21:00:35 +??P1 21:01:35 -??P1 21:01:37 zaki, code? 21:01:42 zakim, code? 21:01:42 the conference code is 2894 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), Jan 21:01:55 +[IPcaller] 21:02:08 +??P1 21:02:08 zakim, [IPcaller] is really Jan 21:02:10 +Jan; got it 21:02:54 zakim, ??P1 is really Alessandro 21:02:54 +Alessandro; got it 21:03:11 zakim, Alessandro is really AleMiele 21:03:11 +AleMiele; got it 21:03:22 zakim, who's here? 21:03:22 On the phone I see Jeanne, Jan, AleMiele 21:03:24 On IRC I see AleMiele, RRSAgent, Zakim, Jan, trackbot 21:06:15 +Tim_Boland 21:07:40 +??P4 21:08:14 zakim, ??P4 is really Jutta 21:08:14 +Jutta; got it 21:08:34 +Sueann 21:09:33 Topic: Survey 21:10:12 http://www.w3.org/2002/09/wbs/35520/20110302z/results 21:10:29 Scribe: Jan 21:10:37 Topic: Definition of author 21:10:39 http://www.w3.org/2002/09/wbs/35520/20110302z/results#xq5 21:11:50 Resolution: All accept "People who use authoring tools to create or modify web content. The term may cover roles such as content authors, designers, programmers, publishers, testers, etc. (see also "Part B Conformance Applicability Note #6: Multiple author roles"). Some authoring tools control who may be an author by managing *author permissions*. " 21:12:02 Topic: Definition of authoring tool 21:12:09 http://www.w3.org/2002/09/wbs/35520/20110302z/results#xq7 21:12:48 +Greg 21:12:48 Resolution: All accept the new definition. 21:13:03 Sueann has joined #au 21:13:23 Topic: Wording of B.1.1.2 Content Auto-Generation During Authoring Sessions 21:13:28 http://www.w3.org/2002/09/wbs/35520/20110302z/results#xq9 21:13:57 @@B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG): Authors have the default option that, when web content is automatically generated during an authoring session, then one of the following is true: [Implementing B.1.1.2] 21:13:59 Note 1: Automatic generation includes automatically selecting templates for authors. 21:14:01 Note 2: This success criterion applies only to automatic processes specified by the authoring tool developer. It does not apply when author actions prevent generation of accessible web content. 21:14:02 (a) Accessible: The content is accessible web content (WCAG) without author input; or (b) Prompting: During the automatic generation process, authors are prompted for any required accessibility information (WCAG); or (c) Automatic Checking: After the automatic generation process, accessibility checking is automatically performed; or (d) Checking Suggested: After the automatic generation... 21:14:04 ...process, the authoring tool prompts authors to perform accessibility checking. The WCAG 2.0 Level A success criteria are met (Level A); or 21:14:06 The WCAG 2.0 Level A and Level AA success criteria are met (Level AA); or 21:14:08 The WCAG 2.0 Level A, Level AA, and Level AAA success criteria are met (Level AAA). 21:14:43 -Tim_Boland 21:16:18 Resolution: All accepts wording "Content Auto-Generation During Authoring Sessions (WCAG): Authors have the default option that, when web content is automatically generated during an authoring session, then one of the following is true:" 21:16:33 Topic: 2. B.2.1.1 Accessible Content Possible (WCAG) Proposal 21:17:06 http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0076.html 21:17:58 jeanne has joined #au 21:18:15 Jutta has joined #au 21:23:55 Resolution: All accept: http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0076.html 21:24:15 Topic: 3. Series of long-waiting non-normative (and hopefully minor) edits marked with a single "@": 21:27:22 Resolution: All accept: @The intent of this success criterion is to ensure that web content transformations intended only to optimize content do not result in the introduction of web content accessibility problems. 21:28:12 Resolution: All accept: @Pretty-print: A "pretty-print" tool reformats markup code to make it easier to read by programmers. The tool never makes changes to the markup tags. 21:29:00 @Video compression: A tool that compresses video does not automatically delete text tracks or secondary audio tracks since these may contain accessibility information. 21:29:18 Resolution: All accept @Video compression: A tool that compresses video does not automatically delete text tracks or secondary audio tracks since these may contain accessibility information. 21:30:04 @The intent of this success criterion is to increase the likelihood that text alternatives will be preserved by web content transformations. This is especially important because text alternatives, such as labels and long descriptions, can represent substantial investments of author effort. 21:30:44 Resolution: All accept: @The intent of this success criterion is to increase the likelihood that text alternatives will be preserved by web content transformations. This is especially important because text alternatives, such as labels and long descriptions, can represent substantial investments of author effort. 21:31:21 @Save as HTML: A word processor includes a "Save as Simple HTML" feature that re-codes word processor files into HTML where there is a one-to-one correspondence between elements. As a result, some word processor-specific content is lost (e.g., change tracking, footnotes). However, because of the existence of the tag in HTML, images are preserved and, in order to meet this success... 21:31:22 ...criterion, the text alternatives associated with the image are also preserved in HTML. 21:31:39 Resolution: All accept: @Save as HTML: A word processor includes a "Save as Simple HTML" feature that re-codes word processor files into HTML where there is a one-to-one correspondence between elements. As a result, some word processor-specific content is lost (e.g., change tracking, footnotes). However, because of the existence of the tag in HTML, images are preserved and, in order to... 21:31:40 ...meet this success criterion, the text alternatives associated with the image are also preserved in HTML. 21:33:38 OLD: The intent of this success criterion is to ensure that if authoring tools only allow authors the ability to modify a subset of the properties of a content element, then the properties required for conformance to WCAG 2.0 are included in that subset. 21:33:59 @The intent of this success criterion is to ensure that if authoring tools provide authors with content authoring support that goes beyond source editing (e.g., property dialogs, etc.) then accessibility information that is required for the content are similarly supported. In many cases, authoring tools support a subset of all of the possible properties that technologies might offer. This... 21:34:01 ...success criterion requires that the subset of supported properties must include properties required for conformance to WCAG 2.0. 21:35:24 Resolution: All accept: @The intent of this success criterion is to ensure that if authoring tools provide authors with content authoring support that goes beyond source editing (e.g., property dialogs, etc.) then accessibility information that is required for the content are similarly supported. In many cases, authoring tools support a subset of all of the possible properties that technologies mi 21:35:26 ght offer. This success criterion requires that the subset of supported properties must include properties required for conformance to WCAG 2.0. 21:36:57 Resolution: All accept: @ (e.g. an "Image Properties" dialog). 21:38:21 Resolution: All accept @Silverlight, Flex 21:39:29 http://www.w3.org/WAI/AU/2011/ED-IMPLEMENTING-ATAG20-20110228/#sc_b121 21:39:43 Topic: Implementing Success Criterion B.1.2.1 Restructuring and Recoding Transformations (WCAG) 21:49:17 Action JR: Replace value judgement term with negative connotation term and flesh out a, b,s,d a bit morew 21:49:18 Created ACTION-325 - Replace value judgement term with negative connotation term and flesh out a, b,s,d a bit morew [on Jan Richards - due 2011-03-14]. 21:51:21 JT: All members, esp from large companies, please make sure you have no more issues 21:51:39 JT: Next steps as well comment responses, implementation research 21:51:54 JS: Also we need to highlight what we think are the biggest changes 21:52:29 JS: For the status section 21:54:38 JT: We of course have considered all the comments, but we'd prefer not to have to approve comment reponsese point by point so will a 2 week window be sufficient? 21:54:51 SN: 2 weeks is pretty tough 21:55:16 SN: Esp with CSUN and spring break 21:55:26 JT: We be after CSUN 21:55:46 JT: What about splitting them into A and B 21:58:23 -Greg 21:58:25 JT: Will talk to everyone next wk - Mar 14 21:58:33 -Sueann 21:58:34 -Jutta 21:58:38 -AleMiele 22:06:14 -Jan 22:06:24 -Jeanne 22:06:25 WAI_AUWG()3:00PM has ended 22:06:27 Attendees were Jeanne, Jan, AleMiele, Tim_Boland, Jutta, Sueann, Greg 22:08:36 RRSAgent, make minutes 22:08:36 I have made the request to generate http://www.w3.org/2011/03/07-au-minutes.html Jan 22:08:43 RRSAgent, set logs public 22:08:49 Zakim, bye 22:08:49 Zakim has left #au 22:08:56 RRSAgent, bye 22:08:56 I see 1 open action item saved in http://www.w3.org/2011/03/07-au-actions.rdf : 22:08:56 ACTION: JR to Replace value judgement term with negative connotation term and flesh out a, b,s,d a bit morew [1] 22:08:56 recorded in http://www.w3.org/2011/03/07-au-irc#T21-49-17