An input's id connects it to other parts of a page, while a label's for points to that exact id. Their strings must match exactly. We will keep the example small, so you can see how the fields work without building a whole application first.
What You Need to Know
Name controls the submitted data key and does not have to be the same as id, though matching names sometimes helps readability.
A form is like a question sheet. The label asks the question, the control holds the answer, and the name tells the receiving application what that answer is called.
Example: See It in Action
This example keeps the idea small. Copy it carefully, then follow the explanation instead of guessing what the browser will do.
This is a short HTML fragment. To try it as a webpage, put it inside the body element of a complete HTML document.
<form action="/register" method="post">
<label for="student-name">Student name</label>
<input id="student-name" name="student_name" required>
<button type="submit">Register</button>
</form>Let’s Understand the Example
- Input creates a form control. Its type decides whether people type text, choose a date, move a slider and more.
- Label tells people what a control is for. For connects the label to the control with the matching id.
- Id gives one element a unique name within the page, so a link, label, or script can point to it.
- For links a label to the input whose id matches, so clicking the label can focus the control.
- Action names the destination where the browser sends a form submission. A real server handler must exist there.
- Method controls how a form submits; GET makes values part of the URL, while POST sends them in the request body.
The browser can submit values with keys such as student_name. A control without a name normally contributes no entry. Whether the submission produces a result depends on the action URL and the server behind it.
What Should You See?
You should see controls for Student name. The example uses an input of type text and sends a POST request when submitted. If the action points to a missing server endpoint, the browser cannot complete the task.
Choose one field and predict its submitted name and value. Then change the value and check whether the browser accepts it. Do not assume that a working-looking form has a real server behind it.
Try It Yourself
- Rename the input id and update the label's for attribute to match.
- Save your changes, open or refresh the page, and compare the result with the original example.
- Tell a friend what your change did. If you are not sure, undo it, refresh the page, and compare.
Common Beginner Mistakes
- Writing for="student" when the input uses id="student-name".
- Client-side HTML validation is a helpful first check, not a security boundary. A real receiving application must validate the values again.
Key Takeaways
- An input's id connects it to other parts of a page, while a label's for points to that exact id.
- Input creates a form control. Its type decides whether people type text, choose a date, move a slider and more.
- Name controls the submitted data key and does not have to be the same as id, though matching names sometimes helps readability.