E-mail List Archives
Thread: RE: e-mail addresses and proper forms labelling of their constituent parts
Number of posts in this thread: 1 (In chronological order)
From: Karl Groves
Date: Mon, Sep 15 2003 1:26PM
Subject: RE: e-mail addresses and proper forms labelling of their constituent parts
No previous message | No next message
How is the form being processed?
I recommend against using two form elements for this.
Don't make the user do the work when the script can do it for you.
Since you're validating the address, have the script separate the address via regular expressions and convert it into two variables (separated by the @).
Karl L. Groves
Opinions expressed in this e-mail represent only myself and are not in any way to be taken as the words or opinions of my employer.
> -----Original Message-----
> From: Lori K. Brown [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Monday, September 15, 2003 3:13 PM
> To: = EMAIL ADDRESS REMOVED =
> Subject: e-mail addresses and proper forms labelling of their
> constituent parts
>
>
> Dear list:
>
> I am reviewing a form for my company's product. In it, we have a form
> that asks for an e-mail address. In this instance, the e-mail
> address is
> not for a particular person, but is for setting up a pop client that
> posts messages received by that account into a web-based
> piece of software.
>
> Right now, the form requests the pop client address in two different
> fields, with an @ sign in between them. This is our way of doing a
> little brute force data validation, as we then concatenate the two
> fields w/ the @ sign in between to build the e-mail address.
>
> I have several usability / accessibility questions about this
> problem,
> and this technique.
>
> 1) This is another one of those annoying cases where one data
> element --
> an e-mail address -- is built from two form elements (and the @ in
> between). Is there a proper way to label this so as not to be
> confusing
> for screen reader users? In particular, are there specific
> names for the
> front part of an e-mail address and the back part that are widely and
> correctly understood?
>
> 2) Would an example, like ' = EMAIL ADDRESS REMOVED = ', be helpful?
>
> 3) Is there a best-practice solution to this problem? In
> particular, is
> it preferred to just let users type their own complete
> addresses without
> engaging in this kind of parsing operation?
>
> Thanks in advance for any assistance.
>
> Lori K. Brown
>
>
>
>
> ----
> To subscribe, unsubscribe, suspend, or view list archives,
> visit http://www.webaim.org/discussion/
>
>
----
To subscribe, unsubscribe, suspend, or view list archives,
visit http://www.webaim.org/discussion/