W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2005

Re: W3C User Agent Teleconference for 3 November 2005

From: Aaron Leventhal <aaronlev@moonset.net>
Date: Wed, 02 Nov 2005 12:49:44 -0500
Message-ID: <4368FC38.4000808@moonset.net>
To: Charles McCathieNevile <chaals@opera.com>
CC: jimallan@tsbvi.edu, WAI-UA <w3c-wai-ua@w3.org>


> An alternative would be to define, in format specifications, that 
> anything that has intereaction behaviour (an event listener, or a 
> default interactivity), should be focusable. As an example, the SVG 
> Tiny 1.2 specification has this notion, and I filed a last call 
> comment on the way they handle events which includes the notion that 
> things with event listeners should be focusable by default. As I am a 
> member of the SVG working group I expect a resolution - look for a 
> public comment from them at some point.

You can put a listener on a container element and the script might only 
care about events to a few targets within the container. Can't tell what 
the script is doing.

Allowing anything to be focusable also doesn't work, because when you 
click on something the browser needs to know what element in the 
ancestor chain to put focus on. It could be that a <span> shouldn't get 
focused, but it's <td> or <table> ancestor should. Impossible to know 
without allowing the author to somehow specify.

- Aaron
Received on Wednesday, 2 November 2005 17:49:53 GMT

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