RE: An accessible way to format Date and Social Security Number form fields?

The date may be tricky, because 12108 could be 1/21/08 or 12/1/08.   You
could require leading zeros, but presumably users who don't want to
enter "/" won't want to enter zeros, either.  Personally I'd rather
enter slashes than leading zeros (or the leading "20"), but I have no
idea what others would prefer.  Is it possible build a form to interpret
multiple formats?

Jean

----------------------------------
Jean Fox
Bureau of Labor Statistics
2 Mass Ave, NE, Room 1950
Washington, DC  20212
(202) 691-7370 (ph)
(202) 691-7426 (fax)


-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On
Behalf Of Accessys@smart.net
Sent: Tuesday, October 28, 2008 9:54 AM
To: Jennifer Gauvreau
Cc: w3c-wai-ig@w3.org
Subject: Re: An accessible way to format Date and Social Security Number
form fields?



actually you also need to also consider the folks who automatically or
otherwise actually do enter the - or / so that you don't end up with two
of each.  12--3456789 or whatever

Bob



On Tue, 28 Oct 2008, Jennifer Gauvreau wrote:

> Hello,
>
>
>
> One of my project teams raised a question regarding the most 
> accessible way to apply formatting to a text entry form field.
>
>
>
> Background:
>
> Currently, when adding or updating data within a web application, 
> users are required to input identifiers, date, and amounts in a 
> certain format. For example, TIN must be in 12-3456789 format 
> (including the -), date must be in mm/dd/yyyy format (including the 
> /).  Based on preliminary testing, users mentioned that they are tired

> of inputting the - or /. We want to make it more convenient to the 
> user by filling in the - or / for the user.
>
>
>
> The question is when to prefill the hyphen, slash, dollar sign, and/or

> comma. The team proposed three options:
>
> 1. As user is entering their value
>
> 2. After the user enters their value and the focus is lost from the 
> field.
>
> 3. After saving the entry to the database.
>
>
>
> Is one implementation considered more compliant with Section 508 than 
> another? My personal opinion was that the most logical time to apply 
> the formatting would be after the user finishes inputting their value 
> and focus moves off the field option (2). However, I was interested in

> hearing other people's perspectives, particularly if there are any 
> blind or motor-impaired users who would be willing to share their 
> personal experiences.
>
>
>
> Thank you,
>
> Jennifer Gauvreau
>
>
>
> Jennifer Gauvreau, CUA
> Senior Consultant
> Human Factors Practice
> CGI Federal
> T: 703-227-6167
> F: 703-227-4205
> 12601 Fair Lakes Circle, 6th Floor
> Fairfax, VA 22033
> http://www.cgi.com <http://www.cgi.com>
>
> CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging

> to CGI Group Inc. and its affiliates may be contained in this message.
> If you are not a recipient indicated or intended in this message (or 
> responsible for delivery of this message to such person), or you think

> for any reason that this message may have been addressed to you in 
> error, you may not use or copy or deliver this message to anyone else.
> In such case, you should destroy this message and are asked to notify 
> the sender by reply email.
>
>
>
>

-
end
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
occasionally a true patriot must defend his country from its' government
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
"They that can give up essential liberty to obtain a little temporary
safety deserve Neither liberty nor safety",    Benjamin Franklin
-   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -   -
-
   ASCII Ribbon Campaign. . . . . . . . . . . . accessBob
   .NO HTML/PDF/RTF/MIME in e-mail. . . . . . . accessys@smartnospam.net
   .NO MSWord docs in e-mail . . . .. . . . . . Access Systems,
engineers
   .NO attachments in e-mail, .*LINUX powered*. access is a civil right
*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
*#*#*#
THIS message and any attachments are CONFIDENTIAL and may be privileged.
They are intended ONLY for the individual or entity named

Received on Tuesday, 28 October 2008 14:59:08 UTC