WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: form "auto tab"

for

From: Bryan Garaventa
Date: Nov 9, 2011 1:30PM

Would it be benefitial to add cancelBubble=true to this as well?


----- Original Message -----
From: "Ryan Hemphill" < <EMAIL REMOVED> >
To: "WebAIM Discussion List" < <EMAIL REMOVED> >
Sent: Wednesday, November 09, 2011 12:01 PM
Subject: Re: [WebAIM] form "auto tab"


> The skipping of form fields is probably happening because the tab key
> event
> is getting passed to the focus target. It's easy enough to avoid by a
> event.preventDefault() et al of bubbling. Here's my little catchall which
> seems to knock out pretty much everything..
>
> function preventEvents(event)
> {
> /* NOTE: insures that keyup event doesn't fire on target as well. */
> event.preventDefault();
> event.stopPropagation();
> event.stopImmediatePropagation(); /* you may not want this one, depending
> on your situation, so comment it out if things are not in a happy place */
> }
>
> That being said, I still hate the idea of auto-tab. I don't blame anyone
> who ends up complaining about it's use either. They aren't whining - it
> really is annoying and a bad idea.
>
>
>
>
> On Wed, Nov 9, 2011 at 2:51 PM, Paul Adam < <EMAIL REMOVED> > wrote:
>
>> I also find the auto-advancing form fields annoying and recommend
>> avoiding
>> it. I can't find the exact location in WCAG but I thought it recommended
>> that if you use this sort of feature to warn the users before hand. Makes
>> sense to me. I often end up hitting the TAB button and wind up 2 form
>> fields ahead and have to go back to correct my mistakes.
>>
>> On Wed, Nov 9, 2011 at 2:35 PM, Jon Brundage < <EMAIL REMOVED> >
>> wrote:
>>
>> > hi All,
>> >
>> > I'd like to get input on the use of "auto tab" in form field
>> > navigation.
>> I
>> > generally feel it is a poor practice, but would like to know the
>> > general
>> > consensus on its use.
>> >
>> > Thanks,
>> >
>> > Jon
>> >
>> >