Think of filling out a sign-up page. Clear fields make the job simple; confusing fields make people leave.
What You Need to Know
JavaScript changes the age minimum from 13 to 18, so the browser now checks against the new rule.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form id="signup-form" action="/sign-up" method="post">
<label for="age">Age</label>
<input id="age" name="age" type="number" min="13" required>
<button type="submit">Continue</button>
</form>
<script>
const ageField = document.querySelector("#age");
ageField.min = "18";
console.log(ageField.checkValidity());
</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.
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.
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
Type 16, call checkValidity(), and explain why it returns false.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- Dynamic changes can affect focus and error handling; a server must enforce its own current rules.
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.