You may have seen a short HTML attribute change how a field, image, or link behaves. This guide is about Input Type Values: Checkbox vs Radio. Checkboxes allow independent yes-or-no choices; radio buttons let someone choose one option from a named group.
The useful question is not simply “Which value should I memorize?” It is “What should people be able to do on this page?” First decide the goal, then choose an HTML value that matches it.
How the values work
| Value | Meaning |
|---|---|
checkbox | Each box is independent; unchecked boxes normally send nothing. |
radio | One selected option per group with the same name. |
A practical example
<fieldset>
<legend>Choose a contact method</legend>
<label><input type="radio" name="contact" value="email"> Email</label>
<label><input type="radio" name="contact" value="phone"> Phone</label>
</fieldset>
<label><input type="checkbox" name="newsletter" value="yes"> Get news</label>Understanding the code
Start by finding the attribute in the example. The HTML element tells the browser what kind of thing it is displaying; the attribute supplies an extra instruction or hint about that particular element. If you remove the attribute, the element usually still exists, but one part of its behavior may change.
A checked checkbox or radio sends its name and value. Unchecked boxes are normally absent from submitted data. Radio controls without a shared name will not act as one group.
If a file path or form action appears in the code, it is an example project path. Create the matching file or server endpoint before expecting the complete behavior to work. This distinction is important: HTML describes the page, but it does not automatically build a server or create missing resources.
When to use it
Use type only where its documented behavior helps someone complete a task. Ask whether the choice improves clarity, keyboard access, performance, or correct data collection. If an extra attribute has no clear purpose, leaving it out may be safer than relying on a poorly understood hint.
Try it yourself
Select a radio option, toggle the checkbox independently, and inspect what the form sends.
Save the code in a local HTML file, open it in a current browser, and inspect the relevant control or request. When the feature depends on a server, use a small local development server rather than guessing from the source alone.
Common Beginner Mistakes
- Giving radio buttons different name values and wondering why multiple options can stay selected.
- Assuming every browser provides identical controls or follows a hint in exactly the same way.
- Copying a demonstration without providing the files or server behavior it expects.
Key Takeaways
- Use a fieldset and legend to explain grouped options.
- Choose the value based on what the visitor needs to do, not only on how the source looks.
- Test the result in the browser, including keyboard access and submitted values where relevant.