Surveys are a valid use case for radio buttons that come unchecked by default. You do not want to influence people by presenting them with a default (already c

Surveys are a valid use case for radio buttons that come unchecked by default. You do not want to influence people by presenting them with a default (already checked) choice. (You also typically want to randomize the order, at least when there is no inherent order to the options, e.g. when you are asking about frequency.) Surveys are also the place where that distinction between single choice (radio buttons) and multiple choice (checkboxes) becomes most apparent because surveys tend to liberally mix the two, so any additional UI signposts you can use to help people filling out the survey are helpful. (The typical recommendation for multiple choice is to still explicitly call out in text that multiple options can be checked.) Surveys sometimes also have the absolutely wild combined list with checkboxes and – typically as the fixed last option even if you randomize the rest of the options – a radio button (e.g. “None of the above”) that automatically unchecks all other options (and is unchecks itself if any other option is picked). I don’t think this exists in any spec anywhere but is the most normal thing in the world in most survey software. I‘m always very precise with whether I use checkboxes or radio buttons when designing surveys.