16:55:25 RRSAgent has joined #ua 16:55:25 logging to http://www.w3.org/2011/09/01-ua-irc 16:55:27 RRSAgent, make logs public 16:55:27 Zakim has joined #ua 16:55:29 Zakim, this will be WAI_UAWG 16:55:29 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 5 minutes 16:55:30 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 16:55:30 Date: 01 September 2011 16:56:53 zakim, aganda? 16:56:54 I don't understand your question, JAllan. 16:56:59 Agenda+ Register for TPAC http://www.w3.org/2011/11/TPAC/ 16:56:59 Agenda+ Resolve configure important items, UA determine relationships. 16:56:59 Agenda+ Review/Resolve outstanding issues 16:56:59 Agenda+ survey results http://www.w3.org/2002/09/wbs/36791/abc/ 16:56:59 Agenda+ review comments - 16:57:00 http://lists.w3.org/Archives/Public/w3c-wai-ua/2011JulSep/0010.html 16:57:22 Agenda+ Items needing summary 16:57:40 Agenda+ Action Item Review 16:57:42 regrets: Jan, Mark 17:01:14 WAI_UAWG()1:00PM has now started 17:01:21 + +1.617.324.aaaa 17:01:24 Greg has joined #ua 17:01:31 zakim, aaaa is me 17:01:32 +jeanne; got it 17:01:35 +Jim_Allan 17:03:11 + +1.425.895.aabb 17:03:18 zakim, aabb is me 17:03:20 +Greg; got it 17:06:30 Sorry I keep trying to connect with the phone but it doesn't seem to be working. 17:06:47 JAllan has joined #ua 17:07:19 +[Microsoft] 17:07:28 zakim, microsoft is kford 17:07:28 +kford; got it 17:07:59 zakim, agenda? 17:07:59 I see 7 items remaining on the agenda: 17:08:00 1. Register for TPAC http://www.w3.org/2011/11/TPAC/ [from jeanne] 17:08:03 2. Resolve configure important items, UA determine relationships. [from jeanne] 17:08:05 3. Review/Resolve outstanding issues [from jeanne] 17:08:07 4. survey results http://www.w3.org/2002/09/wbs/36791/abc/ [from jeanne] 17:08:09 5. review comments - [from jeanne] 17:08:10 6. Items needing summary [from jeanne] 17:08:12 7. Action Item Review [from jeanne] 17:08:27 zakim, open item 1 17:08:27 agendum 1. "Register for TPAC http://www.w3.org/2011/11/TPAC/" taken up [from jeanne] 17:09:18 TPAC will be an unconference format. See the list of ideas for sessions <- http://www.w3.org/wiki/TPAC2011/SessionIdeas 17:09:58 Dates for UAWG meeting is Nov 3 & 4 17:14:29 sharper has joined #ua 17:20:06 registration closes 14 october and registration fee goes up 17:20:44 zakim, agenda? 17:20:44 I see 7 items remaining on the agenda: 17:20:46 1. Register for TPAC http://www.w3.org/2011/11/TPAC/ [from jeanne] 17:20:48 2. Resolve configure important items, UA determine relationships. [from jeanne] 17:20:51 3. Review/Resolve outstanding issues [from jeanne] 17:20:52 4. survey results http://www.w3.org/2002/09/wbs/36791/abc/ [from jeanne] 17:20:54 5. review comments - [from jeanne] 17:20:56 6. Items needing summary [from jeanne] 17:20:57 7. Action Item Review [from jeanne] 17:20:59 zakim, take up item 1 17:20:59 agendum 1. "Register for TPAC http://www.w3.org/2011/11/TPAC/" taken up [from jeanne] 17:20:59 zakim, close item 1 17:21:01 agendum 1, Register for TPAC http://www.w3.org/2011/11/TPAC/, closed 17:21:02 I see 6 items remaining on the agenda; the next one is 17:21:04 2. Resolve configure important items, UA determine relationships. [from jeanne] 17:21:18 zakim, take up item 2 17:21:18 agendum 2. "Resolve configure important items, UA determine relationships." taken up [from jeanne] 17:21:48 JS: I don't think we have enough people for a viable consensus. Postpone until next week. 17:21:52 zakim, close this item 17:21:52 agendum 2 closed 17:21:54 I see 5 items remaining on the agenda; the next one is 17:21:56 3. Review/Resolve outstanding issues [from jeanne] 17:22:43 zakim, take up item 3 17:22:43 agendum 3. "Review/Resolve outstanding issues" taken up [from jeanne] 17:22:52 JA: Principle 1 is complete 17:23:00 ... Principle 5 is complete 17:23:12 ... need a summary for 4.2 17:23:49 ... 4.2.1 and 4.2.1 need intent. (already have examples) 17:24:06 s/ 4.2.1 and 4.2.1 / 4.2.1 and 4.2.2 17:25:16 [group breaks for writing] 17:26:49 sharper_ has joined #ua 17:28:44 +??P2 17:31:46 http://www.w3.org/WAI/UA/2011/ED-UAAG20-20110819 17:32:01 Possible Summary for 2.2: 17:32:07 That's 4.2. 17:32:09 Input focus correctly transitions between nested user agents (4.2.1), the user can determine input focus at any time (4.2.2) and input focus never gets stuck in any nested user agent (4.2.3). 17:32:30 zakim, P2 is really sharper 17:32:30 sorry, JAllan, I do not recognize a party named 'P2' 17:32:42 zakim, ??P2 is really sharper 17:32:42 +sharper; got it 17:33:39 KimPatch has joined #ua 17:35:11 + +1.617.325.aacc 17:42:35 zakim, aacc is Kim 17:42:35 +Kim; got it 17:46:35 Possible summaries for 4.2 and 2.7: 17:46:45 4.2 17:46:47 Input focus correctly transitions between nested user agents (4.2.1), the user can determine input focus at any time (4.2.2) and input focus never gets stuck in any nested user agent (4.2.3). 17:46:49 2.7 17:46:51 The user can customize user agent settings related to accessibility (2.7.1) with settings changes being saved between sessions (2.7.2) and restore settings to default values (2.7.3). Users can have multiple sets of preferences (2.7.4), have related settings restored to default as a group (2.7.5) and adjust preferences outside the user agent main user interface (2.7.6). Users can also... 17:46:53 ...transfer settings between devices (2.7.7) and are offered a wizard to assist in user customization (2.7.8). 17:48:21 possible summaries for 3.1-3.4 17:48:24 3.1 Users can turn off non-essential messaes from the author or user-agent. 17:48:35 3.2 Users can choose to confirm form submissions. 17:48:56 3.3 User documentation is available in an accessible format (3.3.1), it includes accessbilbity features (3.3.2), delineates differences between versions (3.3.3), provides a centralized views of the browser meets UAAG2.0 (3.3.4), and is available as context sensitive help in the UA (3.3.5). 17:49:08 3.4 Moving the focus allow presentation of information (e.g. tooltips) but does not cause any other action (3.4.2). Users can prevent non-requested focus changes (3.4.1). 17:50:50 Topic: proposed Summary for 2.1 17:50:54 Guideline 2.1 - Ensure full keyboard access. 17:50:54 Users have many ways to input information into a computer or device, including mouse, keyboard, gesture, and speech. The keyboard paradigm is the most universal interface for text input - even devices that do have a keyboard (like mobile phones) support a software interface for them. All functions can be operated only using a keyboard (2.1.1), the focus can be moved by the keyboard (2.1.2, 2.1.3), 17:50:54 important or commonly used features of the web page or application should have shortcut keys for direct navigation (2.1.8). and the user can override keyboard shortcuts and user interface controls (2.1.4). Users should have a mechanism to escape keyboard traps such as embedded objects that do not return focus to the main web page (2.1.5). Users can set a preference that selecting an item in a 17:50:56 dropdown list or menu, does not activate that item or move to that new web page (2.1.6). Text entry should use the standard keys for that platform (2.1.7). 17:51:27 Topic: Proposed Summary for 2.2 17:51:29 Guideline 2.2 - Provide sequential navigation 17:51:29 Users need to be able to move through all the enabled content in the web page in a logical sequential fashion (2.2.1 and 2.2.2). Unless the author specifies a different navigation order, the default is the document order (2.2.3). Users can prevent or request notification when wrapping to the start of the page, to prevent unwanted repetition (2.2.4). 17:56:54 2.1.2 Keyboard Focus (former 1.9.1): 17:56:55 Every viewport has an active or inactive keyboard focus at all times. (Level A) 17:56:57 2.1.3 Viewport Navigation (former 1.9.2 & 1.9.4): 17:56:58 The user can move the active keyboard focus to any viewport. (Level A) 17:57:10 2.2.1 Sequential Navigation Between Elements [replaces 1.9.8 Bi-Directional and 2.1.8 Keyboard Navigation] 17:57:12 The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the current viewport. (Level A) 17:57:13 2.2.2 Sequential Navigation Between Viewports [new]: 17:57:15 The user can move the keyboard focus backwards and forwards between viewports, without having to sequentially navigate all the elements in a viewport. (Level A) 17:58:24 Action: revisit Nested User Agents 2.1.2, 2.1.3, .2.2.1, 2.2.2, -- these should be cross referenced with gl 4.2 <-- should also be reviewed. 17:58:24 Sorry, couldn't find user - revisit 17:58:40 Action: jallan to revisit Nested User Agents 2.1.2, 2.1.3, .2.2.1, 2.2.2, -- these should be cross referenced with gl 4.2 <-- should also be reviewed. 17:58:41 Created ACTION-610 - Revisit Nested User Agents 2.1.2, 2.1.3, .2.2.1, 2.2.2, -- these should be cross referenced with gl 4.2 <-- should also be reviewed. [on Jim Allan - due 2011-09-08]. 18:00:01 Users can discover the keys which facilitate direct navigation and activation (2.5.1), view their location in the structural hierarchy (2.5.3), along with the relationships within that hierarchy (2.5.5), and specify the elements (2.5.7+1.10.3) important to building and navigate different hierarchical views (1.10.2). 18:00:38 topic: summary 4.2 Input focus correctly transitions between nested user agents (4.2.1), the user can determine input focus at any time (4.2.2) and input focus never gets stuck in any nested user agent (4.2.3). 18:02:43 summary 4.2 Input focus correctly transitions between nested user agents (4.2.1), the user can retrieve input focus at any time (4.2.2) and input focus never gets stuck in any nested user agent (4.2.3). 18:03:37 topic: 2.7.5 summary 18:03:48 The user can customize user agent settings related to accessibility (2.7.1) with settings changes being saved between sessions (2.7.2) and restore settings to default values (2.7.3). Users can have multiple sets of preferences (2.7.4), have related settings restored to default as a group (2.7.5) and adjust preferences outside the user agent main user interface (2.7.6). Users can also... 18:03:50 ...transfer settings between devices (2.7.7) and are offered a wizard to assist in user customization (2.7.8). 18:05:42 Users can customize user agent settings related to accessibility (2.7.1) with settings being saved between sessions (2.7.2) and restore settings to default values (2.7.3). Users can have multiple sets of preferences (2.7.4), have related settings restored to default as a group (2.7.5) and adjust preferences outside the user agent main user interface (2.7.6). Users can also transfer settings... 18:05:44 ...between devices (2.7.7) and are offered a wizard to assist in user customization (2.7.8). 18:06:18 topic: summary for GL 3.1 -3.4 18:06:36 3.1 Users can turn off non-essential messaes from the author or user-agent. 18:06:37 3.2 Users can choose to confirm form submissions. 18:06:39 3.3 User documentation is available in an accessible format (3.3.1), it includes accessbilbity features (3.3.2), delineates differences between versions (3.3.3), provides a centralized views of the browser meets UAAG2.0 (3.3.4), and is available as context sensitive help in the UA (3.3.5). 18:06:41 3.4 Moving the focus allow presentation of information (e.g. tooltips) but does not cause any other action (3.4.2). Users can prevent non-requested focus changes (3.4.1). 18:09:35 gl: what about an SC requiring spell checking for folks with reading or writing disabilities. 18:10:29 all agree. 18:10:59 Action: Greg to write new SC 3.2.x about spell checking 18:10:59 Created ACTION-611 - Write new SC 3.2.x about spell checking [on Greg Lowney - due 2011-09-08]. 18:13:23 3.3 User documentation is available in an accessible format (3.3.1), it includes accessibility features (3.3.2), delineates differences between versions (3.3.3), provides a centralized views of conformance UAAG2.0 (3.3.4), and is available as context sensitive help in the UA (3.3.5). 18:15:01 Topic: proposed Summary for 2.1 18:15:20 Users have many ways to input information into a computer or device, including mouse, keyboard, gesture, and speech. The keyboard paradigm is the most universal interface for text input - even devices that do have a keyboard (like mobile phones) support a software interface for them. All functions can be operated only using a keyboard (2.1.1), the focus can be moved by the keyboard (2.1.2, 2.1.3), 18:15:22 important or commonly used features of the web page or application should have shortcut keys for direct navigation (2.1.8). and the user can override keyboard shortcuts and user interface controls (2.1.4). Users should have a mechanism to escape keyboard traps such as embedded objects that do not return focus to the main web page (2.1.5). Users can set a preference that selecting an item in a 18:15:23 dropdown list or menu, does not activate that item or move to that new web page (2.1.6). Text entry should use the standard keys for that platform (2.1.7). 18:15:25 Topic: Proposed Summary for 2.2 18:15:26 Guideline 2.2 - Provide sequential navigation 18:15:28 Users need to be able to move through all the enabled content in the web page in a logical sequential fashion (2.2.1 and 2.2.2). Unless the author specifies a different navigation order, the default is the document order (2.2.3). Users can prevent or request notification when wrapping to the start of the page, to prevent unwanted repetition (2.2.4). 18:17:19 scribe: jallan 18:18:27 kf: first couple of sentences read more like an intent. 18:19:15 JS: move first 2 sentences to intent of 2.1.1 18:21:30 "important or commonly used features should have shortcut keys for direct navigation (2.1.8)" 18:21:35 Users can operate all functions (2.1.1), and can move focus (2.1.2, 2.1.3) using just the keyboard. 18:23:22 gl: but need to distinguish between 212 and 213 18:28:15 Users can override author keyboard shortcuts and user interface controls (2.1.4) 18:29:53 can override keyboard shortcuts and user interface keyboard controls (2.1.4) 18:31:51 Users can escape keyboard traps such as embedded objects that do not return focus to the main web page (2.1.5). 18:32:39 "Users can override keyboard shortcuts in content and the user agent's user interface (2.1.4)" 18:32:53 Users can operate all functions (2.1.1), and move focus (2.1.2, 2.1.3) using just the keyboard. Users can activate important or common features with shortcut keys, (2.1.8), override keyboard shortcuts and user interface controls (2.1.4), escape keyboard traps (2.1.5), specify that selecting an item in a dropdown list or menuoes not activate that item or move to that new web page (2.1.6),... 18:32:55 ...and use standard keys for that platform (2.1.7). 18:35:07 Users can discover the keys which facilitate direct navigation and activation (2.5.1), view their current location in the structural hierarchy (2.5.3) as well as the relationships within that hierarchy (2.5.5), and specify the elements (2.5.7+1.10.3) important to building and navigating different hierarchical views (1.10.2). 18:35:28 Topic: Simon's proposal for 2.5 18:36:21 Users can operate all functions (2.1.1), and move focus (2.1.2, 2.1.3) using just the keyboard. Users can activate important or common features with shortcut keys, (2.1.8), override content and interface keyboard shortcuts (2.1.4), escape keyboard traps (2.1.5), specify that selecting an item in a dropdown list or menuoes not activate that item or move to that new web page (2.1.6) and use... 18:36:22 ...standard keys for that platform (2.1.7). 18:38:19 need lots of discussion about 1.10.2 1.10.3 and 2.5.7 and 2.5.4 18:38:50 Users can operate all functions (2.1.1) and move focus (2.1.2, 2.1.3) using just the keyboard. Users can activate important or common features with shortcut keys (2.1.8), override content and interface keyboard shortcuts (2.1.4), escape keyboard traps (2.1.5), specify that selecting an item in a dropdown list or menu doesn't activate or move item to that new web page (2.1.6). User can use... 18:38:52 ...standard keys for text entry (2.1.7). 18:39:07 "override keyboard shortcuts in content and user interface (2.1.4)" 18:40:21 (Don't want it to read like "override content and override interface keyboard shortcuts.) 18:42:00 -jeanne 18:42:02 -Kim 18:42:05 -sharper 18:42:10 -Jim_Allan 18:42:17 rrsagent, make minutes 18:42:17 I have made the request to generate http://www.w3.org/2011/09/01-ua-minutes.html JAllan 18:42:45 Present: JimA, KellyF, GregL, KimP, SimonH 18:43:12 rrsagent, make minutes 18:43:12 I have made the request to generate http://www.w3.org/2011/09/01-ua-minutes.html JAllan 18:44:00 -Greg 18:44:09 Chair: JimAllan, KellyFord 18:44:13 rrsagent, make minutes 18:44:13 I have made the request to generate http://www.w3.org/2011/09/01-ua-minutes.html JAllan 18:44:30 zakim, please part 18:44:30 leaving. As of this point the attendees were +1.617.324.aaaa, jeanne, Jim_Allan, +1.425.895.aabb, Greg, kford, sharper, +1.617.325.aacc, Kim 18:44:30 Zakim has left #ua 18:44:45 rrsagent, please part 18:44:45 I see 3 open action items saved in http://www.w3.org/2011/09/01-ua-actions.rdf : 18:44:45 ACTION: revisit Nested User Agents 2.1.2, 2.1.3, .2.2.1, 2.2.2, -- these should be cross referenced with gl 4.2 <-- should also be reviewed. [1] 18:44:45 recorded in http://www.w3.org/2011/09/01-ua-irc#T17-58-24 18:44:45 ACTION: jallan to revisit Nested User Agents 2.1.2, 2.1.3, .2.2.1, 2.2.2, -- these should be cross referenced with gl 4.2 <-- should also be reviewed. [2] 18:44:45 recorded in http://www.w3.org/2011/09/01-ua-irc#T17-58-40 18:44:45 ACTION: Greg to write new SC 3.2.x about spell checking [3] 18:44:45 recorded in http://www.w3.org/2011/09/01-ua-irc#T18-10-59