W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2002

event handlers Re: [w3c-wai-gl] <none>

From: Charles McCathieNevile <charles@w3.org>
Date: Thu, 3 Jan 2002 21:27:08 -0500 (EST)
To: Gregg Vanderheiden <GV@TRACE.WISC.EDU>
cc: "GLWAI Guidelines WG (GL - WAI Guidelines WG)" <w3c-wai-gl@w3.org>
Message-ID: <Pine.LNX.4.30.0201032117330.23519-100000@tux.w3.org>
HTML 4 defines a number of event handlers of two kinds: some which are based
on keyboard or mouse events

onmouseover, onmouseout, onclick, ondblclick, onmousemove, onkeypress,
onkeyup, onkeydown.

The others are generic (not device-specific) and are onload, onunload,
onfocus, onblur, etc.

DOM 2 adds an event called onactivate (and onfocusin, onfocusout, to cope
with historic compatibility problems in browsers) which is also
non-device-specific. It leaves out the keyboard events but does include the
device-specific mouse events. These event triggers are also used in SVG and
SMIL, along with some time-based events. (Those are not device-specific, and
are already covered by the requirements that the timebase can be changed -
SMIL 2 goes into considerable detail about how that works).

Using these event triggers means that there is no device specific way of
triggering an event, and the user agent should be able to fire them
via the keyboard, mouse, pen, voice, etc. Keyboard access will of course only
be ensured by the User Agents implementing the spec to provide a keyboard
method, but that seems likely.

The only reason to provide a direct manipulation interface is for speed, at
the total expense of device independence or portability as well as of
accessibility. Although of course in a very limited interface, such as a
double key, it is going to be difficult to move around the interfcae fast
enough to control a plane. Using the generic events would enable them to be
fired by scripts that a user can create to optimise various functions -
effectively like using macros in a piece of software.


On Thu, 3 Jan 2002, Gregg Vanderheiden wrote:

  Here is a summary of the results of the telecon meeting today
  1 - need a complete list of generic event handlers.  (or a place where
  they are officially defined. )   (PUT IN GLOSSARY?? )
  2 - is a requirement for generic going to iNSURE keyboard acccess.  If
  not then do we need to require keyboard access as an option?
  3 - is there an exception for any type of direct manipulation interface.
  What about flying a plane.  (note: remember that slow operation is
  already required for non competitive or realtime situations
Received on Thursday, 3 January 2002 21:27:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:33:40 UTC