- From: Jon Gunderson <jongund@uiuc.edu>
- Date: Fri, 04 Jan 2002 14:19:37 -0600
- To: "Jim Ley" <jim@jibbering.com>, <w3c-wai-ua@w3.org>
Jim, A mousedown attached to the body element is usually useless (from an accessibility perspective) since any element in the document can respond to it. While technically you could test every element and trigger mouse down, this would be a usability nightmare. That is why UAAG only requires activation of events associated with explicit event handlers of an element. The event bubbling issue has been discussed in the past [1] and this was our resolution to the problem. So at least one boolean query must only provide event handler information that is explicitly associated with a particular element (or is it node?). Jon [1] http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990602.html At 05:45 PM 1/4/2002 +0000, Jim Ley wrote: > > Todo: The WAI groups need to provide a use case of when it's useful > > to know that an event handler was declared on the current node > > and not an ancestor. > >Is this not necessary to make the representation of the events to the >user easier, for example, when reaching a body element (say) with an >onmousedown event attached, a voice user, may be informed by a prompt >that mousedown is possible, you wouldn't then want the UA to prompt on >every child node, which is all that a Boolean check would give is it not? > >Jim. Jon Gunderson, Ph.D., ATP Coordinator of Assistive Communication and Information Technology Division of Rehabilitation - Education Services MC-574 College of Applied Life Studies 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 WWW: http://www.w3.org/wai/ua
Received on Friday, 4 January 2002 15:19:43 UTC