https://bugzilla.wikimedia.org/show_bug.cgi?id=29199
Ruben <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #5 from Ruben <[email protected]> --- I would like to add that for most users (not using screen readers or other accessibility tools), the usefulness and impact of good tab indexing greatly depends on the input context. When are the users more likely to be in a typing modus - and have one or two hands on the keyboard? I would claim that after searching for something, you are more probable to be in that context, then you are while browsing pages. If you are on the search result page, you most definite have just typed in something. You will also very likely want to access one of the first links in the search result (rather than make a new search). As of now, the tab indexing varies between browsers - and they do a pretty bad job at guessing correctly. At a quick glance, I actually didn't see any tabindexes in the HTML. On a search result page, you will have to have good arguments for not letting the result set have high index priority. Google understands this and does it very well as they even remove the search button (as most users know you can press enter directly in the search input field. On the search result page you'll have the hands on the keyboard, and not being able to tab down to the first result(s) is a major usability issue for MediaWiki and Wikipedia. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
