20:51:04 RRSAgent has joined #au 20:51:05 logging to http://www.w3.org/2010/02/22-au-irc 20:51:10 Zakim, this will be AUWG 20:51:10 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 51 minutes ago 20:51:16 Meeting: WAI AU 20:51:40 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0061.html 20:52:04 Regrets: Ann M. 20:57:09 jeanne has joined #au 20:58:50 WAI_AUWG()3:00PM has now started 20:58:57 +Jeanne 21:00:51 +[IPcaller] 21:01:26 zakim, [IPcaller] is really Jan 21:01:26 +Jan; got it 21:02:57 +Greg_Pisocky 21:03:20 Greg has joined #au 21:07:37 + +1.561.582.aaaa 21:08:30 zakim, aaaa is really SueAnn 21:08:30 +SueAnn; got it 21:10:06 Chair: Jan Richards 21:10:29 Scribe: jeanne 21:10:41 Topic: Publishing planning 21:10:46 http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0060.html 21:12:14 JR: Review of the ATAG schedule for the next 8 weeks. 21:13:34 JS: This is a tentative schedule only. 21:13:34 Topic: 2- Working through survey 21:13:47 http://www.w3.org/2002/09/wbs/35520/20100210/results 21:15:37 ARonksley has joined #au 21:16:33 This success criterion pertains to the rendered properties of text on the screen, even if the properties differ from the web content being edited. For example, when an author has chosen custom display settings (as per Success Criterion A.2.3.1). 21:17:17 Resolution: Use "This success criterion pertains to the rendered properties of text on the screen, even if the properties differ from the web content being edited. For example, when an author has chosen custom display settings (as per Success Criterion A.2.3.1). " as 3rd,4th sentences in intent of A222 21:17:27 JS: ok with me as the second paragraph 21:19:07 +??P7 21:19:14 Sueann has joined #au 21:19:34 zakim, ??P7 is really ARonksley 21:19:34 +ARonksley; got it 21:19:59 Resolution: Accept text "The first requirement (a) applies only to the authoring tool user interface, which is the part of the authoring tool that developers have the most control over. In this case, there should not be keyboard traps. If authors can move focus to a component using standard keyboard navigation commands (e.g., using the tab key), then they must be able to move focus out of... 21:20:01 ...the component in the same way. The second requirement (b) applies to renderings of web content. Because the web content may contain keyboard handlers, the authoring tool may not be able to prevent keyboard traps entirely. Therefore, the requirement is only that the authoring tool be able to restore the keyboard focus to some known location. This known location could be outside of the... 21:20:02 ...rendered area (e.g., the menus) or it might be the next rendered element." 21:22:16 Resolution: Accept new text "Of course, the editing mechanisms are contingent on the web content containing the appropriate structure. For example, editing by structure would not be very effective in an HTML document composed of plain text in a pre element." in Intent of A341 21:24:25 Resolution: to accept Intent of Success Criterion A.3.4.2 text from http://www.w3.org/2002/09/wbs/35520/20100210/results 21:25:57 http://www.w3.org/WAI/AU/2010/ED-ATAG20-20100222/ 21:26:18 GP: I didn't know what was being replaced 21:26:43 JR: The question was "what does available mean?" from the commenter. 21:26:49 GP: I am ok with that 21:26:51 Resolution: Accept rewording "B.1.2.1 Preserve Accessibility Information (Minimum): Any accessibility information (WCAG 2.0 Level A) recognized in the input to any web content transformation is preserved as accessibility information in the output, if allowed by the web content technology of the output." 21:27:32 B.2.1.3 Other Technologies: If the authoring tool enables web content to be inserted that the authoring tool cannot be used to edit, then provide the author(s) can associate accessibility information with that web content. (Level A) 21:28:39 JR: Tim objected (see his survey comments) and Greg asked to reword for clarity. 21:29:08 JR: What is the difference between Edit and Modify, and can we just say Edit. 21:29:10 If the authoring tool can insert web content which it cannot subsequently edit or modify, then the author(s) can associate accessibility information with that web content 21:29:32 GP: Yes. 21:30:20 +Tim_Boland 21:31:13 Tim has joined #au 21:31:21 http://www.w3.org/2002/09/wbs/35520/20100210/results#xq7 21:33:52 TB: "association" has to be demonstrable and evident. 21:34:23 If the authoring tool can insert web content which it cannot subsequently edit, then the author(s) can associate accessibility information with that web content 21:34:28 JR: I think it will be easy to demonstrate, for example, a PDF file could have a linked HTML document. 21:34:37 TB: That would be clear for that example. 21:34:48 Resuliton: Accept: If the authoring tool can insert web content which it cannot subsequently edit, then the author(s) can associate accessibility information with that web content 21:34:58 Resolution: Accept: If the authoring tool can insert web content which it cannot subsequently edit, then the author(s) can associate accessibility information with that web content 21:35:35 Action JR: For B.2.1.3 write a sentence explaining associate. 21:35:35 Created ACTION-259 - For B.2.1.3 write a sentence explaining associate. [on Jan Richards - due 2010-03-01]. 21:38:31 TB: Is this normative? JR: It is a normative note. Because people know that not all checking can be semi automated or automated checking, it is important to have the note saying that instructions to the author what to check are the minimum. It is hard to draw the line. 21:38:40 TB: It seems like a loophole. 21:39:04 JR: It is somewhat, but it would be a poor tool that didn't provide some checking. 21:39:28 TR: But we should encourage semi-automated and automated checking. 21:39:45 JR: We have a whole section about this. Can we accept it? 21:39:56 TR: I would like to think about it some more. 21:40:22 Action TB: Report back to the group on checking automation thoughts. 21:40:22 Sorry, couldn't find user - TB 21:41:00 Action TB: Report back to the group on checking automation thoughts (SC B.2.2.1 Check Accessibility) 21:41:00 Sorry, couldn't find user - TB 21:42:48 Action: Boland to Report back to the group on checking automation thoughts (SC B.2.2.1 Check Accessibility) 21:42:48 Created ACTION-260 - Report back to the group on checking automation thoughts (SC B.2.2.1 Check Accessibility) [on Frederick Boland - due 2010-03-01]. 21:42:55 Resolution: Text accepted: B.2.2.4 Help Authors Locate: For any checks that require author judgment to determine whether a potential web content accessibility problem is correctly identified (i.e., manual checking and semi-automated checking), the relevant web content is identified (e.g., highlight the affected web content, displaying line numbers, etc.) (Level A) 21:43:49 B.2.2.7 Save Status for Repair: If repair assistance is not provided during checking, then the author(s) have the option to save a list of web content accessibility problems to facilitate later repair. (Level AA) 21:44:13 No objections 21:44:14 Resolution: To accept B.2.2.7 Save Status for Repair: If repair assistance is not provided during checking, then the author(s) have the option to save a list of web content accessibility problems to facilitate later repair. (Level AA) 21:45:30 Resolution: Accept New text for Related Resources for Success Criterion B.2.2.8: 21:46:00 B.2.2.9 Metadata for Repair: If repair assistance is not provided during checking, then the author(s) have the option to save a metadata listing of the web content accessibility problems to facilitate interoperability with external repair tools. (Level AAA) 21:47:24 GP: I am still not clear. 21:48:24 GP: ok, no objection. 21:48:43 Action: JR add some text to intent of B.2.29 explaining that extrenal tools are tools outside the conformance claim 21:48:43 Created ACTION-261 - Add some text to intent of B.2.29 explaining that extrenal tools are tools outside the conformance claim [on Jan Richards - due 2010-03-01]. 21:48:45 TB: Ok with included text that explains that external tool is not part of the conformance claim 21:49:10 Resolution: Accept text: B.2.2.9 Metadata for Repair: If repair assistance is not provided during checking, then the author(s) have the option to save a metadata listing of the web content accessibility problems to facilitate interoperability with external repair tools. (Level AAA) 21:49:58 Resolution: Accept "Note: While automated repair assistance or more advanced implementations of semi-automated repair assistance may improve the authoring experience, manual repair assistance is the minimum requirement to meet this success criterion (as well as success criteria B.2.3.1 and B.2.3.2)." 21:51:26 Templates Accessible (WCAG Level A): If the authoring tool automatically selects templates or pre-authored content, then the selections conform to WCAG 2.0 Level A when used. (Level A) Note: Templates may be complicated to check for accessibility due to their inherent incompleteness. The accessibility status of templates is instead measured by the accessibility of web content (in the final... 21:51:28 ...web content technology) created when the templates are used properly. 21:54:13 Note: Templates may not successfully pass accessibility checks due to their inherent incompleteness. The accessibility status of template should instead be measured by the accessibility of completed web content (in the final web content technology) created when the template is used properly. 21:55:10 Note: Templates may not pass accessibility checks due to their inherent incompleteness. The accessibility status of template should instead be measured by the accessibility of completed web content (in the final web content technology) created when the template is used properly. 21:55:52 Templates Accessible (WCAG Level A): If the authoring tool automatically selects templates or pre-authored content, then the selections conform to WCAG 2.0 Level A when used. (Level A) Note: Templates may not pass accessibility checks due to their inherent incompleteness. The accessibility status of template should instead be measured by the accessibility of completed web content (in the... 21:55:54 ...final web content technology) created when the template is used properly. 21:56:05 no objections 21:56:06 Action: JR change text to: Templates Accessible (WCAG Level A): If the authoring tool automatically selects templates or pre-authored content, then the selections conform to WCAG 2.0 Level A when used. (Level A) Note: Templates may not pass accessibility checks due to their inherent incompleteness. The accessibility status of template should instead be measured by the accessibility of... 21:56:07 Created ACTION-262 - Change text to: Templates Accessible (WCAG Level A): If the authoring tool automatically selects templates or pre-authored content, then the selections conform to WCAG 2.0 Level A when used. (Level A) Note: Templates may not pass accessibility checks due to their inherent incompleteness. The accessibility status of template should instead be measured by the accessibility of... [on Jan Richards - due 2010-03-01]. 21:56:08 ...completed web content (in the final web content technology) created when the template is used properly. 21:56:57 Resolution: Accept "The intent of this success criterion is to help ensure that authors are as likely to notice and use functions for addressing accessibility problems as functions for addressing other web content issues (e.g., invalid markup, syntax errors, spelling and grammar errors)." 21:57:12 Resolution: Accept Removing unused term "abbreviation" from glossary 21:58:09 Resolution: Keep Appendix B: How to refer to ATAG 2.0 from other documents 21:58:49 Topic: Links to glossary issue 21:58:51 http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0058.html 22:01:25 Resolution: Accept this approach http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0058.html 22:02:32 -Tim_Boland 22:02:36 -SueAnn 22:02:37 -Jan 22:02:38 -ARonksley 22:02:43 -Greg_Pisocky 22:02:52 ARonksley has left #au 22:03:02 RRSAgent, make minutes 22:03:02 I have made the request to generate http://www.w3.org/2010/02/22-au-minutes.html Jan 22:03:08 RRSAgent, set logs public 22:03:13 Zakim, bye 22:03:13 leaving. As of this point the attendees were Jeanne, Jan, Greg_Pisocky, +1.561.582.aaaa, SueAnn, ARonksley, Tim_Boland 22:03:13 Zakim has left #au 22:03:19 RRSAgent, bye 22:03:19 I see 6 open action items saved in http://www.w3.org/2010/02/22-au-actions.rdf : 22:03:19 ACTION: JR to For B.2.1.3 write a sentence explaining associate. [1] 22:03:19 recorded in http://www.w3.org/2010/02/22-au-irc#T21-35-35 22:03:19 ACTION: TB to Report back to the group on checking automation thoughts. [2] 22:03:19 recorded in http://www.w3.org/2010/02/22-au-irc#T21-40-22 22:03:19 ACTION: TB to Report back to the group on checking automation thoughts (SC B.2.2.1 Check Accessibility) [3] 22:03:19 recorded in http://www.w3.org/2010/02/22-au-irc#T21-41-00 22:03:19 ACTION: Boland to Report back to the group on checking automation thoughts (SC B.2.2.1 Check Accessibility) [4] 22:03:19 recorded in http://www.w3.org/2010/02/22-au-irc#T21-42-48 22:03:19 ACTION: JR add some text to intent of B.2.29 explaining that extrenal tools are tools outside the conformance claim [5] 22:03:19 recorded in http://www.w3.org/2010/02/22-au-irc#T21-48-43 22:03:19 ACTION: JR change text to: Templates Accessible (WCAG Level A): If the authoring tool automatically selects templates or pre-authored content, then the selections conform to WCAG 2.0 Level A when used. (Level A) Note: Templates may not pass accessibility checks due to their inherent incompleteness. The accessibility status of template should instead be measured by the accessibility of... [6] 22:03:19 recorded in http://www.w3.org/2010/02/22-au-irc#T21-56-06