W3C home > Mailing lists > Public > public-webapi@w3.org > February 2006

ISSUE-32: Accessibility and UI events - how to improve the interaction

From: Web APIs Issue Tracker <dean+cgi@w3.org>
Date: Fri, 24 Feb 2006 13:40:49 +0000 (UTC)
To: public-webapi@w3.org
Message-Id: <20060224134049.3C0B6DAFA8@w3c4-bis.w3.org>


ISSUE-32: Accessibility and UI events - how to improve the interaction

http://www.w3.org/2005/06/tracker/webapi/issues/32

Raised by: Charles Mccathienevile
On product: DOM 3 Events

There are a number of problems with accessibility which are becoming even more 
prominent with the wider range of devices on the web, where authors rely on 
events from a particular kind of user input.

mousein/out, focusin/out / focus/blur generally reflect the same user intent, 
but their specs and implementation are generally pretty different. Which makes 
it difficult either for authors, who have to do a bunch of redundant stuff they 
decide to avoid, or users who just can't activate the functionality the author 
tried to provide.

Should there be mouse up / down fired for a generic activation?

(This is the motivation that gets click to work generically, and hopefully won'
t arise with drag and drop...).
Received on Friday, 24 February 2006 13:40:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:53 GMT