19:53:27 RRSAgent has joined #au 19:53:27 logging to http://www.w3.org/2010/06/14-au-irc 19:53:33 Zakim, this will be AUWG 19:53:33 ok, Jan; I see WAI_AUWG()3:00PM scheduled to start 53 minutes ago 19:53:38 Meeting: WAI AU 19:53:59 Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2010AprJun/0069.html 19:54:18 Chair: Jutta Treviranus 19:55:06 Regrets: Andrew R., Tim B., Alastair C. 19:58:10 Regrets: Andrew R., Tim B., Alastair C., Sueann N. 20:00:34 jeanne has joined #au 20:00:48 zakim, code? 20:00:48 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:00 WAI_AUWG()3:00PM has now started 20:01:07 +[IPcaller] 20:01:21 +Jeanne 20:01:25 zakim, [IPcaller] is really Jan 20:01:25 +Jan; got it 20:02:38 +??P2 20:02:55 zakim, ??P2 is really Jutta 20:02:55 +Jutta; got it 20:05:41 AnnM has joined #au 20:06:05 hey 20:07:00 did i screw up the times and miss the meeting? 20:07:54 i can't seem to get on 20:08:01 it's not parsing the conference code 20:08:08 i've tried skype as well as my iphone 20:08:16 and it just keeps asking me to enter the code before hanging up on me 20:08:23 that's what i've been putting in 20:08:58 there were problems with Zakim UK and FR numbers to day. 20:09:07 let me see if they are fixed yet... 20:09:10 oh, ok 20:09:20 ok, back on skype now 20:10:14 present+ Ann 20:12:19 + +3aaaa 20:12:34 zakim, aaaa is really GregP 20:12:34 +GregP; got it 20:14:10 gpisocky has joined #au 20:14:23 Topic: 1. Discussion of issues that might be addressed before Las Call publication. 20:14:40 http://lists.w3.org/Archives/Public/w3c-wai-au/2010AprJun/0068.html 20:14:56 JT: Skip editorial andgo to "Minor" 20:15:32 Topic: (2) Adding "Any": "A.3.1.6 Present Keyboard Commands: Authoring tool user interface controls can be presented with any associated keyboard commands. (Level AAA)" 20:15:48 Resolution: Approve change to "(2) Adding "Any": "A.3.1.6 Present Keyboard Commands: Authoring tool user interface controls can be presented with any associated keyboard commands. (Level AAA)"" 20:16:18 +1 20:16:25 Topic: (1) Adding "Any": A.3.6.1 Save Settings: Any authoring tool display settings and control settings are saved between authoring sessions. 20:16:47 Resolution: Approve change to "(1) Adding "Any": A.3.6.1 Save Settings: Any authoring tool display settings and control settings are saved between authoring sessions." 20:17:16 Topic: PROPOSAL: Split "content (web content)" and "Web content properties". Without any other substantive change. Both are already defined terms. 20:17:37 +1 20:18:01 Resolution: Approve PROPOSAL: Split "content (web content)" and "Web content properties". Without any other substantive change. Both are already defined terms. 20:18:25 Topic: Removing "A.3.1.3 Keyboard shortcuts are provided." 20:18:40 JS: Has a concern... 20:18:49 JS: I don't think it is sufficiently covered. 20:19:11 JS: Providing shortcuts for appliucations is not typically part of conventions 20:19:31 JS: I've read Microsoft's - they don't require them 20:20:09 AM: Not sure that all keyboard shortcuts would be included 20:21:01 JR: AC says he would like to keep something about mechanisms to get to edit areas and menus 20:21:29 JT: Maybe we can put some wording around it re: authoring functions. 20:23:40 JR: Maybe its a level AA to make keyboard navigation more efficent and edffective but need be careful to make wording objective 20:23:54 JT: Efficiency and effectiveness should be measurable 20:24:04 GP: Efficiency not always 20:24:12 JT: But can measure by actions 20:24:57 GP: Can't always - often tab order is up to do developer judgement 20:26:06 JR: Maybe use structure of UI? 20:26:27 JT: Irrespective of structure...key point is what functions are needed for editing 20:28:49 JR: Authoring might not be even the primary purpose 20:29:11 GP: Maybe regardles of what I want to do is there an effective way of doing it 20:30:39 JR: What about any ability to navigate functions by keyboard access that is not simply linear 20:30:58 GP: There isn't one testable criteria 20:31:14 JT: Yes when create acces systems for keyboard users we do this 20:31:30 JT: The question is how do we apply this during dev of tool. 20:31:48 JT: One way is to allow user to analyze their own use 20:32:03 JT: But that's not practical for every developer 20:32:43 JR: That's what I was trying to do. 20:33:01 JT: But that makes it too complex and hard to explain. 20:33:38 JR: It's "Bybpass Blocks" from WCAG 20:35:00 JR: Because accesskey is broken on the web. 20:35:28 JT: OK but in content many more links than iun authoring 20:35:38 JR: Not sure about that DW has many functions 20:35:51 JT: Right but commonly used is much smaller set 20:36:20 JR: But unfortunately on a web abased tool you couldn't do this 20:37:46 JR: What about rewording bypass slightly 20:38:43 JS: What's wrong with what we have? 20:38:52 JR: I agree. 20:39:47 JT: I'm worried about adding a new UI convention 20:40:24 JR: But its not - it;s like toolbar bypass in TinyMCE 20:40:36 -Jutta 20:40:57 +??P2 20:42:52 Resolution: Keep A3.1.3 as it is and instead add some support text to the Implementing document that addresses show bypass link blocks might be used to do this in web-based tools 20:43:13 zakim, ??P2 is really Jutta 20:43:13 +Jutta; got it 20:43:48 Topic: (2) Rewording: B.2.2.1 Check Accessibility (WCAG Level A): If the authoring tool provides authors with the ability to add or modify web content so that any WCAG 2.0 Level A Success Criteria are violated, then accessibility checking for those success criteria is provided. (Level A) 20:46:59 -Jutta 20:47:22 +[IPcaller] 20:48:16 B.2.2.1 Check Accessibility (WCAG Level A): If the 20:48:18 authoring tool provides authors with the ability to add or modify web 20:48:20 content so that any WCAG 2.0 Level A Success Criteria are violated, then 20:48:21 accessibility checking for those success criteria is provided. (Level A) 20:48:29 JT: Likes new wording...easier to understand conditions 20:48:32 GP: Yes 20:48:52 +1 20:49:01 Resolution: B.2.2.1 Check Accessibility (WCAG Level A): If the authoring tool provides authors with the ability to add or modify web content so that any WCAG 2.0 Level A Success Criteria are violated, then accessibility checking for those success criteria is provided. (Level A) 20:50:19 Resolution: B.2.2.1 Check Accessibility (WCAG Level A): If the authoring tool provides authors with the ability to add or modify web content so that any WCAG 2.0 Level A Success Criteria can be violated, then accessibility checking for those success criteria is provided. (Level A) 20:50:46 -[IPcaller] 20:51:01 +1 20:51:06 Topic: 2. If any changes have been made - Last Call vote. 20:51:07 +??P2 20:51:10 Topic: 2. If any changes have been made - Last Call vote. 20:51:14 +1 20:52:31 JT: Let's get everyone's vote here...then others later. 20:52:34 JR: Agrees. 20:52:42 I agree to last call 20:52:50 JS: Yes 20:52:58 AM: I agree to Last Call 20:53:11 JT: Yes 20:53:50 -??P2 20:53:51 -GregP 20:53:52 -Jan 20:55:02 -Jeanne 20:55:04 WAI_AUWG()3:00PM has ended 20:55:06 Attendees were Jeanne, Jan, Jutta, +3aaaa, GregP, [IPcaller] 20:55:17 RRSAgent, make minutes 20:55:17 I have made the request to generate http://www.w3.org/2010/06/14-au-minutes.html Jan 20:56:06 RRSAgent, set logs public 22:14:02 jeanne has left #au