[Accessibility_sig] auto tabs

[Jim Allan]

Screen reader users and other keyboard users (myself included) routinely hit
tab to move to the next form field after data entry. I have great annoyance
when there is an auto-tab because now when I hit the tab key, I am moved 1
field beyond  where I want to be (essentially 2 tab key presses - mine and
the auto-tab) and must back up. If I don't catch that it jumped a form
field, because I am not using speech and just merrily filling in the
appropriate fields (phone number for example) without watching the cursor,
then I may enter incorrect information in several fields, before catching
that it jumped and having to correct them. Or a java-script validation alert
pops up and says "you missed a field", or "must have 3 (or 4) digits in this
field", etc.) Auto-tab breaks the keyboard-user's expectation of what will
happen on a form.  Others may have different opinions.I don't like auto-tab.

Jim

 

From: accessibility_sig-bounces at knowbility.org
[mailto:accessibility_sig-bounces at knowbility.org] On Behalf Of Forrest
Washburn
Sent: Tuesday, October 30, 2007 7:26 AM
To: accessibility_sig at knowbility.org
Subject: [Accessibility_sig] auto tabs

 

I have several fields in a field set which will make up one long number
separated by dashes. My client wants an auto tab feature which moves the
focus after the client has typed the correct number of characters. My
question is will this disorient the user of screen readers if it steals the
focus from them. If this is NOT an issue, does anyone have an accessible
script for this?

 

Forrest Washburn
TCEQ IRD/SD&M
512.239.5326
Building A Cube 085

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://knowbility.org/pipermail/accessibility_sig_knowbility.org/attachments/20071030/6ddca79d/attachment.html