W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2008

RE: [XHTML Access] activate boolean? & asserting user control (update)

From: Gregory J. Rosmaita <oedipus@hicom.net>
Date: Thu, 1 May 2008 18:58:31 +0100
To: "Jim Allan" <jimallan@tsbvi.edu>, <public-xhtml2@w3.org>, <w3c-wai-ua@w3.org>, <wai-xtech@w3.org>
Message-Id: <20080501175255.M53514@hicom.net>

aloha, jim!

no, i don't think you are missing anything...

i understand your concern, which is why i feel that the sole material 
question that remains to be answered is:

will a pointer-driven query of an object for which multiple events 
have been defined, be interpreted as activate="yes" for all events,
or is there something that needs to be stated explicitly about UA 
and/or user control over pointer device interaction with object for 
which access has been set?

this is especially pertinent, as not only is the pointer-driven 
experience the dominant one on the web, but also because those 
using simulated pointing devices may need to query an object 
via the pointer interface before any events defined for that 
object are fired...   and, of course, there is always the issue
of inadvertent/accidental mouseOver events being fired without 
the user's cognizance

gregory.
----------------------------------------------
Theory helps us to bear our ignorance of fact.
    -- George Santayana, "The Sense of Beauty"
----------------------------------------------
Gregory J. Rosmaita: oedipus@hicom.net
Camera Obscura: http://www.hicom.net/~oedipus/
----------------------------------------------

---------- Original Message -----------
From: "Jim Allan" <jimallan@tsbvi.edu>
To: "'Gregory J. Rosmaita'" <oedipus@hicom.net>, <public-xhtml2@w3.org>, 
<w3c-wai-ua@w3.org>, <wai-xtech@w3.org>
Sent: Thu, 1 May 2008 12:44:10 -0500
Subject: RE: [XHTML Access] activate boolean? & asserting user control 
(update)

> My concern is that you are asking for functions for a keyboard 
> user that are not available to a mouse user. If a mouse user 
> activates an element - all events fire. The user has no idea 
> what will happen or how many things go off. They only know that 
> an element can be 'clicked on' and something will happen. Why 
> should a keyboard user have the additional functionality of knowing
> events available and choosing which events to fire?
> 
> Or am I missing something?
> 
> Jim
Received on Thursday, 1 May 2008 17:59:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:57 GMT