[IxDA Discuss] Required fields - one or the other

2009-10-14 Thread Brian Mila
Can anyone point to examples of forms that require one or the other of something? For instance, a contact form where either email -or- phone is required. The context is I have a web app that has search fields in which some combination of elements is needed. There could be as many as a dozen diff

Re: [IxDA Discuss] Required fields - one or the other

2009-10-14 Thread Eduardo Ortiz
Brian, As a simple answer, you can address it with a description for that section stating that either field is required and grouping them into logical areas (e.g. Sign-in information, Contact information, Personal details, etc). Here are some samples from Chris Messina's flickr design patterns st

Re: [IxDA Discuss] Required fields - one or the other

2009-10-14 Thread Mike Myles
I just came across this example the other day tracking an order (so it sticks in my mind)... https://www.zzounds.com/ordertrack/ It has some obvious issues: the inputs aren't horizontally aligned, and the "OR" text is barely readable in yellow. So I wouldn't call it a good example. I probably rem

Re: [IxDA Discuss] Required fields - one or the other

2009-10-14 Thread Sarah Weise
Here's a flawed example: http://www.regulations.gov/search/Regs/home.html#contactUs I don't like that the asterisk seems to be defined twice here. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=46747 ___

Re: [IxDA Discuss] Required fields - one or the other

2009-10-14 Thread marcus coghlan
Hi, I'd suggest a single input field with the label reading, "Email or phone". Use some 'hint' text to give examples of both or an explanation that either is ok. The coding of the field validation will increase in complexity a bit, but your user's wont care about that. Cheers. Marcus. . . . .

Re: [IxDA Discuss] Required fields - one or the other

2009-10-15 Thread Shivan Kannan
I personally would not want to fill a phone number field in any form, especially into a machine knowing that it will get stored in some database. So I won't know who can misuse it anytime. If the users for whom you design for think that giving a phone number there can serve them (such as confirmat