Imagine asking a friend for some information on a webpage. The field should explain exactly what you need.
What You Need to Know
The first button asks the browser to check the required email; the second intentionally bypasses that check.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/send" method="post">
<label for="student-email">Email</label>
<input id="student-email" name="email" type="email" required>
<button type="submit">Send with browser validation</button>
<button type="submit" formnovalidate>Save draft without it</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) email. 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
Leave the email blank and compare both submit buttons.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- No browser validation means the server still has to check every submitted value.
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.