17:20:31 <RRSAgent> RRSAgent has joined #ua
17:20:31 <RRSAgent> logging to http://www.w3.org/2006/09/07-ua-irc
17:20:41 <jallan> rrsagent, set logs public
17:21:36 <jallan> title: UAWG teleconference
17:21:44 <jallan> Chair: Jim Allan
17:21:55 <jallan> Regrets: Jan Richards
17:57:12 <Zakim> WAI_UAWG()2:00PM has now started
17:57:19 <Zakim> +Jim_Allan
17:59:13 <Zakim> +[IBM]
17:59:44 <jallan> zakim, [ibm] is pparente
17:59:44 <Zakim> +pparente; got it
17:59:57 <parente> parente has joined #ua
18:01:39 <Zakim> +DPoehlman
18:05:08 <Zakim> +[IBM]
18:05:28 <cklaws> cklaws has joined #ua
18:05:31 <jallan> zakim, [ibm] is cklaws
18:05:31 <Zakim> +cklaws; got it
18:07:10 <jallan> topic: 6.6 Programmatic notification of changes (P1) 
18:08:01 <jallan> AJAX issues, 
18:08:16 <jallan> cl: not all events are referenced in the dom
18:08:59 <jallan> pp: CSS allows creation of text, does w3 say anything about this and accessibility
18:10:44 <jallan> there is a disconnect between dom text and css text
18:10:54 <jallan> cl: different specifications
18:13:09 <jallan> AJAX - html + css+ javascript, accessibility tools can access dom for js events and html, but css changes are difficult.
18:13:32 <jallan> Topic: 6.7 Conventional keyboard APIs (P1) 
18:15:08 <jallan> need technique: for key-bindings from UA and from author
18:16:21 <jallan> cl: HPR added additional modifier for accesskey (alt-shift) to avoid UA conflicts
18:16:48 <jallan> pp: also problems with keybindings with assistive technology
18:17:20 <jallan> cl: dhtml makes use of accesskey to fire events.
18:18:05 <jallan> pp: in gmail - uses single key for navigation
18:18:27 <jallan> ja: same model for screen readers, single key navigation
18:18:59 <jallan> cl: author problem, how to not conflict with AT, when they are not AT experts
18:19:52 <jallan> dp: TAB used in edit fields. in Safari, if you hit TAB you exit a form control.
18:20:21 <Zakim> +Aaron_Leventhal
18:20:24 <jallan> pp: javascript based text editors can insert TAB character in the edit field
18:22:29 <jallan> cl: single key navigation may conflict with onkeypress or onkeydown javascript events
18:23:04 <jallan> al: screen reader arrow keys only work when you are in screenreader browse mode.
18:23:52 <jallan> al: screen reader captures many keys, they have a pass through function
18:24:34 <jallan> al: screen reader gets access first (hooking into os), it has choice to use it and pass it on, or just pass it on
18:24:51 <jallan> capture first, then bubbling
18:25:26 <jallan> capture - event starts at html then moves down tree 
18:25:49 <jallan> bubbling: focus first priority, then move to root
18:27:21 <jallan> some keystrokes (alt to focus menus) UI will grab before it goes to content, other keystrokes UI will allow to go to content
18:28:11 <jallan> no good documents of how is should and does work (capture and bubble)
18:29:27 <jallan> conflicts between keypress, keydown, keyup - depends on the key, the OS, and UA
18:29:55 <jallan> dependent on keyboard api
18:31:07 <jallan> example: key held down, key repeats. does this fire multiple key events
18:32:33 <jallan> ja: How does the OS accessibility keyboard functions work with AT, and UA
18:33:07 <jallan> al: unsure, documentation and implementation issues
18:34:17 <aaronlev> aaronlev has joined #ua
18:34:20 <aaronlev> http://www.mozilla.org/access/keyboard/tabindex
18:35:31 <jallan> al: plug-in keybindings, more conflicts with UA, AT
18:36:16 <jallan> if plug-in dows not need a key, it should pass it on to the UA, not swallow it.
18:36:33 <jallan> should have some pass through to the UA function
18:37:41 <jallan> cl: if stand-alone plug-in, standard practice - should not swallow keys that the application does not need
18:38:46 <jallan> pp: chaining, if something higher up the api chain gets a key lower level api may not see the event
18:39:47 <jallan> ja: this is related to 6.10
18:40:35 <jallan> ja: also UA extensions keybinding conflicts
18:41:29 <jallan> al: big conflicts. keybinding negotiation (extension, content access key, plugins)
18:41:51 <jallan> perhaps assign keys to roles,
18:42:31 <jallan> or similar to fonts have a list of proposed keys with fallback options
18:44:14 <jallan> topic  6.6 Programmatic notification of changes (P1) 
18:44:43 <jallan> cl: css adding content to visual rendering, but not to dom
18:45:52 <jallan> al: difficult to get css information, can tell that it is roman numberals, but not specific item, 
18:47:57 <jallan> is DOM 3 implemented fully?
18:48:35 <jallan> cl: mutation events in dom2
18:48:49 <jallan> ja: what is mutation event
18:49:41 <jallan> cl: attributen name, vlaue, node  changed
18:50:31 <jallan> dom 3 http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/
18:51:13 <jallan> dom 3 load save http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/
18:52:54 <jallan> cl: issues with mutation events, UA implementation of DOM 2 or 3
18:53:37 <jallan> some AT not listening to dom events and locations
18:56:08 <jallan> cl: not just limit notifications to AT through the DOM
18:56:32 <jallan> should include accessibility API
18:57:25 <jallan> Action: ja to create technique for AT notification of change through accessibility api.
18:57:51 <jallan> necessary for AT access to be complete. DOM does not provide enough information.
18:58:21 <jallan> al: no caret indicator in the DOM
18:58:42 <jallan> AT must rely on accessibility api for caret informaton/location
19:00:18 <Zakim> -cklaws
19:00:20 <Zakim> -Aaron_Leventhal
19:00:21 <Zakim> -DPoehlman
19:00:22 <Zakim> -pparente
19:00:23 <Zakim> -Jim_Allan
19:00:24 <Zakim> WAI_UAWG()2:00PM has ended
19:00:26 <Zakim> Attendees were Jim_Allan, pparente, DPoehlman, cklaws, Aaron_Leventhal
19:01:16 <jallan> rrsagent, make minutes
19:01:16 <RRSAgent> I have made the request to generate http://www.w3.org/2006/09/07-ua-minutes.html jallan
19:01:32 <jallan> rrsagent, set logs public
19:07:43 <jallan> jallan has left #ua
20:07:01 <Zakim> Zakim has left #ua