20:56:57 RRSAgent has joined #au 20:56:57 logging to http://www.w3.org/2011/02/07-au-irc 20:57:05 Zakim, this will be AUWG 20:57:05 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 57 minutes ago 20:57:14 Meeting: WAI AU 20:58:26 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0034.html 20:58:32 Chair: Jutta Treviranus 20:59:00 Regrets: Cherie E. 20:59:34 AleMiele has joined #au 21:00:35 WAI_AUWG()3:00PM has now started 21:00:42 +Jeanne 21:00:46 alastairc has joined #au 21:01:40 + +1.571.765.aaaa 21:02:15 +[IPcaller] 21:02:59 +??P5 21:03:02 gpisocky has joined #au 21:03:32 zakim, ??P5 is really Alastair 21:03:32 +Alastair; got it 21:03:45 zakim, [IPcaller] is really Jan 21:03:45 +Jan; got it 21:04:11 +??P6 21:04:17 +[Microsoft] 21:04:54 zakim, [Microsoft] is really Alex 21:04:55 +Alex; got it 21:05:39 scribe: jeanne 21:05:41 zakim, ??P6 is really AleMiele 21:05:41 +AleMiele; got it 21:06:38 Topic: Finish Jan 24 survey 21:07:09 Topic: Definition of programmatically determined (programmatically determinable) 21:07:17 zakim, who's here? 21:07:17 On the phone I see Jeanne, +1.571.765.aaaa, Jan, Alastair, AleMiele, Alex 21:07:19 On IRC I see gpisocky, alastairc, AleMiele, RRSAgent, Zakim, Jan, jeanne, trackbot 21:07:32 zakim, aaaa is really Greg 21:07:32 +Greg; got it 21:08:03 http://www.w3.org/2002/09/wbs/35520/20110113/results#xq11 21:11:47 5 accepts, Jutta requests grammar edits. Alastair had changes for clarity. 21:12:09 When information is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts: 21:12:11 + +1.561.582.aabb 21:12:29 zakim, aabb is really Sueann 21:12:29 +Sueann; got it 21:12:44 Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of a platform accessibility services, general-purpose APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information. 21:12:44 +[IPcaller] 21:13:00 zakim, [IPcaller] is really Jutta 21:13:00 +Jutta; got it 21:13:02 Sueann has joined #au 21:14:24 ARonksley has joined #au 21:14:41 Processing content: Is the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup). 21:15:29 action: jeanne to create a new survey to look for a new time for meeting. 21:15:30 Created ACTION-319 - Create a new survey to look for a new time for meeting. [on Jeanne Spellman - due 2011-02-14]. 21:16:14 Processing content: Whether the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup). 21:16:24 +??P0 21:16:29 Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of a platform accessibility services, general-purpose APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information. 21:16:40 When information is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts: 21:16:46 - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of a platform accessibility services, general-purpose APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information. 21:16:52 - Processing content: Is the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup). 21:17:51 Information that is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts: 21:18:02 +Tim_Boland 21:18:19 Information that is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts: 21:18:37 > - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, general-purpose APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information. 21:18:39 jutta has joined #au 21:18:52 - Processing content: Whether the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup). 21:20:13 SN: Suggests: Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information. 21:20:53 Information that is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts: 21:21:01 - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, APIs, and in some cases document object models. For web-based user interfaces, this means following WCAG 2.0 so that the user agent can pass on the information. 21:21:08 - Processing content: Whether the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup). 21:23:53 For web-based user interfaces, this means ensuring that the user agent can pass on the information (e.g., through the use of ARIA). 21:24:19 - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, APIs, and in some cases document object models. For web-based user interfaces, this means ensuring that the user agent can pass on the information (e.g., through the use of ARIA). 21:24:28 Alex: WCAG doesn't really address this directly. It may be confusing. 21:24:39 Information that is encoded in a way that allows different software, including assistive technologies, to extract and present the information in different modalities. ATAG 2.0 uses this term in two contexts: 21:24:46 - Communication between the authoring tool and assistive technology: For non-web-based user interfaces, this means making use of platform accessibility services, APIs, and in some cases document object models. For web-based user interfaces, this means ensuring that the user agent can pass on the information (e.g., through the use of ARIA). 21:24:52 - Processing content: Whether the authoring tool able to extract information from the content (e.g., to extract the language of content from the markup). 21:25:17 - Processing content: Whether the authoring tool is able to extract information from the content (e.g., to extract the language of content from the markup). 21:25:31 Resolution: All accept the wording above for programmatically determinable. 21:26:04 Topic: Definition of Definition of recognized 21:26:41 http://www.w3.org/2002/09/wbs/35520/20110113/results#xq13 21:27:05 Resolution: All accept remove defn of recognized 21:27:38 Topic: Definition of sequential keyboard navigation 21:28:38 http://www.w3.org/2002/09/wbs/35520/20110113/results#xq14 21:30:54 Using a keyboard interface to navigate one-by-one through all of the items in an ordered set (e.g. menu items, form fields, etc.). This is in contrast to direct navigation methods such as keyboard shortcuts and bypass links. 21:32:45 Resolution: All accept add "sequential keyboard navigation" 21:32:55 no objections 21:33:19 This finishes the 24 january survey 21:34:05 http://www.w3.org/2002/09/wbs/35520/20110204/results#xq2 21:34:19 Topic: Renaming "Applicability Notes" as "Conformance Conditions" 21:34:25 http://www.w3.org/2002/09/wbs/35520/20110204/results#xq2 21:36:26 Alex: they are not conditions, they are disclaimers of W3C. 21:36:48 Jeanne: Not all were conditions, so I didn't want to use the term. 21:39:55 Alastair: "Conformance Applicability" 21:40:32 Jutta: "Conformance Applicability Notes" 21:40:43 Resolution: All accept "Conformance Applicability Notes" 21:41:01 Topic: Proposal re: B.1.1.3 21:41:13 http://www.w3.org/2002/09/wbs/35520/20110204/results#xq1 21:42:06 Resolution: All accept Folding " B.1.1.3 Template Auto-Selection (WCAG)" into a note in "B.1.1.2 Content Auto-Generation During Authoring Sessions (WCAG)": " Note 1: Automatic generation includes automatically selecting templates for authors." 21:42:13 Proposal to strengthen B.2.1.1 (was B.1.1.1) 21:42:18 Topic: Proposal to strengthen B.2.1.1 (was B.1.1.1) 21:42:24 http://www.w3.org/2002/09/wbs/35520/20110204/results#xq3 21:45:05 Greg: It is about the ability to do it, rather than the certainty that it should be done. 21:45:45 Jutta: The authoring tool is only capable of editing what the authoring tool can edit. 21:48:27 Alastair: one authoring tool can have a very simple interface, but follows ATAG, while another simply provides an HTML view. Both would be seen as equal under ATAG and that doesn't seem right. But I recognize that this would be difficult to quantify. 21:48:40 Postponed for more discussion. 21:48:42 Action JR: To organize chat with Greg, Alastair, Alex about this B.2.1.1 21:48:42 Created ACTION-320 - Organize chat with Greg, Alastair, Alex about this B.2.1.1 [on Jan Richards - due 2011-02-14]. 21:48:59 http://www.w3.org/2002/09/wbs/35520/20110204/results#xq4 21:49:10 Topic: B.2.4.4 Save for Reuse: 21:51:25 Greg withdraws objection. 21:51:46 Resolution: All accept: B.2.4.4 Save for Reuse: When authors enter programmatically associated text alternatives for non-text content, both of the following are true: (Level AAA) (a) the text alternatives are automatically saved and suggested by the authoring tool, if the same non-text content is reused; and (b) the author has the option to edit or delete the saved text alternatives. 21:53:54 topic: Next publishing 21:54:01 Jeanne: What's left? 21:56:16 Definition of authoring tool, bundling of changes, maybe a couple more substantive changes. 21:56:39 jeanne: We also need to make sure our comment responses are ok. 21:59:32 Jan: People need to read the responses and make any notes about the comments - wording, tone, etc. 21:59:51 Jeanne: I think the week after CSUN is a more realistic date for publishing. 22:00:49 Jan: We don't want to go to Last Call again without people who made comments having agreed to the changes. 22:01:05 -Alex 22:01:08 -Sueann 22:01:10 -Alastair 22:01:15 -Tim_Boland 22:01:21 -Greg 22:01:23 -??P0 22:01:29 -AleMiele 22:02:19 zakim, bye 22:02:19 leaving. As of this point the attendees were Jeanne, +1.571.765.aaaa, Alastair, Jan, Alex, AleMiele, Greg, +1.561.582.aabb, Sueann, Jutta, Tim_Boland 22:02:19 Zakim has left #au 22:02:30 rrsagent, make logs public 22:02:40 rrsagent, make minutes 22:02:40 I have made the request to generate http://www.w3.org/2011/02/07-au-minutes.html jeanne 22:02:46 RRSAgent, make minutes 22:02:46 I have made the request to generate http://www.w3.org/2011/02/07-au-minutes.html Jan 22:02:57 RRSAgent, set logs public 22:03:23 ARonksley has left #au 22:08:27 action: Jeanne to review Andrew Kirkpatrick comments for AUWG. 22:08:28 Created ACTION-321 - Review Andrew Kirkpatrick comments for AUWG. [on Jeanne Spellman - due 2011-02-14]. 22:49:59 jeanne has left #au