20:56:12 RRSAgent has joined #au 20:56:12 logging to http://www.w3.org/2010/12/06-au-irc 20:56:17 Zakim, this will be AUWG 20:56:17 ok, Jan, I see WAI_AUWG()3:00PM already started 20:56:21 Meeting: WAI AU 20:56:41 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2010OctDec/0091.html 20:56:49 Chair: Jutta Treviranus 20:56:55 Scribe: Jan 20:57:43 jeanne has joined #au 21:00:03 +Greg 21:00:19 zakim, code? 21:00:19 the conference code is 2894 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), Jan 21:00:41 +[IPcaller] 21:00:58 gpisocky has joined #au 21:02:10 +[Microsoft] 21:02:17 zakim, [IPcaller] is really Jan 21:02:17 +Jan; got it 21:02:47 zakim, [Microsoft] is really Cherie 21:02:47 +Cherie; got it 21:02:57 +[Microsoft] 21:03:25 zakim, [Microsoft] is really Alex 21:03:25 +Alex; got it 21:04:39 ARonksley has joined #au 21:05:53 +??P6 21:06:07 zakim, ??P6 is really Jutta 21:06:07 +Jutta; got it 21:06:24 zakim, who's here? 21:06:24 On the phone I see Jeanne, Greg, Jan, Cherie, Alex, Jutta 21:06:25 On IRC I see ARonksley, gpisocky, jeanne, RRSAgent, Zakim, Jan, trackbot 21:06:41 +??P7 21:06:47 http://lists.w3.org/Archives/Public/w3c-wai-au/2010OctDec/0091.html 21:06:55 zakim, ??P7 is really Andrew 21:06:55 +Andrew; got it 21:08:03 jeanne is available 21:08:29 JT: We will meet Dec 13, 20 Jan 3, 10 21:08:41 http://www.w3.org/WAI/AU/2010/ED-IMPLEMENTING-ATAG20-20101206/ 21:08:50 Topic: 2. Traversing draft with rewording proposals (search for "@@") 21:09:03 +Sueann 21:10:54 CherieE has joined #au 21:12:25 @@Note: Some of the other success criteria in Part A are based on WCAG 2.0. This helps ensure that non-web-based authoring tools meet the same requirements as web-based tools. If the requirement has been modified from the WCAG 2.0 wording in order to more appropriately apply to authoring tools, rather than web content in general, then this will be noted. 21:15:52 -Jutta 21:16:23 +??P3 21:17:40 Action: Jan to do a normative note for A.1.1.1 that explains what SC's a web based tool does not have to do 21:17:40 Created ACTION-312 - Do a normative note for A.1.1.1 that explains what SC's a web based tool does not have to do [on Jan Richards - due 2010-12-13]. 21:18:04 +Tim_Boland 21:21:19 @@The intent of this success criterion is to ensure that authoring tool user interfaces that are not web applications are accessible to authors with disabilities. In formulating a requirement that would best fulfill this intent, the Working Group decided upon a requirement to follow (and cite in conformance claims) existing accessibility guidelines because... 21:21:35 -Andrew 21:22:08 +??P7 21:22:16 The intent of this success criterion is to ensure that authoring tool user interfaces that are not web applications are accessible to authors with disabilities. Existing accessibility guidelines are referenced bacause: 21:26:19 Resoultion: The intent of this success criterion is to ensure that authoring tool user interfaces that are not web applications are accessible to authors with disabilities. Existing accessibility guidelines are referenced because: 21:27:26 Topic: Changes in A.1.2.2 Platform Accessibility Services 21:29:05 Resolution: The intent of this success criterion is to ensure that authoring tool user interfaces that are not web applications are accessible to authors with disabilities who use assistive technologies that communicate with software via platform accessibility services. The requirement is stated generally because the specifics of what constitutes a platform accessibility service differs on... 21:29:07 ...each platform. The note that conformance claims must cite the the platform accessibility service(s) implemented should encourage developers to refrain from implementing services that are not supported by assistive technologies. 21:30:51 Topic: A.2.1.1 Alternative Content: 21:33:23 Resolution: "Programmatically Associated" rather than "recognized" 21:37:03 Sueann has joined #au 21:47:20 Action: Jan to outline A.2.1.1 Alternative Content in an email 21:47:20 Created ACTION-313 - Outline A.2.1.1 Alternative Content in an email [on Jan Richards - due 2010-12-13]. 21:49:56 Topic: A.3.1.3 Efficient Keyboard Access 21:50:05 @@The intent of this success criterion is to introduce a Level AA requirement to strengthen the requirement of Success Criterion A.3.1.1. That success criterion would be met even by a keyboard access mechanism in which users had to sequentially navigate through every available user interface component in order to reach their intended destination. The current success criterion (A.3.1.3)... 21:50:07 ...introduces the additional requirement that keyboard access must include mechanisms to make it more efficient that this type of purely sequential keyboard navigation. 21:50:08 The wording is intentionally general because the appropriate mechanisms available for increasing the efficiency of keyboard access vary according to the operating environment and the design of the authoring tool: 21:50:10 In desktop environments with a full keyboard, there is generally some set of keys available for developers to use as shortcut keys that directly link to particular functionality (e.g. the "ctrl" + "S" key combination can be directly mapped to the "Save" function). 21:50:11 In web-based environments very few direct shortcut keys are available, once the potential keys used by the various operating systems, user agents and assistive technologies are taken into account. In this case, bypass links are useful mechanisms for making keyboard access more efficient. 21:50:15 In mobile environments, the situation is variable. Some mobile environments include full, physical keyboards and support keyboard shortcuts. Other mobile environments do not enable keyboard shortcuts, but often increase keyboard navigation efficiency via recommending the use of tabs and other organizational mechanisms. 21:53:00 Resolution: @@The intent of this success criterion is to introduce a Level AA requirement to strengthen the requirement of Success Criterion A.3.1.1. That success criterion would be met even by a keyboard access mechanism in which users had to sequentially navigate through every available user interface component in order to reach their intended destination. This success criterion (A.3.1.3)... 21:53:02 ...introduces the additional requirement that keyboard access must include mechanisms to make it more efficient that this type of purely sequential keyboard navigation. The wording is intentionally general because the appropriate mechanisms available for increasing the efficiency of keyboard access vary according to the operating environment and the design of the authoring tool:In desktop... 21:53:04 ...environments with a full keyboard, there is generally some set of keys available for developers to use as shortcut keys that directly link to particular functionality (e.g. the "ctrl" + "S" key combination can be directly mapped to the "Save" function). In web-based environments very few direct shortcut keys are available, once the potential keys used by the various operating systems,... 21:53:07 ...user agents and assistive technologies are taken into account. In this case, bypass links are useful mechanisms for making keyboard access more efficient.In mobile environments, the situation is variable. Some mobile environments include full, physical keyboards and support keyboard shortcuts. Other mobile environments do not enable keyboard shortcuts, but often increase keyboard... 21:53:11 ...navigation efficiency via recommending the use of tabs and other organizational mechanisms. 21:53:17 Topic: A.3.6.1 Independence of Display 21:54:50 When "WYSIWYG authoring tools" are referred to in the examples, it is with the understanding that browsers will differ in their renderings of the same content and that end users are often free to override the default presentation of web content. 21:55:10 When "WYSIWYG authoring tools" are referred to in the examples, it is with the understanding that browsers will differ in rendering of the same content and that end users are often free to override the default presentation of web content. 21:55:29 Resolution: When "WYSIWYG authoring tools" are referred to in the examples, it is with the understanding that browsers will differ in rendering of the same content and that end users are often free to override the default presentation of web content. 21:56:00 Topic: A.3.6.5 Preferences Assistance 21:56:53 Resolution: "authoring tool display settings and control settings" 21:57:39 Topic: A.4.1.4 Content Changes Reversible (Enhanced) 21:58:08 @@The intent of this success criterion is to establish an enhanced Leve AAA requirement for reversing inadvertent actions. Everyone makes mistakes, but some people with some disabilities have more difficulty creating error-free input. In addition, it may be harder for some people with disabilities to detect that they have made an error, so it is more likely that they will need to reverse a... 21:58:10 ...series of actions once the error is discovered. 21:59:30 Action: Jan to clarify that series means more than one and in the same session 21:59:30 Created ACTION-314 - Clarify that series means more than one and in the same session [on Jan Richards - due 2010-12-13]. 22:00:00 Also note can't be done in multi-author enviornment 22:00:44 -Tim_Boland 22:01:10 -Alex 22:01:15 -Cherie 22:01:17 -Sueann 22:01:18 -Greg 22:01:18 -??P3 22:01:27 -??P7 22:02:04 ARonksley has left #au 22:02:32 -Jeanne 22:02:33 -Jan 22:02:35 WAI_AUWG()3:00PM has ended 22:02:36 Attendees were Jeanne, Greg, Jan, Cherie, Alex, Jutta, Andrew, Sueann, Tim_Boland 22:02:45 RRSAgent, make minutes 22:02:45 I have made the request to generate http://www.w3.org/2010/12/06-au-minutes.html Jan 22:02:53 RRSAgent, set logs public 22:03:00 Zakim, bye 22:03:00 Zakim has left #au 22:03:06 RRSAgent, bye 22:03:06 I see 3 open action items saved in http://www.w3.org/2010/12/06-au-actions.rdf : 22:03:06 ACTION: Jan to do a normative note for A.1.1.1 that explains what SC's a web based tool does not have to do [1] 22:03:06 recorded in http://www.w3.org/2010/12/06-au-irc#T21-17-40 22:03:06 ACTION: Jan to outline A.2.1.1 Alternative Content in an email [2] 22:03:06 recorded in http://www.w3.org/2010/12/06-au-irc#T21-47-20 22:03:06 ACTION: Jan to clarify that series means more than one and in the same session [3] 22:03:06 recorded in http://www.w3.org/2010/12/06-au-irc#T21-59-30