Re: keyboard navigation issues

It helps to think about universal access to commanding the
computer as like key remapping but a little higher level.

Daniel had experience in the X work with defining abstract
commands and binding concrete device events to them.

This is the general direction I hope we can use DOM to go in:
display device objects with methods where you write the
properties of the object, and command device objects where you
listen to the events on the attached device.

CSS migrates to something which provides abstract-to-concrete
class bindings.  And yes, for control as well as for display.

In dual-display scenarios as when one is mirroring a graphic
display in speech, one wants to put listeners on the displays as
well, as Rich S. has pointed out.

Neil Scott out at the Archimedes project has a rather highly
developed system that we could learn a lot from.  Their system
uses an unmodified desktop workstation and emulates the mouse and
keyboard signals of the "normal" user exactly at that interface.

But there is a whole computer in the assistive device and they
often expand composite nominal-interface actions from macros that
are better adapted to voice or head-stick input.  It's that
library of macros that I expect contains best current practice
in terms of universal command concepts.

Al

Reference for Archimedes Project:

http://www-csli.stanford.edu/arch/arch.html

to follow up on what Jon Gunderson said:
> From w3c-wai-ua-request@w3.org  Thu Aug 20 12:58:24 1998
> Resent-Date: Thu, 20 Aug 1998 12:55:42 -0400 (EDT)
> Resent-Message-Id: <199808201655.MAA00718@www19.w3.org>
> Message-Id: <199808201655.LAA08439@staff2.cso.uiuc.edu>
> X-Sender: jongund@staff.uiuc.edu (Unverified)
> X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 
> Date: Thu, 20 Aug 1998 11:53:14 -0500
> To: Ian Jacobs <ij@w3.org>
> From: Jon Gunderson <jongund@staff.uiuc.edu>
> Cc: cltrar@login.dknet.dk, w3c-wai-ua@w3.org
> In-Reply-To: <35DC4666.248B6913@w3.org>
> References: <199808141356.IAA20198@staff1.cso.uiuc.edu>
> 	<199808201538.KAA22059@staff1.cso.uiuc.edu>
> Subject: Re: keyboard navigation issues
> Resent-From: w3c-wai-ua@w3.org
> X-Mailing-List: <w3c-wai-ua@w3.org> archive/latest/396
> X-Loop: w3c-wai-ua@w3.org
> Sender: w3c-wai-ua-request@w3.org
> Resent-Sender: w3c-wai-ua-request@w3.org
> Precedence: list

> I don't think it would be part of CSS.  But a separate specification could
> be developed that may need to be more plateform specific.
> Jon
> 
> 
> At 11:53 AM 8/20/98 -0400, Ian Jacobs wrote:
> >Jon Gunderson wrote:
> >> 
> >> Good points Claus.
> >> We have CSS for adjusting presentation.
> >> Could we not have some type of style sheet for adjusting user input?
> >
> >CSS2 offers very little in the way of
> >style sheet control over the user interface. Features
> >include:
> >
> > - stylistic changes when certain mouse events occur
> >   (hover, focus)
> >
> > - Some control of cursor presentation
> >
> > - The ability to refer to system colors and
> >   fonts in property values.
> >
> > - Dynamic outlines (e.g., to show focus).
> >
> >
> >See also a recent Submission to W3C that discusses "Action Sheets",
> >which are like style sheets but for behavior. See [1].
> >
> > - Ian
> >
> >[1] http://www.w3.org/TR/NOTE-AS
> >   
> >-- 
> >Ian Jacobs (jacobs@w3.org) 
> >Tel/Fax: (212) 684-1814 
> >http://www.w3.org/People/Jacobs
> > 
> 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, 20 August 1998 13:32:16 UTC