Imagine asking a friend for some information on a webpage. The field should explain exactly what you need.
What You Need to Know
Type=email catches some obvious mistakes such as missing @ symbols, but it does not prove that an address belongs to someone.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/subscribe" method="post">
<label for="subscriber-email">Email address</label>
<input id="subscriber-email" name="email" type="email" required>
<button type="submit">Subscribe</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.
How can you test it? Submit once with an empty field, once with a clearly invalid value, and once with a valid value. Watch which rule blocks submission. These are helpful browser checks; your server must validate all received data again.
Your Turn
Compare [email protected], a blank value, and an address without an @ symbol.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- Real account systems may need confirmation messages and additional server checks.
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.