Agreed it does depend entirely on the situation and users.  By universally 
implemented I wasn't being flippant, I meant to be saying that things have 
moved on, just the modified model of radio set use doesn't work everywhere.  
For some reason undefined/unset radio button sets get overlooked by users 
trying to complete a form fast than some other methods.  Personally I try to 
reword/remodel to avoid uses of yes/no answers.  If unsure run some user 
audience testing.  If they hesitate longer at a yes/no then perhaps that is 
confusing for them.

>From a html/w3C standpoint I don't have an issue of course, my view was purely 
>user experience.

On 8 Jun 2010, at 02:38, Ben Buchanan wrote:

> On 7 June 2010 14:58, Steve Gibbings <> wrote:
> I have a problem with that.   Radio button sets should always have an option 
> selected, there is no undefined selection.  This makes sense when you 
> remember where the radio button metaphor came from. However seems that 
> doesn't get universally implemented.
> Technically correct, true. Would you recommend a checkbox instead, or some 
> other option?
> In practice I think the usage of radio buttons has shifted to accommodate 
> sets with no initial selection. In usability terms it's probably better than 
> a dropdown for a yes/no; and some people do have some issues with the implied 
> off state of checkboxes. Compare it with a paper form where you have two 
> boxes and you tick or cross an option - there's no preselection. I guess it 
> depends which paradigm is more likely to fit the scenario.
> cheers,
> Ben
> -- 
> --- <>
> --- The future has arrived; it's just not 
> --- evenly distributed. - William Gibson
> *******************************************************************
> List Guidelines:
> Unsubscribe:
> Help:
> *******************************************************************

List Guidelines:

Reply via email to