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
After the server reports an error, the form can be re-rendered with safe, escaped previous values so the visitor does not have to start over.
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="visitor-email">Email</label>
<input id="visitor-email" name="email" type="email" value="[email protected]" required>
<label for="message">Message</label>
<textarea id="message" name="message" required>Could you help me with HTML?</textarea>
<button type="submit">Send again</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
Imagine the server rejects only the email: which other answers should the form keep?
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- Never insert raw user input into HTML without appropriate output escaping.
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.