17:57:53 RRSAgent has joined #ua 17:57:53 logging to http://www.w3.org/2012/02/23-ua-irc 17:57:55 RRSAgent, make logs public 17:57:55 Zakim has joined #ua 17:57:57 Zakim, this will be WAI_UAWG 17:57:57 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 3 minutes 17:57:58 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 17:57:58 Date: 23 February 2012 17:58:06 kford has joined #ua 17:58:08 rrsagent, set logs public 17:58:28 chair: jimallan, kellyford 18:00:37 WAI_UAWG()1:00PM has now started 18:00:44 +Greg_Lowney 18:01:03 regrets: jan 18:01:13 +Jim_Allan 18:01:41 Agenda+ Discussion on guideline levels - Please, Please -- Fill Out 18:01:43 SPREADSHEET, so we can make decisions on Thursday. there are 115 SC 18:01:44 to add your thoughts (numbers) to. Also, add implementations if you 18:01:46 have them. https://docs.google.com/a/tsbvi.edu/spreadsheet/ccc?key=0AiiGLIaAlHSKdHNrcGNacUp2MHdXQW9sUmpBQ21Lenc&hl=en_US&pli=1#gid=0 18:01:47 Agenda+ Review other proposals sent to list 18:01:49 Agenda+ actions/issues 18:02:47 KimPatch has joined #ua 18:03:07 +[Microsoft] 18:03:15 zakim, microsoft is kford 18:03:15 +kford; got it 18:03:20 zakim, agenda? 18:03:20 I see 3 items remaining on the agenda: 18:03:21 1. Discussion on guideline levels - Please, Please -- Fill Out [from JAllan] 18:03:21 2. Review other proposals sent to list [from JAllan] 18:03:21 3. actions/issues [from JAllan] 18:03:29 jeanne has joined #ua 18:04:20 +Kim_Patch 18:05:10 sharper has joined #ua 18:05:11 +Jeanne 18:07:32 zakim, code? 18:07:32 the conference code is 82941 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), sharper 18:07:42 +??P5 18:07:47 zakim, ??P5 is sharper 18:07:47 +sharper; got it 18:07:54 present+ Harper_Simon 18:15:31 discussion on the A11y Professional Association 18:17:43 zakim, take up item 1 18:17:43 agendum 1. "Discussion on guideline levels - Please, Please -- Fill Out" taken up [from JAllan] 18:17:58 scribe: JimAllan 18:18:21 zakim, open item 1 18:18:21 agendum 1. "Discussion on guideline levels - Please, Please -- Fill Out" taken up [from JAllan] 18:18:22 agenda ? 18:19:24 kf: question: will we be able to do the spreadsheet? or should we try something else? 18:19:37 ...why is this taking so long. 18:20:12 gl: 115 rows,by 13 columns and comments....its a lot. SS is difficult 18:20:32 ...doesn't work well for me, just navigating. 18:21:36 kf: what can we do and call it success. 18:22:06 js: go down the implementation column and see what we know about browsers 18:23:10 https://docs.google.com/a/tsbvi.edu/spreadsheet/ccc?key=0AiiGLIaAlHSKdHNrcGNacUp2MHdXQW9sUmpBQ21Lenc&hl=en_US&pli=1#gid=0 18:23:41 gl: implementation was also hard. created test files. 18:23:53 topic: UA SC implementations 18:24:03 I'd find the columns more intuitive if they were specific disabilities rather than the current terms, which I find vague. 18:25:31 js: when Kim and I talked the implementation was to be off the top of head. not so detailed 18:26:01 kp: getting the numbers down and if there is a cluster of @@ then we can talk about those. 18:26:59 ... column heads were to be functional rather than disability specific. 18:28:46 kf: start with Principle 2 18:29:42 topic: 211 keyboard operation 18:30:02 js: basically everyone does this. 18:30:44 gl: there are bugs. what about mobile browsers (those designed specifically for touch screen) 18:31:17 kp: ipad configuring swipes and multiple touches. 18:31:45 js: need to get a rough count. easy to do or rough count. not discuss and get detailed. 18:31:54 kp: generally implemented 18:33:04 kf: are there any features that are not keyboard accesible 18:33:28 every browser has some features that are not keyboard accessible. 18:34:06 js: is this something that is easy and should be an A or very hard and be a AAA 18:35:01 topic: 212 keyboard focus 18:35:29 generally true 18:39:39 topic: 213 viewport navigation 18:40:11 generally true 18:40:38 topic: 214 specify preferred keystrokes 18:42:34 keyconfig addon for FF change binding 18:42:45 perhaps greasemonky 18:44:46 sh: why looking only at browsers. if a given function can be demonstrated in some other application, then it is possible and should be counted in implementaions. 18:45:43 kf: MS word is a browser, and can do lots of things we are looking for. 18:46:22 topic: no keyboard trap 18:47:53 generally supported, FF has issues 18:48:10 topic: 216 separate selection from activation 18:48:48 FF does well (at one time) , IE does not, Jaws does 18:49:27 topic: 217 follow text keyboard conventions 18:49:33 5 18:50:22 topic: 218 efficient keyboard access 18:53:41 generally true, check by looking at the UI to see if underscore and shortcut keys 18:55:02 could be rewritten to be 'indicate keyboard shortcuts' 18:55:13 kf: leave it. 18:55:28 topic: 219 override bindings 18:58:02 gl: this is similar to 214. confusing. 18:58:27 ... perhaps change to "author supplied user interface controls" to clarify. 18:59:22 214 is author supplied, 219 is UI controls 19:00:26 Action: JAllan to compare keyboard section with jb keyboard section from 2 years ago 19:00:27 Created ACTION-714 - Compare keyboard section with jb keyboard section from 2 years ago [on Jim Allan - due 2012-03-01]. 19:01:54 js: does the IER match? 19:02:11 rrsagent, make minutes 19:02:11 I have made the request to generate http://www.w3.org/2012/02/23-ua-minutes.html JAllan 19:05:12 We need to move the Elaine example from 2.1.4 to 2.1.9. Kim will write a sentence for 2.1.4 Intent and/or example of author supplied UI. 19:05:56 action: jeanne to move the Elaine example from 2.1.4 to 2.1.9. 19:05:56 Created ACTION-715 - Move the Elaine example from 2.1.4 to 2.1.9. [on Jeanne F Spellman - due 2012-03-01]. 19:06:02 action: Kim will write a sentence for 2.1.4 Intent and/or example of author supplied UI. 19:06:02 Created ACTION-716 - Will write a sentence for 2.1.4 Intent and/or example of author supplied UI. [on Kimberly Patch - due 2012-03-01]. 19:07:23 kford has joined #ua 19:07:38 topic: 221 provide sequential navigation 19:07:44 -Jeanne 19:09:01 generally done by everyone. exception for mobile. FF does not do object/embed navigation 19:09:50 topic: 222 nave between viewports 19:10:10 s/nave/nav 19:11:50 generally everyone, except mobile devices 19:14:02 topic: 223 defaul nav 19:14:20 generally all 19:14:41 topic: 224 wrap navigation 19:17:06 no one knows of a UA that does this 19:17:35 mhakkien has joined #ua 19:18:03 better late than never (i hope) 19:18:14 topic: 231 direct nav to impt elements 19:19:01 + +1.609.734.aaaa 19:19:23 https://docs.google.com/spreadsheet/ccc?key=0AiiGLIaAlHSKdHNrcGNacUp2MHdXQW9sUmpBQ21Lenc#gid=0 19:19:24 Cell R81 19:20:36 JAllan has joined #ua 19:21:32 rrsagent, make minutes 19:21:32 I have made the request to generate http://www.w3.org/2012/02/23-ua-minutes.html Greg 19:27:31 JAllan has joined #ua 19:28:07 Chrome with ChromeVox add-on provides sequential navigation to selected types of structural or operable elements (e.g. next/previous h2). 19:28:26 Which SC does that fall into? Is that structural navigation or sequential navigation with filtering? 19:28:49 (Thanks to Mark for info on ChromeVox.) 19:28:57 discussion about direct navigation and sequential navigation of important elements. 19:29:13 rrsagent, make minutes 19:29:13 I have made the request to generate http://www.w3.org/2012/02/23-ua-minutes.html JAllan 19:31:36 Definition of Important Elements: This specification intentionally does not identify which "important elements" must be navigable because this will vary by specification. What constitutes "efficient navigation" may depend on a number of factors as well, including the "shape" of content (e.g. sequential navigation of long lists is not efficient) and desired granularity (e.g. among tables,... 19:31:38 ...then among the cells of a given table). Refer to the Implementing document [Implementing UAAG 2.0] for information about identifying and navigating important elements. @@ Editors' Note: Update links 19:31:46 mh: what is an element? html element, and combination of HTML div span, etc with a "role" (aria) 19:32:39 kp: structural and operable elements 19:34:43 Action: KFord Resolve direct and sequential navigation to important elements 2.3.1 and 2.2.1. 19:34:44 Created ACTION-717 - Resolve direct and sequential navigation to important elements 2.3.1 and 2.2.1. [on Kelly Ford - due 2012-03-01]. 19:42:59 - +1.609.734.aaaa 19:43:00 -Kim_Patch 19:43:10 -sharper 19:43:13 sharper has left #ua 19:43:27 -Greg_Lowney 19:43:29 rrsagent, make minutes 19:43:29 I have made the request to generate http://www.w3.org/2012/02/23-ua-minutes.html JAllan 19:43:39 zakim, who is here 19:43:40 JAllan, you need to end that query with '?' 19:43:43 zakim, who is here? 19:43:43 On the phone I see Jim_Allan, kford 19:43:45 On IRC I see JAllan, mhakkien, kford, jeanne, KimPatch, Zakim, RRSAgent, Greg, trackbot 19:45:18 rrsagent, please part 19:45:18 I see 4 open action items saved in http://www.w3.org/2012/02/23-ua-actions.rdf : 19:45:18 ACTION: JAllan to compare keyboard section with jb keyboard section from 2 years ago [1] 19:45:18 recorded in http://www.w3.org/2012/02/23-ua-irc#T19-00-26 19:45:18 ACTION: jeanne to move the Elaine example from 2.1.4 to 2.1.9. [2] 19:45:18 recorded in http://www.w3.org/2012/02/23-ua-irc#T19-05-56 19:45:18 ACTION: Kim will write a sentence for 2.1.4 Intent and/or example of author supplied UI. [3] 19:45:18 recorded in http://www.w3.org/2012/02/23-ua-irc#T19-06-02 19:45:18 ACTION: KFord Resolve direct and sequential navigation to important elements 2.3.1 and 2.2.1. [4] 19:45:18 recorded in http://www.w3.org/2012/02/23-ua-irc#T19-34-43