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

Re: Next events meeting: 17 Jan 2002 @ 4pm ET

From: Charles McCathieNevile <charles@w3.org>
Date: Sat, 5 Jan 2002 00:14:35 -0500 (EST)
To: Jim Ley <jim@jibbering.com>
cc: <w3c-wai-ua@w3.org>
Message-ID: <Pine.LNX.4.30.0201050009540.9692-100000@tux.w3.org>
Well, I suspect that a visual GUi user would get a message that it is
possible to annotate any element by clicking on it from the content, although
it would be more useful if this could be provided as part of the association
between the trigger and the function it calls.

If you query an element you would like to know that it is possible to use
this trigger. Is there a use for having some further information about where
that trigger is in fact attached, by further querying it? I suspect so.



On Fri, 4 Jan 2002, 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?


Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Saturday, 5 January 2002 00:14:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:32 UTC