HTML Custom Validity Messages and Native Validation UI

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

Here is a small, realistic example focusing on custom validity.

Try the Example

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

<form id="club-form" action="/join" method="post">
    <label for="club-code">Club code</label>
    <input id="club-code" name="club-code" required>
    <button type="submit">Join</button>
</form>
<script>
    const clubCode = document.querySelector("#club-code");
    clubCode.addEventListener("input", () => {
        clubCode.setCustomValidity(clubCode.value === "OPEN" ? "" : "Enter OPEN to join.");
    });
</script>

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.
id: An id uniquely identifies an element on this page.
for: For connects a label or output with a control by ID.

What the example shows: The markup gives the browser a clear starting point for custom validity. Look at the labels, names, and values rather than only the visual appearance.

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.

How can you test it? Submit once with an empty field, once with a clearly invalid value, and once with a valid value. Watch which rule blocks submission. These are helpful browser checks; your server must validate all received data again.

Your Turn

Change one meaningful attribute, submit the form, and compare the result with the original.

Common Beginner Mistakes

Copying the example without giving the fields a clear label and a usable name.
These browser-side hints improve the experience, but the server must still validate submitted information.

Key Takeaways

Choose the HTML feature that explains this task clearly.
<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.