W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2015

Re: Auto-Tabbing - Is this ever allowed?

From: David Ashleydale <dashleydale@gmail.com>
Date: Thu, 28 May 2015 15:31:31 -0700
Message-ID: <CAGELhn=NS48+ZSjEbhGirfbC3URNT9+otosn9UMDPFV5WcEB+w@mail.gmail.com>
To: "Wishnew, Mary" <mary.wishnew@citi.com>
Cc: IG - WAI Interest Group List list <w3c-wai-ig@w3.org>
Hi Mary,

Do you have any more information about which fields they want to apply the
auto tab to?

Obviously auto tab cannot be used on First Name and Last Name fields
because there's no way for the page to know when you are done typing. But
for something like a three field SSN number there is an exact number of
characters to enter.

If they are proposing auto tab for some fields and not all, that's where it
can get confusing to users. They start wondering if each field is going to
auto tab or not and it can really slow someone down.

Plus, for the SSN example, while it could be nice to not have to type, tab,
type, tab, etc., I find that it is much easier for everyone to just use one
field that can hold all nine digits. If there is a desire to not display it
as a nine digit number, you can actually display it on the form as 3-2-4
digits even though it is one field.

Auto tabbing, to me, is just a way to solve a problem that has better
solutions. If you could give us more details, I'm sure I could help come up
with better solutions.


On Thursday, May 28, 2015, Wishnew, Mary <mary.wishnew@citi.com> wrote:

> I have worked in the past with a reputable Third Party Accessibility
> Vendor that has advised auto-tabbing should never be allowed for a form
> with input fields such as an online application.  The application would
> have multiple input fields such as First Name, Last Name, Address, phone
> number, SSN, etc.  I realize that if the user isn't advised the form will
> auto tab they can end up multiple fields down the form instead of moving to
> the next field as they don't realize the form has auto-tabbed.
> I understand auto-tabbing without notification is considered a violation
> of:
> 3.2.2 On Input: Changing the setting of any user interface component does
> not automatically cause a change of context unless the user has been
> advised of the behavior before using the component. (Level A)
> The development team wants to add auto-tabbing back into the application
> form.  What is the industry best practice?  I would like to get input from
> those on the list about auto-tabbing. I am receiving significant push back
> to add this tabbing back into the form and would like to advise accurately.
> Thanks in Advance,
> Mary Wishnew
Received on Thursday, 28 May 2015 22:31:58 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 25 May 2017 01:54:15 UTC