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
Type=tel can offer a telephone-friendly keyboard but does not verify that a number is real.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/contact" method="post">
<label for="mobile-number">Mobile number</label>
<input id="mobile-number" name="phone" type="tel" autocomplete="tel">
<button type="submit">Save number</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.
Look at the submitted value. The picker may display a friendly calendar or local clock, while form values use specific machine-readable formats. A local date and time does not automatically carry a time-zone identifier. Compare what you see with what your application receives.
Your Turn
Try entering a plus-sign country code and consider how the server should normalize it.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- Different countries have different phone-number formats; avoid one rigid pattern for everyone.
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.