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

RE: Auto-Tabbing - Is this ever allowed?

From: Léonie Watson <lwatson@paciellogroup.com>
Date: Thu, 28 May 2015 17:20:35 +0100
To: "'Wishnew, Mary '" <mary.wishnew@citi.com>, "'IG - WAI Interest Group List list'" <w3c-wai-ig@w3.org>
Message-ID: <030b01d09962$3af93640$b0eba2c0$@paciellogroup.com>
-----Original Message-----
From: Wishnew, Mary [mailto:mary.wishnew@citi.com] 
Sent: 28 May 2015 16:41

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.  


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.

Speaking as a screen reader/keyboard user, I strongly dislike having auto-tab functionality imposed on me. It is unexpected, and based on a flawed assumption that it is helpful.

It's worth noting that it takes me more time and effort to correct mistakes caused by auto-tab, than it does to move focus for myself. 


Léonie Watson - Senior accessibility engineer
@LeonieWatson @PacielloGroup PacielloGroup.com
Received on Thursday, 28 May 2015 16:20:55 UTC

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