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

Re: Repair of Pointer Based Events

From: David Poehlman <poehlman1@home.com>
Date: Fri, 9 Feb 2001 19:31:38 -0500
Message-ID: <001201c092f8$d4d8da20$2cf60141@mtgmry1.md.home.com>
To: "Charles McCathieNevile" <charles@w3.org>, "Jon Gunderson" <jongund@uiuc.edu>
Cc: "WAI PF group" <w3c-wai-pf@w3.org>, "WAI UA group" <w3c-wai-ua@w3.org>
I was thinking of it more along the lines of actually tying a key
binding by repair to the element such that it would expose the
activity.

----- Original Message -----
From: "Charles McCathieNevile" <charles@w3.org>
To: "Jon Gunderson" <jongund@uiuc.edu>
Cc: "WAI PF group" <w3c-wai-pf@w3.org>; "WAI UA group"
<w3c-wai-ua@w3.org>
Sent: February 09, 2001 6:18 PM
Subject: Re: Repair of Pointer Based Events


Certainly it is an acceptable part of a solution.

What is missing from mousekeys is the ability to navigate from element
to
element, or indeed to really know where the mouse is non-visually in
terms of
the document structure. What is missing from commmon keyboard
implementations
is the ability to fire mouse events.

The simplest technique for getting this to work that I can think of is
to
provide a function that brings the mouse cursor/pointer to the
location of
the currently focussed element. This provides for mouse hover, and the
rest
is already available using mousekeys - in other words operating system
standards. (I haven't tried to implement this - how easy it is depends
on the
window management system being used.)

As far as I can tell that would satisfy the user requirement and
the various checkpoint requirements. Albeit not the most elegant of
user
interfaces, is possibly good enough that people won't worry what is
the most
elegant for a while longer.

cheers

Charles McCN

On Fri, 9 Feb 2001, Jon Gunderson wrote:

  Response in JRG to CMN:

  >[snip]
  >   The reasons for reducing the requirement for active elements:
  >   1. We do not have any implementation experience for this
feature.
  >
  >MouseKeys implements this feature. The only bit it does not
commonly provide
  >is the abilitry  to move the mouse cursor to a point that has been
reached by
  >keyboard navigation (which isn't explicitly required by the
feature - it is
  >just a technique that leverages the fact that mousekeys is readily
available
  >on common platforms such as linux, MacOS, Windows)

  JRG: Would you consider mouse keys to be an acceptable part of a
solution
  to this repair function?


  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



--
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: I-cubed, 110 Victoria Street, Carlton VIC 3053, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis
Cedex, France)
Received on Friday, 9 February 2001 19:31:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:29 UTC