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

Re: Events

From: Jon Gunderson <jongund@staff.uiuc.edu>
Date: Thu, 29 Oct 1998 08:39:18 -0600
Message-Id: <199810291440.IAA03899@staff2.cso.uiuc.edu>
To: Charles McCathieNevile <charlesn@srl.rmit.EDU.AU>, WAI UA group <w3c-wai-ua@w3.org>
I think that we should have guidelines that say develop accessible user
interfaces.  Mouse based input is not inherently bad.  It is only "bad"
when the author (programmer) does not also have keyboard equivalents that
are visible to the user.   Therefore the guidelines I think should talk
aboutcreating an accessible user interface, not a mouseless one.

Jon


At 05:07 AM 10/29/98 +1100, Charles McCathieNevile wrote:
>The discussion on PAGL was about logical events (those which specified a 
>function) as opposed to device-dependent events.
>
>The division below was the list as it stands. It occurred to me that we
>could easily enough add onActivate - corresponding in a mouse interface to
>onClick, and to pressing return to activate the item with focus in a
>keyboard interface. 
>
>I'm not sure about the rest, but I suspect that onMouseDown, onMouseUp,
>onKeyDown, onKeyUp and onMouseMove are related to selecting a part of the
>document. In determining how to do that we are likely to sort out the
>relationship between the current device-dependent attributes and new
>'logical' event triggers that can be triggered from various interfaces (eg
>voice)
>
>Which seems to me to leave onMouseOut and onDblClick out in the cold. One 
>of the consequences of this is that we should recommend against using 
>those events which we are likely to lose (except for providing 'eye-candy' 
>- stuff that has no functional importance) and make suggestions about how 
>the rest might be used in the page authoring guidelines. (have i said 
>this before on this group? if so, sorry)
>
>Charles McCathieNevile
>
>From: http://lists.w3.org/Archives/Public/w3c-wai-gl/1998OctDec/0029.html
>
>Chris is right, so for the sake of completeness I looked up all the event
>attributes again.  Those which I think are device-dependent, and we should
>recommend not be used are: 
>
>onMousedown, onMouseup, onMouseover, onMousemove, onMouseout, onKeydown, 
>onKeyup, onKeypress, onClick, onDblclick
>
>Those which seem to be logical events are:
>
>onFocus, onBlur, onSelect, onChange, onSubmit, onReset, onLoad, onUnload.
>
>It should also be possible to define something like 'onActivate' - which 
>would be equivalent to onClick for a link, but I guess this belongs to 
>other groups.
>
>Charles McCathieNevile
> 
Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
University of Illinois at Urbana/Champaign
1207 S. Oak Street
Champaign, IL 61820

Voice: 217-244-5870
Fax: 217-333-0248
E-mail: jongund@uiuc.edu
WWW:	http://www.staff.uiuc.edu/~jongund
	http://www.als.uiuc.edu/InfoTechAccess
Received on Thursday, 29 October 1998 09:40:45 GMT

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