Picking the Right HTML Control for a Binary Question
At first glance, a yes/no question looks like a perfect job for a checkbox. A checkbox is inherently binary — on or off. But as Sara Soueidan points out in her analysis of this front-end pattern, the checkbox's implicit default state ("off") can quietly bias the answer. The real question is whether you want an explicit, deliberate response or are simply asking the user to confirm the obvious.
When the answer is expected to be heavily skewed toward one option, a checkbox lets the user either make a conscious statement or simply acknowledge the expected default without much friction. The trade-off: a checkbox can't easily be marked as required, since it's technically always in a valid state. Forcing an answer isn't possible without extra JavaScript validation.
Radio buttons, on the other hand, shine when you need a concrete and deliberate answer — especially when you don't provide a default selection. If you need an explicit "no," radio buttons are the better fit because the user must actively choose one of the two options to proceed.
That said, there are other paths. A range input can behave like a toggle if you cap its maximum value at 1. A <select> element can also force a choice and stays remarkably compact; modern styling options make it less clunky than it used to be. And if you really want to slow someone down and make them think, a text input that requires them to type the answer is always an option.
Still, the deciding factor often comes down to how you frame the interaction: confirm an expected state versus commit to an explicit choice.
