16:14:05 RRSAgent has joined #ua 16:14:05 logging to http://www.w3.org/2010/04/15-ua-irc 16:14:07 RRSAgent, make logs public 16:14:07 Zakim has joined #ua 16:14:09 Zakim, this will be WAI_UAWG 16:14:09 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 46 minutes 16:14:10 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 16:14:10 Date: 15 April 2010 16:36:57 Agenda+ Action-178 http://www.w3.org/2002/09/wbs/36791/DefinitionOfFocus/ 16:57:31 jeanne has joined #ua 16:58:07 Greg has joined #ua 16:58:59 WAI_UAWG()1:00PM has now started 16:59:07 +Greg 17:00:21 +Jim_Allan 17:00:31 Agenda+ pending action items http://www.w3.org/WAI/UA/tracker/actions/open 17:00:49 regrets: MHakkenin 17:00:53 kford has joined #ua 17:01:10 Is the phone working for people? 17:01:16 yes 17:01:27 zakim, code? 17:01:27 the conference code is 82941 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), jeanne 17:01:37 Odd, I keep calling trying to enter the code and it just goes to a ring. 17:01:39 +Jeanne 17:02:42 jeanne says wait for the prompt to finish 17:02:50 then enter the code 17:03:04 sharper has joined #ua 17:03:16 Zakim, code? 17:03:16 the conference code is 82941 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), sharper 17:03:27 KimPatch has joined #ua 17:04:16 +KimPatch 17:04:28 +[Microsoft] 17:04:42 +??P14 17:04:47 zakim, ??P14 is sharper 17:04:47 +sharper; got it 17:04:48 zakim, microsoft is kford 17:04:48 +kford; got it 17:06:28 regrets+ plauke 17:07:12 zakim, agenda? 17:07:12 I see 2 items remaining on the agenda: 17:07:14 1. Action-178 http://www.w3.org/2002/09/wbs/36791/DefinitionOfFocus/ [from AllanJ] 17:07:15 2. pending action items http://www.w3.org/WAI/UA/tracker/actions/open [from AllanJ] 17:10:19 zakim, take up Item 1 17:10:19 agendum 1. "Action-178 http://www.w3.org/2002/09/wbs/36791/DefinitionOfFocus/" taken up [from AllanJ] 17:10:29 http://www.w3.org/2002/09/wbs/36791/DefinitionOfFocus/results 17:10:47 I am back. 17:10:50 Topic: Active Input Focus 17:11:17 active input focus and input focus -- put in same block? 17:11:32 If and when we collapse multiple terms into a single glossary entry, I suggest we include cross-references. 17:12:37 Greg: one glossary entry for all three terms sorted under input focus, because they're really all the same except active and inactive variations. 17:13:41 Another alternative to collapsing the input focus, inactive input focus, and active input focus together would be to have a single definition for input focus and a separate pair of entries for active and inactive. Thus when we use "active input focus" (which the document does NOT currently use at all) we could have that phrase be two separate links, one to "active" and one to "input focus". 17:14:23 Jim: do use inactive anywhere in the success criteria 17:14:47 Jim: Does this is just muddy the waters 17:15:27 Greg: we can cut out eventually, but it's good to have the moment of thinking about them at first 17:17:16 Great: at the moment neither active nor an active is used in the document with the exception of one e.g. Which is a different meaning of the term 17:17:58 Jim: anybody have any objections to including all of them 17:19:04 Greg: leave them in but put a note if not used 17:20:04 action: Jeanne to update the glossary entry to note the definitions that are not currently used as an Editors Note. 17:20:04 Created ACTION-355 - Update the glossary entry to note the definitions that are not currently used as an Editors Note. [on Jeanne Spellman - due 2010-04-22]. 17:20:12 To clarify, leave them in the working draft, and the note would say they could be removed from the final version if not used. 17:20:57 Just a note, re "active input focus" and other related terms, Technically you can't have "the" active input focus, but rather one input focus for each input device. Thus this should really be "For an input device..." 17:22:23 Action: Jeanne to add def of Active input focus - The *input focus* location in the *active viewport*. The active input focus is usually visibly indicated. In this document "active input focus" generally refers to the active keyboard input focus. to glossary, ncu 17:22:23 Created ACTION-356 - Add def of Active input focus - The *input focus* location in the *active viewport*. The active input focus is usually visibly indicated. In this document "active input focus" generally refers to the active keyboard input focus. to glossary, ncu [on Jeanne Spellman - due 2010-04-22]. 17:22:42 Jim: NCU, not currently used 17:23:34 Topic: Active Selection 17:23:35 Jim: accept them as individual units and put them in for now -- 17:23:46 Jeanne: editors issue 17:24:20 Active selection 17:24:22 action: Jeanne to take the glossary definitions of various different "Focus" and collapse them into one Focus glossary entry with details. 17:24:22 Created ACTION-357 - Take the glossary definitions of various different "Focus" and collapse them into one Focus glossary entry with details. [on Jeanne Spellman - due 2010-04-22]. 17:24:36 Jim: in the current viewport 17:25:08 Greg: of the selections in the current window 17:26:03 action: Jeanne to add Active Selection - The *input focus* location in the *active viewport*. The active input focus is usually visibly indicated. In this document "active input focus" generally refers to the active keyboard input focus. to glossary. ncu 17:26:03 Created ACTION-358 - Add Active Selection - The *input focus* location in the *active viewport*. The active input focus is usually visibly indicated. In this document "active input focus" generally refers to the active keyboard input focus. to glossary. ncu [on Jeanne Spellman - due 2010-04-22]. 17:26:17 topic: Cursor 17:26:20 Topic: Cursor 17:28:21 Jim: Patrick's comment -- cursor/^? 17:28:35 Greg: we should get him to explain what he means 17:29:12 Jim: is the technical people people call it ^ and others call it cursor? 17:29:50 ^ = carat 17:30:04 s/carat/caret 17:30:51 Greg: Mark suggesting and new success criteria -- put that as an issue? 17:31:25 Jim: Marcs question is should an inactive viewport remain visible 17:31:34 Jim: is there an accessibility benefit 17:32:52 Greg:when you're using assistive technology if you need to move the Arrow, whose information as to where you command will have affect in the document window -- that being said I would not want to put this in because it would be going against the user interface conventions in many platforms. Windows convention is to hide inactive ^. 17:33:09 Greg:we could put it in as low priority 17:33:26 Jim: didn't hear any objections pending comments from Patrick -- 17:33:49 none here. 17:34:12 Jim: any objections to the definition 17:35:13 Greg:were we have the definition in the second sentence -- changing to flashing vertical bar in text field, also known as ^ 17:35:15 Action: Jeanne to add cursor - Visual indicator showing where keyboard input will occur. There are two types of cursors: *focus cursor* (e.g. the dotted line around a button) and *text cursor* (e.g. the flashing vertical bar in a text field, also called a 'caret'). Cursors are active when in the active viewport, and inactive when in an inactive viewport. to the glossary 17:35:15 Created ACTION-359 - Add cursor - Visual indicator showing where keyboard input will occur. There are two types of cursors: *focus cursor* (e.g. the dotted line around a button) and *text cursor* (e.g. the flashing vertical bar in a text field, also called a 'caret'). Cursors are active when in the active viewport, and inactive when in an inactive viewport. to the glossary [on Jeanne Spellman - due 2010-04-22]. 17:35:47 Topic: focus cursor 17:36:50 Greg: focus cursor is one subset of cursor-- focus cursor and text cursor -- we could make that clear here 17:39:00 Simon: does it make more sense to you have something called touch cursor and focus cursor within that 17:39:19 Greg: make sense -- collapse in the editing process 17:40:09 action: jeanne to add Focus Cursor: Indicator that *highlights* a user interface element to show that it has *keyboard focus*, e.g. a dotted line around a button, or brightened title bar on a window. There are two types of cursors: *focus cursor* (e.g. the dotted line around a button) and *text cursor* (e.g. the flashing vertical bar in a text field). to the glossary. 17:40:09 Created ACTION-360 - Add Focus Cursor: Indicator that *highlights* a user interface element to show that it has *keyboard focus*, e.g. a dotted line around a button, or brightened title bar on a window. There are two types of cursors: *focus cursor* (e.g. the dotted line around a button) and *text cursor* (e.g. the flashing vertical bar in a text field). to the glossary. [on Jeanne Spellman - due 2010-04-22]. 17:40:17 Jim: no objections 17:40:38 Topic: Focusable Elements 17:41:27 action: jeanne to do a global change of "focusable items" to "focusable elements" 17:41:27 Created ACTION-361 - Do a global change of "focusable items" to "focusable elements" [on Jeanne Spellman - due 2010-04-22]. 17:41:28 Greg: note that in some places its focusable elements and sometimes items -- should consistent, probably all be focusablel elements 17:41:55 Jim: the objections 17:42:42 action: Jeanne to add Focasable element- Any element capable of having input focus, e.g. link, text box, or menu item. In order to be accessible and fully usable, every focusable element should take keyboard focus, and ideally would also take pointer focus. 17:42:42 Created ACTION-362 - Add Focasable element- Any element capable of having input focus, e.g. link, text box, or menu item. In order to be accessible and fully usable, every focusable element should take keyboard focus, and ideally would also take pointer focus. [on Jeanne Spellman - due 2010-04-22]. 17:42:46 Jim: if it were bound visibly then everything would show up as long as you were in ^ browsing-- could we get someone to craft an extension 17:43:40 Greg: working on learning Firefox extensions so we can prototype 17:44:52 Jim: David Bolter, browserscope.org where compiling information about browser functionality -- his statement was I wonder if this is a good venue for building a library of browser extensibility or keep track of limitations 17:44:54 www.browserscope.org 17:45:06 http://code.google.com/p/browserscope/ 17:45:38 Jim: we might be able to jump in and squeeze out a little accessibility space in there 17:45:45 Topic: highlighting 17:45:55 Jim: looks like a done deal 17:46:28 action: jeanne to add Highlight - Emphasis indicated through the user interface. For example, user agents highlight content that is selected,focused, or matched by a search operation. Graphical highlight mechanisms include dotted boxes, changed colors or fonts, underlining, magnification, and reverse video. Synthesized speech highlight mechanisms include alterations of voice pitch and volume... 17:46:28 Created ACTION-363 - Add Highlight - Emphasis indicated through the user interface. For example, user agents highlight content that is selected,focused, or matched by a search operation. Graphical highlight mechanisms include dotted boxes, changed colors or fonts, underlining, magnification, and reverse video. Synthesized speech highlight mechanisms include alterations of voice pitch and volume... [on Jeanne Spellman - due 2010-04-22]. 17:46:30 ...("speech prosody"). User interface items may also be highlighted, for example a specific set of foreground and background colors for the title bar of the active window. Note that content that is highlighted may or may not be a *selection*. to the glossary 17:46:44 Topic: inactive input focus 17:47:09 Jim: no objections 17:47:53 Changing "The" to "An" would get around the problem I mentioned earlier about the fact that there can be one input focus per input device. 17:48:08 action: jeannes to add Inactive Input Focus - An input focus location in an inactive viewport such as a background window or pane. The inactive input focus location will become the active input focus location when input focus returns to that viewport. An inactive input focus may or may not be visibly indicated. to the glossary 17:48:08 Sorry, couldn't find user - jeannes 17:48:18 action: jeanne to add Inactive Input Focus - An input focus location in an inactive viewport such as a background window or pane. The inactive input focus location will become the active input focus location when input focus returns to that viewport. An inactive input focus may or may not be visibly indicated. to the glossary 17:48:18 Created ACTION-364 - Add Inactive Input Focus - An input focus location in an inactive viewport such as a background window or pane. The inactive input focus location will become the active input focus location when input focus returns to that viewport. An inactive input focus may or may not be visibly indicated. to the glossary [on Jeanne Spellman - due 2010-04-22]. 17:48:30 Topic: inactive focus 17:48:55 Topic: inactive selection 17:49:10 Action: Jeanne to add INactive Selection - A selection that does not have the* input focus* and thus does not take input events. to the glossary 17:49:10 Created ACTION-365 - Add INactive Selection - A selection that does not have the* input focus* and thus does not take input events. to the glossary [on Jeanne Spellman - due 2010-04-22]. 17:49:20 ncu 17:50:07 Topic: Input focus 17:50:28 action: Jeanne to add Input Focus - The place where input will occur if a viewport is active. Examples include keyboard focus and pointing device focus. Input focus can also be active (in the active viewport) or inactive (in an inactive viewport). 17:50:28 Created ACTION-366 - Add Input Focus - The place where input will occur if a viewport is active. Examples include keyboard focus and pointing device focus. Input focus can also be active (in the active viewport) or inactive (in an inactive viewport). [on Jeanne Spellman - due 2010-04-22]. 17:50:41 Topic: keyboard focus 17:51:50 Jim: Patrick comment -- distinguish between keyboard input and keyboard interaction -- trying to distinguish between typing and causing something to activate, but I think anything from the keyboard is keyboard input 17:52:25 Greg: not sure we're understanding his concern-- goahead, but have him elaborate 17:52:37 Jim: any objections to that 17:53:45 Greg: understand there's a major difference between this keyboard focus and ANSI -- this is talking about a location where input will occur -- others talk about keyboard focus as current assignment to element -- that's much more targeted, it's a property that gets moved around and always about a user interface element not a screen location. 17:54:25 Jim: ours is broader -- you do a left arrow it moves left in addition to being in a menu system -- we have to be vague because we're trying to cover so many different bases were we get really convoluted in our words 17:54:38 action: Jeanne to add Keyboard Focus - The screen location where keyboard input will occur if a viewport is active. Keyboard focus can be active (in the active viewport) or inactive (in an inactive viewport). to the glossary 17:54:38 Created ACTION-367 - Add Keyboard Focus - The screen location where keyboard input will occur if a viewport is active. Keyboard focus can be active (in the active viewport) or inactive (in an inactive viewport). to the glossary [on Jeanne Spellman - due 2010-04-22]. 17:54:42 Jim: no objections 17:54:49 Topic: point of regard 17:56:55 Jim: point of regard is what we have been using 17:58:18 Greg: we didn't change it 17:59:04 everything stays current, no action 17:59:11 Greg: we should keep term consistent between versions 17:59:18 Topic: pointer 18:00:05 Jim: Mark has same question about calling out UIs 18:00:54 Greg:confusion between pointing device and pointer -- touch screens typically pointing device not pointer, device is users finger. We can put in note clarifying this because it's obviously a point of confusion. 18:02:33 NOTE: When touch screens are used, the "pointing device" is a combination of the touch screen and the user's finger or stylus. On most systems there is no pointer (on-screen visual indication) associated with this type of pointing device. 18:03:06 action: jeanne to add Pointer: Visual indicator showing where pointing device input will occur. The indicator can be moved with a pointing device or emulator such as a mouse, pen tablet, keyboard-based mouse emulator, speech-based mouse commands, or 3-D wand. A pointing device click typically moves the *input focus* to the pointer location. The indicator may change to reflect different... 18:03:06 Created ACTION-368 - Add Pointer: Visual indicator showing where pointing device input will occur. The indicator can be moved with a pointing device or emulator such as a mouse, pen tablet, keyboard-based mouse emulator, speech-based mouse commands, or 3-D wand. A pointing device click typically moves the *input focus* to the pointer location. The indicator may change to reflect different... [on Jeanne Spellman - due 2010-04-22]. 18:03:08 ...states. NOTE: When touch screens are used, the "pointing device" is a combination of the touch screen and the user's finger or stylus. On most systems there is no pointer (on-screen visual indication) associated with this type of pointing device. to the glossary 18:03:39 Topic: pointing device focus 18:06:03 Jim: pointing device focus versus pointer 18:06:15 Greg: focus versus Arrow 18:07:09 scribe: KimPatch 18:07:19 This hierarchical summary helps to explain the relationship between the terms, and thus why some terms are included to clarify the parallel construction: 18:07:21 1. Input focus (active/inactive) “The place where input will occur if a viewport is active” 18:07:23 1.1. Keyboard focus (active/inactive) “The screen location where keyboard input will occur if a viewport is active” 18:07:24 1.1.1. Cursor (active/inactive) “Visual indicator showing where keyboard input will occur” 18:07:27 1.1.1.1. Focus cursor (active/inactive) “Indicator that highlights a user interface element to show that it has keyboard focus” 18:07:28 1.1.1.2. Text cursor (active/inactive) “Indicator showing where keyboard input will occur in text” 18:07:30 1.2. Pointing device focus (active/inactive) “The screen location where pointer input will occur if a viewport is active” 18:07:32 1.2.1. Pointer “Visual indicator showing where pointing device input will occur” 18:09:05 Greg: hierarchical: pointing device, focuse location, then visual indicator of focus location 18:09:22 action: Jallan to write Jan about clarification of pointing device focus 18:09:22 Created ACTION-369 - Write Jan about clarification of pointing device focus [on Jim Allan - due 2010-04-22]. 18:09:48 Jim: no objections 18:10:14 action: jeanne to Pointing Device Focus The screen location where pointer input will occur if a viewport is active. There can be multiple pointing device foci, for example when using a screen sharing utility there is typically one for the user's physical mouse and one for the remote mouse. NOTE: this term is not used in the document other than the glossary. to the glossary 18:10:15 Created ACTION-370 - Pointing Device Focus The screen location where pointer input will occur if a viewport is active. There can be multiple pointing device foci, for example when using a screen sharing utility there is typically one for the user's physical mouse and one for the remote mouse. NOTE: this term is not used in the document other than the glossary. to the glossary [on Jeanne Spellman - due 2010-04-22]. 18:10:25 Topic: selection 18:12:40 Greg: principle 2 -- selection should be one of the criteria 18:13:08 Greg: selection, highlighting a focus are all currently missing from 2.1 and all should be there 18:14:01 Jim: could fall under 2.16? subset of an element? 18:15:06 So to 2.1.6 add bullets for selection, highlighting, and input device foci. 18:16:16 Jim: highlighting versus selection? 18:17:16 Greg: e-mail with screenshots that clarified. Highlighting can be used for many different things -- one is to indicate selection, but it's also used for other things such as highlighting matched text after a search operation, when navigation is separated from focus-- using search key -- highlighting is very broad 18:19:48 action: to change 2.1.6 to add bullets for selection, highlighting, input device focuses 18:19:48 Sorry, couldn't find user - to 18:20:03 action: jeanne to change 2.1.6 to add bullets for selection, highlighting, input device focuses 18:20:03 Created ACTION-371 - Change 2.1.6 to add bullets for selection, highlighting, input device focuses [on Jeanne Spellman - due 2010-04-22]. 18:20:40 action: Jeanne to add Selection http://www.w3.org/2002/09/wbs/36791/DefinitionOfFocus/results#xq14 to the glossary 18:20:40 Created ACTION-372 - Add Selection http://www.w3.org/2002/09/wbs/36791/DefinitionOfFocus/results#xq14 to the glossary [on Jeanne Spellman - due 2010-04-22]. 18:20:41 Jim: any objections to the definition -- no objections 18:20:56 Topic: split focus 18:22:34 Greg: regardless of whether its useful in this document is it clear 18:22:54 Jim: perhaps if we were a couple more examples it would be useful but we don't need to get into now 18:23:38 action: jeanne to add Split Focus - A state when the user could be confused because the input focus is separated from something it is usually linked to, such as being at a different place than the selection or similar highlighting, or has been scrolled outside of the visible portion of the viewport. [Note: this term is not used in the document other than the glossary. This may or may not... 18:23:38 Created ACTION-373 - Add Split Focus - A state when the user could be confused because the input focus is separated from something it is usually linked to, such as being at a different place than the selection or similar highlighting, or has been scrolled outside of the visible portion of the viewport. [Note: this term is not used in the document other than the glossary. This may or may not... [on Jeanne Spellman - due 2010-04-22]. 18:23:39 ...stay in the final document, but is a useful concept.] to glossary 18:23:48 Topic: text cursor 18:24:05 -Jeanne 18:24:36 Jim: comments about adding caret 18:26:38 Greg: rather than a reference to caret browsing in the definition why not an example -- keeps definition as concise as possible 18:27:04 Jim: is an example of user versus developer? Developer caret, user cursor 18:27:31 Greg: we should use both terms -- the commonly used terms because no one term will be useful to everybody 18:28:03 Indicator showing where keyboard input will occur in text (e.g. the flashing vertical bar in a text field, also called a caret). 18:29:09 Greg: difficult to define browsing -- navigating within a block of text 18:29:46 action: jeanne to add Text Cursor - Indicator showing where keyboard input will occur in text (e.g. the flashing vertical bar in a text field, also called a caret). 18:29:46 Created ACTION-374 - Add Text Cursor - Indicator showing where keyboard input will occur in text (e.g. the flashing vertical bar in a text field, also called a caret). [on Jeanne Spellman - due 2010-04-22]. 18:29:59 Jim: any objections to using definition as Greg wrote it in IRC-- no objections 18:30:27 no objection 18:32:13 Jim: any preference for dates, November 1-5 18:32:49 Jim: any objections to latter part of the week -- slightly better chance of Simon participation -- no objection 18:33:02 -kford 18:33:07 -sharper 18:33:32 -KimPatch 18:33:34 -Greg 18:33:35 -Jim_Allan 18:33:37 WAI_UAWG()1:00PM has ended 18:33:39 Attendees were Greg, Jim_Allan, Jeanne, KimPatch, sharper, kford 18:34:46 rrsagent, make minutes 18:34:46 I have made the request to generate http://www.w3.org/2010/04/15-ua-minutes.html AllanJ 18:37:49 5122069315 18:46:29 zakim, please part 18:46:29 Zakim has left #ua 18:47:52 rrsagent, please part 18:47:52 I see 22 open action items saved in http://www.w3.org/2010/04/15-ua-actions.rdf : 18:47:52 ACTION: Jeanne to update the glossary entry to note the definitions that are not currently used as an Editors Note. [1] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-20-04 18:47:52 ACTION: Jeanne to add def of Active input focus - The *input focus* location in the *active viewport*. The active input focus is usually visibly indicated. In this document "active input focus" generally refers to the active keyboard input focus. to glossary, ncu [2] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-22-23 18:47:52 ACTION: Jeanne to take the glossary definitions of various different "Focus" and collapse them into one Focus glossary entry with details. [3] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-24-22 18:47:52 ACTION: Jeanne to add Active Selection - The *input focus* location in the *active viewport*. The active input focus is usually visibly indicated. In this document "active input focus" generally refers to the active keyboard input focus. to glossary. ncu [4] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-26-03 18:47:52 ACTION: Jeanne to add cursor - Visual indicator showing where keyboard input will occur. There are two types of cursors: *focus cursor* (e.g. the dotted line around a button) and *text cursor* (e.g. the flashing vertical bar in a text field, also called a 'caret'). Cursors are active when in the active viewport, and inactive when in an inactive viewport. to the glossary [5] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-35-15 18:47:52 ACTION: jeanne to add Focus Cursor: Indicator that *highlights* a user interface element to show that it has *keyboard focus*, e.g. a dotted line around a button, or brightened title bar on a window. There are two types of cursors: *focus cursor* (e.g. the dotted line around a button) and *text cursor* (e.g. the flashing vertical bar in a text field). to the glossary. [6] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-40-09 18:47:52 ACTION: jeanne to do a global change of "focusable items" to "focusable elements" [7] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-41-27 18:47:52 ACTION: Jeanne to add Focasable element- Any element capable of having input focus, e.g. link, text box, or menu item. In order to be accessible and fully usable, every focusable element should take keyboard focus, and ideally would also take pointer focus. [8] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-42-42 18:47:52 ACTION: jeanne to add Highlight - Emphasis indicated through the user interface. For example, user agents highlight content that is selected,focused, or matched by a search operation. Graphical highlight mechanisms include dotted boxes, changed colors or fonts, underlining, magnification, and reverse video. Synthesized speech highlight mechanisms include alterations of voice pitch and volume... [9] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-46-28 18:47:52 ACTION: jeannes to add Inactive Input Focus - An input focus location in an inactive viewport such as a background window or pane. The inactive input focus location will become the active input focus location when input focus returns to that viewport. An inactive input focus may or may not be visibly indicated. to the glossary [10] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-48-08 18:47:52 ACTION: jeanne to add Inactive Input Focus - An input focus location in an inactive viewport such as a background window or pane. The inactive input focus location will become the active input focus location when input focus returns to that viewport. An inactive input focus may or may not be visibly indicated. to the glossary [11] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-48-18 18:47:52 ACTION: Jeanne to add INactive Selection - A selection that does not have the* input focus* and thus does not take input events. to the glossary [12] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-49-10 18:47:52 ACTION: Jeanne to add Input Focus - The place where input will occur if a viewport is active. Examples include keyboard focus and pointing device focus. Input focus can also be active (in the active viewport) or inactive (in an inactive viewport). [13] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-50-28 18:47:52 ACTION: Jeanne to add Keyboard Focus - The screen location where keyboard input will occur if a viewport is active. Keyboard focus can be active (in the active viewport) or inactive (in an inactive viewport). to the glossary [14] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T17-54-38 18:47:52 ACTION: jeanne to add Pointer: Visual indicator showing where pointing device input will occur. The indicator can be moved with a pointing device or emulator such as a mouse, pen tablet, keyboard-based mouse emulator, speech-based mouse commands, or 3-D wand. A pointing device click typically moves the *input focus* to the pointer location. The indicator may change to reflect different... [15] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T18-03-06 18:47:52 ACTION: Jallan to write Jan about clarification of pointing device focus [16] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T18-09-22 18:47:52 ACTION: jeanne to Pointing Device Focus The screen location where pointer input will occur if a viewport is active. There can be multiple pointing device foci, for example when using a screen sharing utility there is typically one for the user's physical mouse and one for the remote mouse. NOTE: this term is not used in the document other than the glossary. to the glossary [17] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T18-10-14 18:47:52 ACTION: to change 2.1.6 to add bullets for selection, highlighting, input device focuses [18] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T18-19-48 18:47:52 ACTION: jeanne to change 2.1.6 to add bullets for selection, highlighting, input device focuses [19] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T18-20-03 18:47:52 ACTION: Jeanne to add Selection http://www.w3.org/2002/09/wbs/36791/DefinitionOfFocus/results#xq14 to the glossary [20] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T18-20-40 18:47:52 ACTION: jeanne to add Split Focus - A state when the user could be confused because the input focus is separated from something it is usually linked to, such as being at a different place than the selection or similar highlighting, or has been scrolled outside of the visible portion of the viewport. [Note: this term is not used in the document other than the glossary. This may or may not... [21] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T18-23-38 18:47:52 ACTION: jeanne to add Text Cursor - Indicator showing where keyboard input will occur in text (e.g. the flashing vertical bar in a text field, also called a caret). [22] 18:47:52 recorded in http://www.w3.org/2010/04/15-ua-irc#T18-29-46