Andy, I will pause development, and write up a WIKI. The big problem with tab indexes is tables or extra components that people don't want to tab to (skipping over an advertisement link for example). Tables tab left to right, sometimes people want newspaper style tabs - top to bottom then left to right.
I think that perhaps we can discuss different approaches on a wiki that could make development easier than having to set a tab index on every component. I'll start one within the week that has different options, with pros and cons so that we can have a discussion. Thanks, Andrew On Sat, Mar 22, 2008 at 7:31 AM, Andy Schwartz <[EMAIL PROTECTED]> wrote: > > So if I have a log in form, the tab indexes would probably be: > > > > user name: 1 > > password: 2 > > submit: 3 > > > > And then everything else would not have one. This way all the > > "template" components would be tabbed, just not first. > > In this particular use case it sounds like you actually like the > natural tab order of the form (user name, password, submit), but want > to make life easier for the end user by placing the focus in the user > name field when the page is loaded. I think that, rather than mucking > with tab indicies, a better solution to this problem would be to take > advantage of tr:document's initialFocusId attribute. IIRC > initialFocusId is not currently honored in the default accessibility > mode, which makes this attribute somewhat less useful, but I think we > should revisit this decision - ie. I think that we should start > honoring initialFocusId in the default accessibility mode. > > Andy >
