A form should feel easy to use. The visitor sees a question, gives an answer, and needs to know what will happen next.
What You Need to Know
The date and phone controls may look different on phones and desktops but share the same HTML semantics.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/appointment" method="get">
<label for="appointment-date">Date</label>
<input id="appointment-date" name="date" type="date" required>
<label for="phone">Phone</label>
<input id="phone" name="phone" type="tel" inputmode="tel">
<button type="submit">Book</button>
</form>Let’s Read the Code
- <form>: The form groups controls and identifies where submitted data goes.
- <label>: The label tells people what the input is for. A matching for/id pair makes the label clickable.
- for: For connects a label or output with a control by ID.
- id: An id uniquely identifies an element on this page.
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) date, phone. 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
Compare the same form on a phone, tablet, and desktop at different text sizes.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- Do not design instructions that rely on one exact calendar widget appearance.
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.