- From: Danny Ayers <danny.ayers@gmail.com>
- Date: Tue, 21 Feb 2012 14:51:14 +0100
- To: HTML WG <public-html@w3.org>
- Cc: Leif Halvard Silli <lhs@malform.no>
I just discovered this has already been processed as: Bug 13942 - Allow @autofocus on any element with @tabindex https://www.w3.org/Bugs/Public/show_bug.cgi?id=13942 Hixie's response: Status: Rejected Change Description: no spec change Rationale: Let's see how people do with autofocus on <input> before we start making it even easier to move focus around. I don't find that very satisfactory, adding a feature inconsistently strikes me as a bad idea, it unnecessarily increases the cognitive load of developers/publishers. Leif's proposal resolves this. Cheers, Danny. On 19 February 2012 13:57, Danny Ayers <danny.ayers@gmail.com> wrote: > I may well have overlooked something, but this appears to be an inconsistency. > > When a page is loaded, the focus may be directed to a form control > using the autofocus attribute. But this attribute isn't available on > regular links, and I can't find a way of doing it that doesn't rely on > script. > > The use case I have is for slide shows (i.e. a prepared navigation > path) but I suspect this also has accessibility implications. > I've set up a demo of the behaviour using script at: > http://dannyayers.com/stuff/pp/ > > If there isn't an approach I've missed, two alternatives seem apparent: > 1. allow the autofocus attribute on <a> elements > 2. add autofocus behaviour to tabindex > > 1. would seem preferable as 2. would impact existing documents. > > Cheers, > Danny. > > -- > http://dannyayers.com > > http://webbeep.it - text to tones and back again -- http://dannyayers.com http://webbeep.it - text to tones and back again
Received on Tuesday, 21 February 2012 13:51:49 UTC