Imagine asking a friend for some information on a webpage. The field should explain exactly what you need.
What You Need to Know
Radio buttons answer one-choice questions; checkboxes answer multiple-choice questions.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/survey" method="post">
<fieldset>
<legend>Which subject do you like most?</legend>
<label><input type="radio" name="favorite" value="art"> Art</label>
<label><input type="radio" name="favorite" value="science"> Science</label>
</fieldset>
<fieldset>
<legend>Which clubs might you join?</legend>
<label><input type="checkbox" name="club" value="music"> Music</label>
<label><input type="checkbox" name="club" value="robotics"> Robotics</label>
</fieldset>
<button type="submit">Submit survey</button>
</form>
Let’s Read the Code
- <form>: The form groups controls and identifies where submitted data goes.
- <fieldset>: The fieldset keeps related choices together.
- type: Type changes what sort of control or resource the browser uses.
- name: The name is the key used for the submitted value.
Read the named elements and attributes together. They explain how the browser connects this feature to the rest of the page.
What Happens in the Browser?
The HTML controls work in the browser, but saving an answer requires the example action path to be handled by a real server.
Where does the answer go? The example uses the submitted name(s) favorite, club. Those names help the receiving server identify each answer. A label is for people; a name attribute is for the form data; an ID connects elements in the page.
Your Turn
Add another favorite subject and another club; notice which changes require a matching name.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- Do not give unrelated radio button groups the same name.
Key Takeaways
- A control needs a clear label and, when submitted, a meaningful name and value.
- <form>: The form groups controls and identifies where submitted data goes.
- Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.