Is a ‘single tab-stop’ a valid goal for a toolbar which is almost the whole of the UI?
This W3C best practice document says
To optimize the benefit of toolbar widgets...
Implement focus management so the keyboard tab sequence
includes one stop for the toolbar and arrow keys move
focus among the controls in the toolbar
I can certainly do this, and indeed the example linked from that entry is very, very close (in terms of complexity) to what we need.
The 'problem' (if it be a problem at all), is that the toolbar in our product is pretty much our whole UI.
We have a couple of other controls not located in the toolbar. One of these is "Exit" and the other is "About" - they are special, liminal cases, each producing a modal window which takes the user out of the main activity.
A couple of other controls become available via the toolbar, some of them as actions in popup menus (see screenshot of our prototype).
There are three of these popups, each containing from two to four action buttons. And here I collide with another recommendation from the same document:
Avoid including controls that require arrow keys
to operate, such as textbox or radio group.
If unavoidable, include only one such control
and make it the last element .
Catch-22?
There are a couple of other controls which appear in a separate panel after one of the toolbar actions is activated.
The toolbar, then, is (pretty much) the UI.
If I understand correctly, the "single tab stop" design goal is intended to make it easier/faster to navigate the UI with a keyboard or similar device. It is a 'cognitive chunking' mechanism.
But if I follow the 'best practice' recommendation in this case, then almost all the controls will be available only with arrow keys (plus Home / PageUp etc.), rather than the tab. I am curious whether this really is desirable and in-keeping with established and preferred idioms.
It means that the tab key will be used hardly at all. Is that ok? There's so frequent mention of "tabindex" and "tabbing" that I feel it might be 'wrong' to rely far more on other keys, especially for those three popup action menus.
At the moment, I have a prototype where you tab through the toolbar, and use the arrow keys to select actions from the popup menus (if activated).
I will of course be testing a couple of approaches with seasoned keyboard users, and the results of those tests will weigh heavily, but until then, I'm curious to discover the rationale of the 'single tab stop', and how strongly to adhere to whatever principles lie behind it.