- From: Al Gilman <Alfred.S.Gilman@IEEE.org>
- Date: Tue, 26 Jun 2007 23:05:02 +0200
- To: Martin Kliehm <martin.kliehm@bluemars.net>, public-pfwg-comments@w3.org
At 4:07 PM +0100 17 12 2006, Martin Kliehm wrote: >In xhtml11-aaa-base.dtd the "tabindex" attribute is only bolted on >text containers like "div", "span", "p", "th", "td", and "li". I >don't think this will be sufficient. In common AJAX applications at >least h1-h6 also can get focus, see flickr or netvibes for examples. >Basically anything that's editable, and that's a lot in Web 2.0 >applications. > >Therefore I'd suggest to add "tabindex" to all headline elements, >"address", "dt", "dd", "legend", and "label", perhaps also to all >(other) elements that come with an "accesskey" attribute. I know >"accesskey" is problematic, but I don't aim for the attribute, but >for the reason it was added to certain elements. Though I suppose >adding "tabindex" to %Common.extra.attrib would be too much. Thank you for catching this for us. The working consensus that the group just reached is as follows: >Tabindex shall apply to all elements that can be visible. The reason >is that these elements may receive input events such as mouse events, >and they need to be keyboard navigable. Again, thank you for the good catch. Sorry to have been unresponsive for so long. We are beefing up our issue tracking methods to be ready to handle a Last Call. Al >Best regards, > Martin
Received on Tuesday, 26 June 2007 21:06:21 UTC