There is actually a fourth option, which is a pair of buttons, which is a good 
idea if both choices require an action, such as feeding on to a different form, 
or if this is the last action of the form.

For me, the main thing to think about is 'negative responses' - with a radio 
button you get one answer by default, which may not be the correct response - 
if people don't understand a question they will often ignore it, (a negative 
response) so in your case you should either go with one of the free-choice 
options (ie not a radio button) or else make sure that you word it in such a 
way that people need to change the default if they understand that they do 
_not_ want an interpreter.  If that wasn't clear, think about the difference 
between an opt-out tick-box, and an opt-in tick-box - on paper they are 
interchangeable, but legally speaking they are not.


From: [] On 
Behalf Of nedlud
Sent: 04 June 2010 03:30
To: wsg
Subject: [WSG] Yes/No structure?

I have a web form I'm building and there is a simple yes/no question in it.
I got to wondering what the best semantic  mark up for this is? Does anyone 
have any good UI/UX suggestions?

My three ideas were...

Two radio buttons for "yes" and "no"...
<p>Do you...?</p>
<label for="ans-yes">Yes</label><input type="radio" name="ans" id="ans-yes">
<label for="ans-no">No</label><input type="radio" name="ans" id="ans-no">

A single check box. A tick implies a "yes" answer while no tick implies "no"...
<p>Do you...?</p>
<input type="checkbox" name="ans" id="ans">

Or a selection list with a "yes" and a "no" answer...
<p>Do you...?</p>
<select name="ans" id="ans">
   <option value="yes">Yes</option>
   <option value="no">No</option>

Which is the preferred way? Or can you suggest a better way?


List Guidelines:

List Guidelines:

Reply via email to