HTML Exercise: Build a Validated Application Form

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 practice combines several kinds of constraints so you can test them one at a time.

In this example: build a small job application form.

Try the Example

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

<form action="/apply" method="post">
    <label for="applicant-email">Email</label>
    <input id="applicant-email" type="email" name="email" required>
    <label for="applicant-age">Age</label>
    <input id="applicant-age" name="age" type="number" min="13" max="120" required>
    <label for="reason">Why do you want to join?</label>
    <textarea id="reason" name="reason" minlength="20" required></textarea>
    <button type="submit">Submit application</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.

Look at the submitted value. The picker may display a friendly calendar or local clock, while form values use specific machine-readable formats. A local date and time does not automatically carry a time-zone identifier. Compare what you see with what your application receives.

Your Turn

Try a missing email, age 12, and a very short reason; see which check blocks the form.

Common Beginner Mistakes

Copying the example without giving the fields a clear label and a usable name.
The server still needs to repeat its own validation and show errors safely.

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.