W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 1999

Re: User Agent Accessibility Guidelines

From: Charles McCathieNevile <charles@w3.org>
Date: Fri, 1 Oct 1999 07:47:00 -0400 (EDT)
To: Kasper Peeters <K.Peeters@damtp.cam.ac.uk>
cc: Ian Jacobs <ij@w3.org>, disc@mnemonic.org, w3c-wai-ua@w3.org
Message-ID: <Pine.LNX.4.10.9910010727480.5015-100000@tux.w3.org>
Although there are cases where keyboard control isn't that handy (think of a
speech-driven palmtop, or even more a pen-driven one) there are a lot of
cases where people cannot use a mouse effectively. (The obvious one is people
who are blind.)

For such people, all functionalities need to be available through the
keyboard. While there are some features that already are, using a differnt
metaphr, I cannot think of anything that cannot be sensibly and usefully
implemented.

To take the drag and drop example:

Imagine the ability to select an object, grab it, and then go to another
object and ask the second one to do something to "whatever has been marked".
This describes, pretty clearly, drag and drop. And the keyboard technique
used in windows of select, copy, select, paste, using application icons. For
people without a useful spatial model (for example those who are using speech
output and the completely linear navigation available via the tab key) that
is much more sensibe than trying to drive around a mouse and hope they hit
the things they are after.

The essential point is to abstract the user interface sufficiently that it
doesn't depend on a particular input or output device. Then it is possible
for people to use your software with the device they need, be it a full
combination of keyboard, force-feedback mouse, dataglove, voice I/O and a 24"
monitor, or a head switch and a morse code buzzer, or anywhere in between.

keep up the feedback.

Charles

On Fri, 1 Oct 1999, Kasper Peeters wrote:

  
  There are two issues here: 1. do all mouse-driven manipulations have a
  useful keyboard equivalent and 2. is it a good idea to drive software
  by simulating keyboard events. For the first one, I think that there
  are definitely things that don't make much sense when done through the
  keyboard (drag and drop, for instance). As far as the second point is
  concerned, I think that the proper way to drive software by external
  means is to expose an API to the outside world. Granted, you list that
  somewhere else too (`make the browser scriptable', or something along
  those lines).
  
Received on Friday, 1 October 1999 07:47:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:24 UTC