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, 16 Nov 2005 19:07:30 +0100
Message-ID: <437B7562.501@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.
Isn't there a problem that an event handler may be on the container for 
something so that it can listen to the event on any descendant? It just 
uses event.target in the script to see where the event happened. We also 
have the problem that there are no descriptions for XML event handlers, 
so even if a user can get there, how will they know what these 
programmatic event names mean?

To help the discussion, here are 3 kinds of navigation we need to 
support in every kind of web content:

1. Simple controls are in tab order
- Examples: checkbox, slider

2. Container controls group focusable children
- Examples: trees, lists, radio groups, spreadsheets
- The last focused child is in the tab order
- Other children can be focused via the pointer
- Key navigation managed by the container widget (often arrows)

3. Non-interactive content won’t take input
- Examples: progress meter, alerts, doc structural elements
- Click to focus skips, goes up parent chain for focus
- On screen keyboards don’t list them as choices
- Screen readers skip them in navigation order
- Voice input skips them during “say what you see” vocab buildup
Received on Wednesday, 16 November 2005 18:07:40 GMT

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