Think of filling out a sign-up page. Clear fields make the job simple; confusing fields make people leave.
What You Need to Know
This example puts a readable label next to each control and gives each submitted value a name.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/submit-billing" method="post">
<label for="billing-address">Billing address</label>
<input id="billing-address" name="billing-address" type="text" autocomplete="billing street-address" required>
<button type="submit">Continue</button>
</form>Let’s Read the Code
- autocomplete: Autocomplete tells browser autofill what kind of information belongs here.
- <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.
What the example shows: A browser can display and check the fields, but an address such as /submit-contact needs server code to actually save a response.
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.
What about privacy? A password input hides characters from people looking over your shoulder, but it is not encryption. A real application uses HTTPS, secure server logic, and careful handling of any private information. Do not put passwords into GET query strings.
Your Turn
Change one label and one name attribute. Which change affects what people see, and which changes the name sent to the server?
Common Beginner Mistakes
- Using an autocomplete token as validation instead of a hint for browser autofill.
- Never treat a form value as trusted simply because it came from a field on your own page.
Key Takeaways
- A control needs a clear label and, when submitted, a meaningful name and value.
- autocomplete: Autocomplete tells browser autofill what kind of information belongs here.
- Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.