WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: event handlers

for

From: Reidy Brown
Date: Sep 6, 2001 3:35PM

I've documented similar behavior for event handlers-- browsers may interpret
events differently. In some cases, it may make sense to perform an action
(such as a highlighted image rollover) on more than one event handlers. <a
href="" onMouseOver="highlightMe();" onFocus="highlightMe();">.
Reidy
-------------------------------------------
Reidy Brown
Accessibility Coordinator/Sr. Software Engineer
Blackboard, Inc.
(202) 463-4860 x236
-------------------------------------------
Blackboard 5.5 Fully Implements Section 508 Accessibility Standards!
Learn more:
http://access.blackboard.com
-------------------------------------------
-----Original Message-----
From: Tim Harshbarger [mailto: <EMAIL REMOVED> ]
Sent: Thursday, September 06, 2001 5:19 PM
To: ' <EMAIL REMOVED> '
Subject: RE: event handlers

Leo,
I am not perfectly certain on some of this, so I tested with the only
browser I have available at the moment. -- IE 5.0.
onClick is not equivalent to onSelect.
onClick is actually device independent. It can be triggered by either
clicking with the mouse or pressing enter on the keyboard. My understanding
is that the onSelect event works better with the select tag. In my quick
test, onSelect did not trigger when I activated the link.
onMouseOver and onFocus do not appear to be exact equivalents.
The onFocus event is not triggered when the mouse pointer is moved over the
object. It will be triggered only if the object is clicked on by the mouse
and the dotted rectangle appears around the object (thus bringing the system
focus to that object.) Keyboard navigation tends to move the system focus
automatically, so the event is triggered immediately.
onMouseOut is not equivalent to onBlur
Moving the mouse away from an object does not trigger the onBlur event since
that does not automatically move the system focus.