Community
Participate
Working Groups
The up and down keystrokes are ignored by the Bookshelf view which means you are forced to use the mouse.
Arrows don't work (yet), but you can tab and hit enter. We hope to have a fix for getting arrows to work; currently tabs are what the browser supports by default (help is implemented using html).
Default browser support for keyboard navigation uses the arrows for scrolling. I am not sure we should override browser's behavior, but it can certainly be done.
If they are just regular links, then you should stick with Tab since that is standard for a web browser. As long as there is some way of accessing them, we're OK for accessibility. For usability, though, it should match the user's expectations. That is, if they think it's a web browser, it should work like a web browser. If it looks like a regular app, it should work like a regular app. The problem with Help using an embedded web browser is that it may be unclear to the user whether it's a web browser or a regular app.
Help can be used in other non-eclipse scenarios (standalone and infoceter/server-based), so in some cases it is clear this is a browser app. The next build will have support for associating a default topic to a book (i.e. a TOC). We should also have "welcome" kind of page for the help bookshelf as well. Perhaps we can use these pages to provide a quick introduction to the help features, accessibility included. The major problem right now is getting focus inside the help content. See http://dev.eclipse.org/bugs/show_bug.cgi?id=12398
Fixed. One must use tabs to navigate entries in the bookshelf.
