19:47:37 RRSAgent has joined #au 19:47:37 logging to http://www.w3.org/2010/01/18-au-irc 19:47:45 Zakim, this will be AUWG 19:47:45 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start in 13 minutes 19:47:50 Meeting: WAI AU 19:48:31 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0019.html 19:49:14 Regrets: Andrwe R., SueAnn N. (partial) 19:57:32 jeanne has joined #au 19:58:40 WAI_AUWG()3:00PM has now started 19:58:47 +Jeanne 20:00:42 zakim, code? 20:00:42 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:08 + +0208123aaaa 20:01:27 +[IPcaller] 20:01:29 AnnM has joined #au 20:01:53 zakim, [IPcaller] is really Jan 20:01:53 +Jan; got it 20:03:51 - +0208123aaaa 20:04:17 + +0208123aabb 20:04:31 zakim, aabb is really AnnM 20:04:31 +AnnM; got it 20:06:56 +Tim_Boland 20:12:36 +??P15 20:13:13 Greg has joined #au 20:13:15 zakim, ??P15 is really 20:13:15 +really; got it 20:13:29 zakim,really is really Jutta 20:13:29 +Jutta; got it 20:14:59 +Greg_Pisocky 20:15:43 Chair: Jutta Treviranus 20:15:58 Scribe: Greg 20:17:06 Ourstanding reviews, MSFT, CNIB, Adobe 20:18:15 Pushlist Jeanne tracking on an spreadsheet. Has grown to approximately 70 contacts 20:20:01 Jeanne would like to take time next week to go through the gap analysis 20:20:12 JS: Next week - push list gap analysis 20:21:08 Next face to face meeting MSFT would like to host in Redmond in April 20:21:47 -AnnM 20:22:13 Potentially week of April 19, April 26 what works? 20:23:08 AnnM_ has joined #au 20:23:19 AI Jeanne create a survey question to determine best dates for 2 day face to face 20:24:00 Action Jeanne create a survey question to determine best dates for 2 day face to face 20:24:00 Created ACTION-226 - Create a survey question to determine best dates for 2 day face to face [on Jeanne Spellman - due 2010-01-25]. 20:24:22 +AnnM 20:25:42 Survey Results 20:26:05 Proposed 20:26:07 A.3.1.1 Keyboard Access (Minimum): All functionality of the *authoring tool* is operable through a *keyboard interface*, except for *freehand drawing*. (Level A) 20:27:34 5 accepted proposals, 1 recommend change 20:29:44 TB would like to verify some of the terms used in this proposal 20:30:21 Jeanne prefers the term "enhanced freehand drawing" 20:32:40 Objections to putting the note but highlighting the term "enhanced freehand drawing" to indicate ongoing search for a more acceptable term? 20:32:44 No objections 20:32:58 Action: JR to add the proposal on "A.3.1.1 Keyboard Access (Minimum): All functionality of the *authoring tool* is operable through a *keyboard interface*, except for *freehand drawing*" - highlighting "freehand drawing" as a tentative term 20:32:58 Created ACTION-227 - Add the proposal on "A.3.1.1 Keyboard Access (Minimum): All functionality of the *authoring tool* is operable through a *keyboard interface*, except for *freehand drawing*" - highlighting "freehand drawing" as a tentative term [on Jan Richards - due 2010-01-25]. 20:33:43 No more comments on item 1. On to item 2 rationale for B.2.5 20:34:00 Proposed 20:34:02 Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) has numerous benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility. 20:35:01 6 accepts, and 1 tentative accept, 20:36:51 JR: Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility. 20:38:06 Action: JR add in the new ratioanle for B.2.5: "Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility" 20:38:06 Created ACTION-228 - Add in the new ratioanle for B.2.5: "Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility" [on Jan Richards - due 2010-01-25]. 20:39:08 Next Action, proceed to review comments or go through Jan's actions re: Cynthia's comments? 20:39:10 Topic: JRs action items 20:39:13 http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0011.html 20:39:33 Decided to pursue Jan's action items re: Cynthia's comments 20:39:37 Topic: JR to Add "Remember" sections in context as proposed text... 20:41:25 Jan: Readers seem to overlook the note indicating this is NOT about automated checking 20:43:06 Any objections to keeping the notes where they are, or should they be improved? 20:43:50 Resolution: Keep the notes where they are - no "Remember" section 20:44:04 Notes should stay put. Perhaps adjust the style to make them more prominent, noticeable 20:44:31 Action Investigate ways notes can be more prominent, visible Jan and Jeanne 20:44:31 Sorry, couldn't find user - Investigate 20:44:52 Action: JS, JR investigate formatting the notes for visibility 20:44:53 Sorry, couldn't find user - JS, 20:47:12 Action JR: Link "Check" to a definition in SCB.2.2.1 20:47:12 Created ACTION-229 - Link "Check" to a definition in SCB.2.2.1 [on Jan Richards - due 2010-01-25]. 20:48:46 Note: While automated checking or more advanced implementations of 20:48:48 semi-automated checking are possible for many types of web content 20:48:49 accessibility problems, manual checking is the minimum requirement to 20:48:51 meet success criteria B.2.2.1, B.2.2.4 and B.2.2.10. In manual checking, 20:48:53 the authoring tool provides authors with instructions for detecting 20:48:55 problems, which authors must carry out by themselves without further 20:48:57 automated assistance. For more information on checking, see Implementing 20:48:58 ATAG 2.0 - Appendix B: Levels of Checking Automation. 20:52:12 Action JR: Add in this note text: "Note: While automated checking or more advanced implementations of semi-automated checking are possible for many types of web content accessibility problems, manual checking is the minimum requirement to meet success criteria B.2.2.1, B.2.2.4 and B.2.2.10. In manual checking, the authoring tool provides authors with instructions for detecting problems,... 20:52:12 Created ACTION-230 - Add in this note text: "Note: While automated checking or more advanced implementations of semi-automated checking are possible for many types of web content accessibility problems, manual checking is the minimum requirement to meet success criteria B.2.2.1, B.2.2.4 and B.2.2.10. In manual checking, the authoring tool provides authors with instructions for detecting problems,... [on Jan Richards - due 2010-01-25]. 20:52:14 ...which authors must carry out by themselves without further automated assistance. For more information on checking, see Implementing ATAG 2.0 - Appendix B: Levels of Checking Automation." 20:52:41 Topic: JR to Take A.3.6 back to drawing board 20:56:31 JR: Should we keep A.3.6 20:56:44 JT: Question is are there settings related to authoring tools 20:57:09 TB: I think we identified settings related to authoring tools 21:00:08 Resolution: The WG decides to keep A.3.6 21:02:47 Action: JR use proposed text for A.3.6.1 "Save Settings: Authoring tool *display settings* and *control settings* are saved between sessions. (Level AA) + Define "control settings" as: Settings that relate to how the author controls the authoring tool, for example using the keyboard or mouse. 21:02:47 Created ACTION-231 - Use proposed text for A.3.6.1 "Save Settings: Authoring tool *display settings* and *control settings* are saved between sessions. (Level AA) + Define "control settings" as: Settings that relate to how the author controls the authoring tool, for example using the keyboard or mouse. [on Jan Richards - due 2010-01-25]. 21:03:35 Action JR: Use proposed text for "A.3.6.2 Multiple Sets: The author(s) can save and reload multiple sets of any authoring tool *display settings* and *control settings*.(Level AAA)" 21:03:35 Created ACTION-232 - Use proposed text for "A.3.6.2 Multiple Sets: The author(s) can save and reload multiple sets of any authoring tool *display settings* and *control settings*.(Level AAA)" [on Jan Richards - due 2010-01-25]. 21:05:40 JR: Proposed: A.3.6.X Respect Platform Settings: The authoring tool respects platform *display settings* and *control settings*. (Level AA) Note: As per Guideline A.2.3, the author's display settings must still be independent of the web content being edited. 21:06:13 Action: JR to add "A.3.6.X Respect Platform Settings: The authoring tool respects platform *display settings* and *control settings*. (Level AA) Note: As per Guideline A.2.3, the author's display settings must still be independent of the web content being edited." 21:06:13 Created ACTION-233 - Add "A.3.6.X Respect Platform Settings: The authoring tool respects platform *display settings* and *control settings*. (Level AA) Note: As per Guideline A.2.3, the author's display settings must still be independent of the web content being edited." [on Jan Richards - due 2010-01-25]. 21:07:25 Topic: JR to reword proposal with applicability instead of responsibility. 21:08:13 JR: Proposed: "Applicability after the *End of an Authoring Sessions*: For *author-generated content*, the requirements of *Part B* apply only during *authoring sessions*. For example, if the *author* includes a third-party feed in their *web content*, the *authoring tool* is not required to provide *checking* for *web content accessibility problems* in that feed after the *end of the... 21:08:15 ...authoring session*. In contrast, for *automatically-generated content*, Part B continues to apply after the *end of an authoring session*. For example, if the site-wide templates of a content management system are updated, these would be required to meet the accessibility requirements for *automatically generated content*." 21:11:32 Action: JR to add in text : ""Applicability after the *End of an Authoring Sessions*: For *author-generated content*, the requirements of *Part B* apply only during *authoring sessions*. For example, if the *author* includes a third-party feed in their *web content*, the *authoring tool* is not required to provide *checking* for *web content accessibility problems* in that feed after the... 21:11:33 Created ACTION-234 - Add in text : ""Applicability after the *End of an Authoring Sessions*: For *author-generated content*, the requirements of *Part B* apply only during *authoring sessions*. For example, if the *author* includes a third-party feed in their *web content*, the *authoring tool* is not required to provide *checking* for *web content accessibility problems* in that feed after the... [on Jan Richards - due 2010-01-25]. 21:11:34 ...*end of the authoring session*. In contrast, for *automatically-generated content*, Part B continues to apply after the *end of an authoring session*. For example, if the site-wide templates of a content management system are updated, these would be required to meet the accessibility requirements for *automatically generated content*." 21:12:09 Topic: JR to Write some intent text for B.1.1.1 to explain that instead of accessibility supported uses we took the decision support approach in B.2.1 21:15:09 http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0011.html 21:22:46 Resolution: THe WG agrees that the "user supported" requirement in WCAG2 needs to be addressed in ATAG 2.0 21:24:01 Resolution: THe WG agrees that the "user supported" requirement in WCAG2 needs to be addressed in the "Relationship to WCAG 2.0" section 21:32:37 Resolution: The WG agrees to exempt authoring tools from needing to document "accessibility supported uses of technology" for any references to WCAG2 because it is the installer/author who determines the environment (language, dialect, author group, end user group, etc.) of the authoring tool 21:33:05 Resolution: JR, Jeanne will take the final wording to CG 21:34:23 Action: JR clarify in the "accessibility supported" piece that the onus is on the installer/author 21:34:23 Created ACTION-235 - Clarify in the "accessibility supported" piece that the onus is on the installer/author [on Jan Richards - due 2010-01-25]. 21:35:30 Topic: Cynthia's comments (cont) 21:35:35 http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0058.html 21:35:45 Topic: B.2.2.4 Help Authors Locate.... 21:39:52 -Tim_Boland 21:44:08 Action JR: Clarify B.2.2.4 comment response 21:44:08 Created ACTION-236 - Clarify B.2.2.4 comment response [on Jan Richards - due 2010-01-25]. 21:44:20 -Jan 21:44:21 -Greg_Pisocky 21:44:21 -Jutta 21:44:26 -AnnM 21:44:27 -Jeanne 21:44:27 WAI_AUWG()3:00PM has ended 21:44:28 Attendees were Jeanne, +0208123aaaa, Jan, +0208123aabb, AnnM, Tim_Boland, Jutta, Greg_Pisocky 21:44:38 RRSAgent, make minutes 21:44:38 I have made the request to generate http://www.w3.org/2010/01/18-au-minutes.html Jan 21:44:44 RRSAgent, set logs public 21:44:50 Zakim, bye 21:44:50 Zakim has left #au 21:44:55 RRSAgent, bye 21:44:55 I see 11 open action items saved in http://www.w3.org/2010/01/18-au-actions.rdf : 21:44:55 ACTION: JR to add the proposal on "A.3.1.1 Keyboard Access (Minimum): All functionality of the *authoring tool* is operable through a *keyboard interface*, except for *freehand drawing*" - highlighting "freehand drawing" as a tentative term [1] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T20-32-58 21:44:55 ACTION: JR add in the new ratioanle for B.2.5: "Providing accessible templates and other pre-authored content (e.g., clip art, synchronized media, widgets, etc.) can have several benefits, including: immediately improving the accessibility of content being edited, reducing the effort required of authors, and demonstrating the importance of accessibility" [2] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T20-38-06 21:44:55 ACTION: JS, JR investigate formatting the notes for visibility [3] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T20-44-52 21:44:55 ACTION: JR to Link "Check" to a definition in SCB.2.2.1 [4] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T20-47-12 21:44:55 ACTION: JR to Add in this note text: "Note: While automated checking or more advanced implementations of semi-automated checking are possible for many types of web content accessibility problems, manual checking is the minimum requirement to meet success criteria B.2.2.1, B.2.2.4 and B.2.2.10. In manual checking, the authoring tool provides authors with instructions for detecting problems,... [5] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T20-52-12 21:44:55 ACTION: JR use proposed text for A.3.6.1 "Save Settings: Authoring tool *display settings* and *control settings* are saved between sessions. (Level AA) + Define "control settings" as: Settings that relate to how the author controls the authoring tool, for example using the keyboard or mouse. [6] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T21-02-47 21:44:55 ACTION: JR to Use proposed text for "A.3.6.2 Multiple Sets: The author(s) can save and reload multiple sets of any authoring tool *display settings* and *control settings*.(Level AAA)" [7] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T21-03-35 21:44:55 ACTION: JR to add "A.3.6.X Respect Platform Settings: The authoring tool respects platform *display settings* and *control settings*. (Level AA) Note: As per Guideline A.2.3, the author's display settings must still be independent of the web content being edited." [8] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T21-06-13 21:44:55 ACTION: JR to add in text : ""Applicability after the *End of an Authoring Sessions*: For *author-generated content*, the requirements of *Part B* apply only during *authoring sessions*. For example, if the *author* includes a third-party feed in their *web content*, the *authoring tool* is not required to provide *checking* for *web content accessibility problems* in that feed after the... [9] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T21-11-32 21:44:55 ACTION: JR clarify in the "accessibility supported" piece that the onus is on the installer/author [10] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T21-34-23 21:44:55 ACTION: JR to Clarify B.2.2.4 comment response [11] 21:44:55 recorded in http://www.w3.org/2010/01/18-au-irc#T21-44-08