Initial focus should be auto focus
In discussing the question of inserting a tabindex to create an auto focus for certain pages (/user*, /node/add*, node/*/edit) so that the cursor is always sitting in the first field of the event in question, v suggested that this was more of a usability issue than an accessibility one. I recorded a friend with mobility challenges trying to create an account for those who want some understanding of how important this could be.
So because accessibility & usability are intertwined issues anyways, I thought I'd post a discussion here and see if I can't get some more direction on this. I would think that it would be pretty intuitive that if you click on a unique link to a form that you'd first want to do something with the form rather than mess about with the links in the nav and left sidebar.
Thoughts would be appreciated. Oh yeah, and if this kinda stuff interests you, please join the accessibility group too.
Mike
Really great you made a
Really great you made a movie! Next time just cross post the initial post. I don't know much about this, but anything that makes it more accessible seems like a win situation - I would stay away from end-user forms but in node/add and any slightly privileged user related, yes.
Why stay away from /user /user/register & /user/password ?
Glad you liked the video. Was easy to do and got dinner & wine out of the deal too.
It was an afterthought to open a channel to the usability folks, so thought it was best to open a new topic rather than appending an old one. Who knows how that would have worked (would it just have appeared half way down the list in the usability discussion??).
In anycase, wanted to know what your concern is with the user login, registration & forgotten password pages. Why should they auto-focus? It's not like this would be done for all login blocks, just when these forms are in the main content area.
Mike
OpenConcept | CLF 2.0 | Podcasting
Remember that auto-focus
Remember that auto-focus does focus the field, which catches all keystrokes. No arrow keys or page up/down for scrolling, the field receives those events. Auto-focus is good, but should not be overused. Only use it when you are reasonably certain you know where everyone will start. For example, don't auto-focus search in the sidebar of every page. I've seen too many sites overdo auto-focus lately.
Thanks for the warning
The question is if it is reasonable to believe on certain key pages that the focus will on the central form element. Key login paths, adding/editing nodes seem like good bets. Wouldn't want to see others though at this time. Certainly not in core.
Mike
OpenConcept | CLF 2.0 | Podcasting