17:41:48 RRSAgent has joined #ua 17:41:48 logging to http://www.w3.org/2008/04/03-ua-irc 17:41:59 Zakim, this will be UAWG 17:41:59 ok, Jan; I see WAI_UAWG()1:00PM scheduled to start 42 minutes ago 17:42:06 Meeting: WAI UA 17:42:35 Agenda:http://lists.w3.org/Archives/Public/w3c-wai-ua/2008AprJun/0000.html 17:42:40 Chair: Jan RIchards 17:43:53 Regrets: Jim Allan, Judy Brewer 17:57:57 WAI_UAWG()1:00PM has now started 17:58:04 +[Microsoft] 17:58:58 +Gregory_Rosmaita 17:59:01 -[Microsoft] 17:59:02 +[Microsoft] 17:59:50 +??P4 18:00:31 zakim, [Microsoft] is really KFord 18:00:31 +KFord; got it 18:00:56 +Cantor 18:01:58 zakim, ??P4 is really Jan 18:01:58 +Jan; got it 18:02:57 scribe: Gregory_Rosmaita 18:03:02 scribeNick: oedipus 18:03:09 rssagent make logs public 18:03:39 Current text (see 4.1): 18:03:40 http://www.w3.org/TR/2008/WD-UAAG20-20080312/#principle-operable 18:03:46 JR and JA attempts at requirements that include visual indicators: 18:03:48 http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JanMar/0052.html 18:03:49 http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JanMar/0053.html 18:03:54 JR's attempt at definition of "Keyboard Commands": 18:03:55 http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JanMar/0078.html 18:04:02 + +0154558aaaa 18:04:16 zakim aaaa is Sean_H 18:04:30 zakim 0154558aaaa is Sean_Hayes 18:04:37 zakim, 0154558aaaa is Sean_Hayes 18:04:37 sorry, oedipus, I do not recognize a party named '0154558aaaa' 18:04:42 zakim, aaaa is Sean_Hayes 18:04:42 +Sean_Hayes; got it 18:05:04 KFord has joined #ua 18:05:34 JR: would like to see if new definition i proposed captured discussion from last week, what it missed and needs to be added, then address kelly's concerns about scope creep, and then return to priorities 18:05:51 JR: has everyone seen http://lists.w3.org/Archives/Public/w3c-wai-ua/2008JanMar/0078.html 18:06:00 [general assent] 18:06:06 JR: no replies 18:06:30 SH: been pushing to finish TITAC work for last week; started action item and review of JR's post 18:06:36 JR: will walk group through 18:07:02 JR: looking for meta term to capture access keys accelerator keys, etc. and decided on "keyboard commands" 18:07:51 JR: signals sent from interfaces to keyboard or alternate keyboard -- single key operation (for mute) and multiple key combos, stickykeys, repeatkeys, etc. 18:08:06 SH: IME -- language where not simple mapping from key to language concept 18:08:15 SH: japanese, chinese, etc. 18:08:22 JR: IME? 18:09:00 GJR: IME = Input Method Editor (http://en.wikipedia.org/wiki/Input_method_editor) 18:09:21 ime = input method editor. 18:09:40 Looks like I was a bit slow and Gregory beat me. 18:09:43 AC: like single key - like use of numeric keys; multiple keys simultaneously need to be broken down into 2 -- sequence of keys (stickykeys) for managing menu 18:10:06 http://a11y.org/kafs - basic functionality (defines stickykeys, repeatkeys, etc.) 18:10:50 JR: just a special case of single key -- operating UI with sequence of keys -- not so different from tabbing to list, using arrow to move to desired item; maybe add a note that single keys can be used in sequence to achieve a result 18:10:57 AC: single key in sequence 18:11:18 GJR: should borrow vocabulary from KAFS (builds on XBE Library) 18:11:52 SH: wording used for "accelerator key" talks about a toggle key plus an alpha-numeric key -- not really a combination but a sequence 18:11:57 JR: will take that out 18:12:09 AC: DeadKeys 18:12:14 JR: DeadKeys? 18:13:13 AC: exists in progs like MS Word -press key from key sequence nothing appears on screen -- appears keystroke dead; first keypress, deadkey goes in instead -- control plus comma in word, nothing happens, but if then type an "e" puts an accent upon the key 18:13:34 JR: not quite "dead" -- sequence of single keys where first one sets mode and what input follows follows mode 18:14:07 SH: direct command and sequential commands not pairs -- can have sequences of pluses -- key event can be single key or cluster or keys; not sure either or -- 2 parts of story, but not only parts 18:14:25 GJR: instead of "DeadKeys" "DelayedKeys"? 18:14:48 SH: driving mouse with keys (MouseKeys) and command line intercept also need to be considered 18:15:24 AC: for mouse emulation on keyboard should be mentioned as possibliiity -- draw distinction between keyboard and point-and-click -- keyboard not a substitute for mouse (bounded mouse free agent) 18:15:42 KF: need to state that feature like MouseKeys is not sufficient means of making keyboard accessible 18:15:59 AC: exactly -- people jump to conclusion that MouseKeys are acceptable alternate 18:16:30 SH: 2 concepts: keyboard commands and broader concept keyboard operations 18:16:36 s/operations/operation 18:16:53 JR: require keyboard operation in UAAG2 and one of them will be keyboard commands 18:17:06 SH: command line interfaces? like sequential commands, but not really 18:17:10 JR: worth considering 18:17:35 AC: command line usually ignored 18:17:54 SH: "power shell" - drive command line -- unix/linux world command lines prevalent 18:17:57 SH: need to consider 18:17:59 AC: agree 18:18:01 JR: agree 18:18:03 GJR: agree 18:18:06 KF: agree 18:18:35 TOPIC: Distinctions - Where you need indicators and were one doesn't 18:19:06 JR: broke down into 2 groups: direct commands (tied to particular UI control for app function in order to achieve action with one keystroke) 18:19:18 JR: direct command just does what you want done right away 18:19:56 JR: sequential commands cannot be repeated immediately and less common for them to activate controls (arrow keys for mouse pointing on list -- need to note not same as other sequential things) 18:20:42 SH: an accelerator key is a single character that gives focus to object and triggers default event -- default event may be to make menu pop-up, then use sequential keys 18:20:55 JR: no point in pressing accelerator key multiple times 18:21:09 SH: set up a mode so that direct commands are available for specific purposes 18:21:22 SH: think have all right concepts but haven't teased out fully 18:21:57 AC: useful to describe in functional terms rather than "sequential" and "direct" -- on windows, moving foucus to objects and then activting objects 18:22:10 SH: "before event" activates it, but may need subsequent action 18:22:40 SH: fundamental difference: moving and sending events to things one means of driving interface, directly reaching into functionality another 18:23:11 AC: when press control plus f if happen to press alt key for entering a mode, global keystrokes may no longer work / may be trumped 18:24:18 GJR: precedence needs to be addressed -- OS keys usually trump all others 18:24:36 JR: fundamental dividing line between commands that cause navigation and those that don't? 18:24:52 SH: yes, on windows -- don't know globally, but important distinction 18:25:06 SH: those that don't cause change of focus dealt with differently 18:25:18 -Gregory_Rosmaita 18:26:28 +Gregory_Rosmaita 18:26:47 [scribe missed due to being disconnected] 18:27:12 KF: what file do you want to save this as -- still activating command, just stopping to let user save file where wants 18:27:40 JR: "wedge" word/concept -- not moving focus, because there is focus that moves but plenty of other things move focus 18:28:33 SH: if no UI just a bag of functions -- reaching around UI to get to functions directly (figuratively speaking) 18:29:08 AC: "direct commands" almost always available via UI -- faster ways to do things than working through menuing system or mouse on toolbar 18:29:44 JR: because people who designed them took care to program that way 18:29:55 GJR: tabindex="-1" doesn't apply to mouse 18:29:57 JR: right 18:31:48 JR: indicators is point judy stressing; good point, but tricky to draw a box around; direct commands might be subdivided into 2 -- those associated with currently rendered controls and those not directly associated with rendered controls (F1 to open help; typing an a to input an "a" character); idea is indicator on first class needs to expose accelerator; don't think could require in UI, but could be easily accessible 18:32:18 SH: not just "currently rendered" but "currently rendered in current context" 18:32:20 JR: good point 18:32:46 JR: existing functionality in menus not controversial, but toolbars... 18:33:19 SH: operating system might get involved; AT might supply extra commands, plugins or embedded apps may cause extra commands/reassignment of key commands; 18:33:49 SH: concept of whether these things are static -- is CONTROL + S always the same, or are bindings only available under certain state or condition or context 18:34:25 JR: who provides -- JB's point is that a lot of people who need this aren't running ATs -- using keyboard with less strength, digits, etc. 18:35:02 SH: user agent like EMACS -- who provides control keys to EMACS -- written by tens of thousands of people funneled into app -- what is properly the UA's in that respect? 18:35:34 JR: in EMACS direct keyboard alternatives -- programmatically available to be understoon on activation of button tantamount to a display? 18:35:50 SH: point is that actual commands provided by script writer being interpreted by EMACS shell 18:36:12 SH: EMACS an environment which can be extended -- many others in wide use 18:36:44 SH: AT only another contributor to an environment -- why compllicated to deliver myriad software 18:37:28 JR: can cut through that by saying it is up to claimant of conformance has to document everything: this tool plus this extension plus whatever, and disavow conformance for other external/third party pieces 18:37:54 JR: UAAG 1.0 had a lot that could be punted to ATs, but a lot of issues where people need accessibility without AT 18:38:03 AC: like to think of keyboard as an AT 18:38:24 SH: dynamic content/interfaces -- certain amount of predictability necessary 18:38:29 JR: in terms of? 18:38:44 JR: underline under F to signal accelerator key? 18:39:18 SH: alt-w-1 maps to third tab in display sequence - created at runtime, can't write down because dependent upoon runtime conditions -- created by what user is doing 18:39:53 AC: all the more reason from moving away from "commmand" language -- how to drive app with keyboard not knowing which command to use -- principles for driving an application and operating it needed 18:40:36 JR: Judy driving towards putting in a state of UI and being able to call up a llist of availabilities when in that state 18:40:51 JR: new operating system functionality potentially 18:40:58 JR: not a minor issue 18:41:31 JR: would like people to comment on list on this; took notes for revising proposal, but need feedback between calls 18:41:37 SH: not sure if on the list 18:42:17 JR: discusses process with SH 18:42:51 rrsagent, make minutes 18:42:51 I have made the request to generate http://www.w3.org/2008/04/03-ua-minutes.html oedipus 18:44:33 AC: another complexity is direct commands associated with controls (ALT plus a selects all from menu) - when ALT cancels menu mode, will input an "a" instead of chosing item; context is paramount; when in a specific mode, rules may be different -- context and knowing where one is is the exxential need 18:44:47 JR: modes that are part of making a command, larger mode (where am i when make command) -- will put that all in 18:45:07 JR: SH's active context point also to be added 18:45:36 JR: fifteen minutes left -- continue talking about keyboard access next week, perhaps -- review what is in document for rest of minutes 18:45:54 http://www.w3.org/TR/2008/WD-UAAG20-20080312/#principle-operable 18:46:17 "4.1.1 Keyboard: The user can, through keyboard input alone, navigate to and operate all of the functions included in the user interface (e.g., navigating and selecting content within views, operating the user interface "chrome", installing and configuring the user agent, and accessing documentation), except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints (e.g. freeform drawing). This applies 18:46:20 @@The UAWG is currently working to ensure that sufficient requirements are in place regarding how keyboard shortcuts are conveyed to the user (e.g. visual indicators, documentation, etc.). Input from area experts would be welcome.@@ 18:46:20 @@The UAWG is also currently working to ensure that the requirements properly cover interaction with video and dynamic Web content. Input from area experts would be welcome.@@ 18:46:47 JR: 3 levels of success criteria -- will be in level A things unless otherwise indicated 18:48:40 JR: 4.1.1 says if can do with mouse, should be able to do with keyboard except for free-form drawing -- don't say "do same actions" because not using mouse handles, but could still resize window, for example 18:48:45 AC: that is key 18:48:58 SH: "at least one way of using the keyboard..." 18:49:07 AC: don't know what chrome means 18:49:30 JR: chrome is basically all parts of UA that are not rendering contents 18:50:01 KF: chrome and frame often used interchangablely -- UI that app devs developed is chrome, content goes into viewport 18:50:27 JR: piece of text on screen rendered from content, but if right click on it, the context menu IS chrome 18:51:26 JR: if someone wants a radio button, they state radio button and label it -- that is kind of chrome -- rendered on user instruction, but part of chrome; AJAX releated content is rendered and NOT part of chrome 18:51:43 JR: reads "4.1.2 Precedence of Keystroke Processing: The precedence of keystroke processing between the user agent interface, user agent extensions, content keystroke operations administered by the user agent (e.g., access keys), and executable content (e.g., key press events in scripts, etc.) is documented.@@NEW@@ " 18:52:13 JR: no particular order required, but documentaton of a particular order IS required 18:52:36 AC: need to state much more clearly than stated now 18:52:39 JR: agree 18:52:44 "4.1.3 No Keyboard Trap: If focus can be moved to a component with the keyboard, then at least one of the following is true: @@WCAG2 concept@@ 18:52:44 (a) standard keys: focus can be moved away from the component with the keyboard using standard navigation keys (i.e., unmodified arrow or tab keys), or 18:52:44 (b) documented non-standard keys: focus can be moved away from the component with non-standard keys and the user is advised of the method. 18:53:40 JR: if in a plug in and no key combo to escape, need to be able to discover escape method 18:54:26 -Gregory_Rosmaita 18:54:44 SH: problematic -- really on borderline of UA and GL merge -- inside content that has hijacked normal navigation, how can user [droppee] 18:58:44 -KFord 18:58:45 -Cantor 18:58:46 -Sean_Hayes 19:00:14 RRSAgent, make minutes 19:00:14 I have made the request to generate http://www.w3.org/2008/04/03-ua-minutes.html Jan 19:00:31 RRSAgent, set logs public 19:01:09 Zakim, bye 19:01:09 leaving. As of this point the attendees were Gregory_Rosmaita, KFord, Cantor, Jan, +0154558aaaa, Sean_Hayes 19:01:09 Zakim has left #ua 19:01:24 RRSAgent, bye 19:01:24 I see no action items