HTML Input Type Exercise: Build a Registration Form

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

A beginner-friendly registration form uses labels, meaningful autofill hints, and a POST request for credentials.

In this example: build a registration form with six different input types.

Try the Example

Take a look at the example. We’ll explain the important lines right below it.

<form action="/register" method="post">
    <label for="student-name">Your name</label>
    <input id="student-name" name="student-name" autocomplete="name" required>
    <label for="student-email">Email</label>
    <input id="student-email" name="email" type="email" autocomplete="email" required>
    <label for="password">New password</label>
    <input id="password" name="password" type="password" autocomplete="new-password" minlength="8" required>
    <button type="submit">Create account</button>
</form>

Let’s Read the Code

type: Type changes what sort of control or resource the browser uses.
<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.

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) student-name, email, password. 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

Add an optional nickname field and decide whether it should be required.

Common Beginner Mistakes

Copying the example without giving the fields a clear label and a usable name.
Do not treat minlength as a complete password policy; security checks happen on the server.

Key Takeaways

A control needs a clear label and, when submitted, a meaningful name and value.
type: Type changes what sort of control or resource the browser uses.
Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.