Last modified: 2006-01-08 14:50:56 UTC
Using either 'lynx' or 'links' text-browsers, one must cycle through the entire
front page before getting to the search box. This should probably be at the
top, or at least not after the
Wikipedias with 10000 articles or more
Wikipedias with 1000 articles or more
parts. Some blind people still use text-browsers. Having to scroll through a
list of 100+ languages and the list of orphaned page links before getting to
search is unreasonable. I understand that this is almost impossible to change
since it's the basic structure of each page.
Clarified problem in summary, set blocking on markup accessibility tracking bug 367.
Two possible solutions: "skip to navigation" link (which we can hide with CSS, I have a nice trick for it) and/or
move the search box (which I'd like to do). But we should certainly have a skip link - it doesn't hurt and can be of
great help to screen reader, text-only or mobile users.
I don't understand the problem.
Even with very long articles, the search form can be reached by
using the "end" key or keeping "page down" pressed until you
reaches the end.
A possibility is to change the content of the page and put
the long list of wikipedias on another page.
Ashar: not in all text browsers. Some (probably most) you have to tab through each link or form element before you
get to the one you want. Often there are other ways of jumping through a document, but tabbing link by link is the
most common with text browsers.
And this is a problem with all pages, not just the Main Page.
Wich text browser ?(In reply to comment #4)
> Ashar: not in all text browsers. Some (probably most) you have
> to tab through each link or form element before you get to
> the one you want.
All text browser I tested had the "page down" / "end" feature
(lynx, links and its clones).
Can you give an example of a text browser wich:
1/ does not have "end" "page down" feature
2/ is used
3/ is still developped / not totally outdated
> And this is a problem with all pages, not just the Main Page.
Yup, but with the "end" key tip the trouble is solved for every
That only works if you know the search form is at the end
of the page in the first place.
I suggest putting this inside the <head>:
<link rel="search" title="Search" href="#p-search">
This works in lynx and links, afaik, and wouldn't require
that users of other browsers have CSS turned on.
I agree that every text browser allows you to scroll to the bottom quickly. I
also agree that you have to already know the search box is there, which is
silly. When the [[lynx|lynx(browser)]] article was written, the
[[screenshot|Image:MainPage-lynx-brion.png]] shows search at the top!
In HEAD there is now two links to easily jump to navigation and search:
(Redirected from Main Page)
Jump to: navigation, search
Marking as fixed. Will be in 1.6.