Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I'm working on an application form where a user must be 18 years or older to apply.

Should users be able to select years that would equate to them being younger than 18 or should I remove them from the select list (I know a free form input would be easier, but for this question assume it's a fixed list)?

As an aside, earlier in the app is a section of requirements ("You must be 18 years or older...") and right next to the field is text saying the same.

share|improve this question
add comment

1 Answer

up vote 9 down vote accepted

Yes, allowing them to select a value which proves they cannot use your service/product can make it clear that the user is not allowed to sign up; using a validation message you can make it immediately clear why they are now disqualified (or allow them to change the birth date if they entered it wrong).

If you disable disqualifying years, users are actually forced to pick a date that's valid; users that ignore the warnings may unintentionally sign up, against your Terms of Service, because they just used the default or lowest allowed age on the form. You're making it very easy to misrepresent one's age if you are underage, even if the user isn't doing so maliciously.

Note most forms asking "Are you over 18?" always have a "No" option, which usually boots the user to a "safe" part of the site or cancels the 18+ action.

Note there are some cases where you don't want to include disqualifying values; credit card forms almost never allow you to give a past year in the expiration date column. This greatly limits the amount of years you can pick from and makes sure you don't think you can use your expired card.

This is also a bit different from the age case; the users' age really is under 18/whatever, so it's valid input. Technically if you're asking for a valid credit card, past expiration dates are not valid, even if such a card really exists.

share|improve this answer
    
Thanks Ben! Is there ever a point where you would decide not to add an option that would be applicable to a small amount of users but would be an inconvenience for the majority? For example: If you target people with US addresses, would you have a question asking if they live in the US or just ask for their address? –  user4427 Dec 29 '11 at 20:33
2  
For a case like that I'd want to know how big of an issue it is for the minority and how big the minority; if 1% of users are not from the US (and only US users are allowed) and they thus fail to convert/complete their tasks I might leave a note "Applies to US residents only" or something. If I had a substantial number of users frustrated with the form finding it's US only I'd place the warning promenently but avoid adding steps to US users. Unless it's an accessibility issue or it affects lots of users/important users I would certainly try to avoid extra steps for the majority. –  Ben Brocka Dec 29 '11 at 22:21
    
Great. Thanks for the help! –  user4427 Dec 29 '11 at 22:56
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.