Imagine asking a friend for some information on a webpage. The field should explain exactly what you need.
What You Need to Know
The heading tells visitors which step they are on. Real multi-step forms need a server or script to preserve earlier answers.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/register/step-one" method="post">
<h2>Step 1 of 3: Your details</h2>
<p>Next: Choose a plan</p>
<label for="name">Your name</label>
<input id="name" name="name" required>
<button type="submit">Continue to step 2</button>
</form>Let’s Read the Code
- <form>: The form groups controls and identifies where submitted data goes.
- <h2>: A heading divides the page into understandable parts.
- 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) name. 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
Design step two and write down where step-one data will be stored.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- One HTML file does not automatically store or move between steps.
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.