W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2000

Re: Proposal: Single command input and edits to checkpointsabout "easy access" (2.3 and 10.8)

From: Ian Jacobs <ij@w3.org>
Date: Tue, 25 Jul 2000 11:17:13 -0400
Message-ID: <397DAF79.BB7ECA01@w3.org>
To: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
CC: w3c-wai-ua@w3.org
Jon Gunderson wrote:
> 
Hi Jon,

Do you have any comments on the proposals?

> >The following proposals offer a definition of "single
> >command input" and way to avoid related but different terms
> >that might cause confusion in checkpoints 2.3 and 10.8.
> >
> >Proposal 1) Definition: Single command input
> >
> >   In this document, single command input means that the
> >   action required of the user is the simplest that can be
> >   recognized by the user agent for a particular input method.
> >   For the keyboard, this means "single key input", i.e., a
> >   single key press, without modifier keys such as "alt", "control",
> >   "apple", etc. For voice input, "single voice command input"
> >   means an individual vocal cue, though the number of words
> >   in a command may be more than on (e.g., "Activate link",
> >   "Page down", etc.) and should be few in number.
> >   For graphical user interface components, single command input means
> >   direct activation of the UI control (i.e., buttons, not menu
> >   items) with a pointing device.
> >   Note that any navigation through UI controls (by pointing
> >   devices or keyboard navigation) does not constitute single
> >   command input. Double command input means two single commands
> >   (e.g., a modifier key and another key), triple means three, etc.
> >
> >   The user agent may change the input configuration dynamically,
> >   and this may affect the set of single command bindings. The set
> >   of single command bindings is relative to an input configuration.
> >   For example, when the user is entering text, the number of
> >   single key input bindings may be reduced significantly.
> >   Or, if the user agent offers a special "table
> >   navigation mode" for cell-to-cell or cell-to-header navigation,
> >   those single key commands exist within the context of the
> >   table navigation mode.
> >
> >Note about proposal 1: Delete the part about different input modes
> >   from the note after checkpoint 10.5 since now it's in a definition.
> >
> >Proposal 2) Checkpoint 2.3
> >
> >   At the 20 July teleconference [2], we discussed eliminating
> >   the expression "easy access" in checkpoints 2.3 and 10.8.
> >   The proposal was to use "single command", which I find very
> >   confusing (using the term "single" to describe two different
> >   but closely related concepts is a mistake).
> >
> >   For checkpoint 2.3, refer to my proposal [3], which uses the
> >   term "easy access" but explains the techniques that would meet
> >   the requirement. I hope that this proposal satisfies the
> >   resolution from the 20 July teleconference [2]:
> >
> >     "No objections to modification of Jon's proposal for modification
> >2.3
> >      RESOLVED.- accept new proposal with modifications."
> >
> >Proposal 3) Checkpoint 10.8
> >
> >   For checkpoint 10.8, Jon proposed [4] the following wording:
> >
> >      10.8 Ensure that the default input configuration
> >           allows one step activation of frequently used
> >           functionalities.
> >
> >   Rather than "one step" (or "single step") I propose saying
> >   something like this:
> >
> >   <NEW>
> >        10.8 Ensure that the default input configuration
> >             offers single or double command access
> >             to functionalities the user is likely to use
> >             frequently.
> >           Note: For example, the default configuration
> >           might allow history navigation with arrow keys
> >           alone, modified arrow keys (e.g., Alt-left arrow)
> >           or both.
> >   </NEW>
> >
> >
> >Notes about Proposal 3:
> >
> >  a) Some background about the goals of checkpoint
> >     10.8 provided by Charles in his review with some developers [4].
> >
> >  b) There is no resolution marked in the
> >     20 July minutes about checkpoint 10.8.
> >
> >  _ Ian
> >
> >[1] http://www.w3.org/WAI/UA/WD-UAAG10-20000707
> >[2] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JulSep/0097.html
> >[3] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JulSep/0132.html
> >[4] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JulSep/0032.html
> >[5] http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

-- 
Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
Tel:                         +1 831 457-2842
Cell:                        +1 917 450-8783
Received on Tuesday, 25 July 2000 11:17:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:14 GMT