See also: IRC log
title: UAWG teleconference
AJAX issues,
cl: not all events are referenced in the dom
pp: CSS allows creation of text, does w3 say anything about this and accessibility
there is a disconnect between dom text and css text
cl: different specifications
AJAX - html + css+ javascript, accessibility tools can access dom for js events and html, but css changes are difficult.
need technique: for key-bindings from UA and from author
cl: HPR added additional modifier for accesskey (alt-shift) to avoid UA conflicts
pp: also problems with keybindings with assistive technology
cl: dhtml makes use of accesskey to fire events.
pp: in gmail - uses single key for navigation
ja: same model for screen readers, single key navigation
cl: author problem, how to not conflict with AT, when they are not AT experts
dp: TAB used in edit fields. in Safari, if you hit TAB you exit a form control.
pp: javascript based text editors can insert TAB character in the edit field
cl: single key navigation may conflict with onkeypress or onkeydown javascript events
al: screen reader arrow keys only
work when you are in screenreader browse mode.
... screen reader captures many keys, they have a pass through
function
... screen reader gets access first (hooking into os), it has
choice to use it and pass it on, or just pass it on
capture first, then bubbling
capture - event starts at html then moves down tree
bubbling: focus first priority, then move to root
some keystrokes (alt to focus menus) UI will grab before it goes to content, other keystrokes UI will allow to go to content
no good documents of how is should and does work (capture and bubble)
conflicts between keypress, keydown, keyup - depends on the key, the OS, and UA
dependent on keyboard api
example: key held down, key repeats. does this fire multiple key events
ja: How does the OS accessibility keyboard functions work with AT, and UA
al: unsure, documentation and implementation issues
<aaronlev> http://www.mozilla.org/access/keyboard/tabindex
al: plug-in keybindings, more conflicts with UA, AT
if plug-in dows not need a key, it should pass it on to the UA, not swallow it.
should have some pass through to the UA function
cl: if stand-alone plug-in, standard practice - should not swallow keys that the application does not need
pp: chaining, if something higher up the api chain gets a key lower level api may not see the event
ja: this is related to 6.10
... also UA extensions keybinding conflicts
al: big conflicts. keybinding negotiation (extension, content access key, plugins)
perhaps assign keys to roles,
or similar to fonts have a list of proposed keys with fallback options
topic 6.6 Programmatic notification of changes (P1)
cl: css adding content to visual rendering, but not to dom
al: difficult to get css information, can tell that it is roman numberals, but not specific item,
is DOM 3 implemented fully?
cl: mutation events in dom2
ja: what is mutation event
cl: attributen name, vlaue, node changed
dom 3 http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/
dom 3 load save http://www.w3.org/TR/2004/REC-DOM-Level-3-LS-20040407/
cl: issues with mutation events, UA implementation of DOM 2 or 3
some AT not listening to dom events and locations
cl: not just limit notifications to AT through the DOM
should include accessibility API
<scribe> ACTION: ja to create technique for AT notification of change through accessibility api. [recorded in http://www.w3.org/2006/09/07-ua-minutes.html#action01]
necessary for AT access to be complete. DOM does not provide enough information.
al: no caret indicator in the DOM
AT must rely on accessibility api for caret informaton/location
This is scribe.perl Revision: 1.127 of Date: 2005/08/16 15:12:03 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: jallan Inferring Scribes: jallan Default Present: Jim_Allan, pparente, DPoehlman, cklaws, Aaron_Leventhal Present: Jim_Allan pparente DPoehlman cklaws Aaron_Leventhal Regrets: Jan Richards WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting Got date from IRC log name: 7 Sep 2006 Guessing minutes URL: http://www.w3.org/2006/09/07-ua-minutes.html People with action items: ja WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]