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
Step=30 means 30-second increments for a time input. The value uses 24-hour time.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/times" method="get">
<label for="visit-time">Choose a time, including seconds</label>
<input id="visit-time" name="visit-time" type="time" step="30" value="14:30:00">
<button type="submit">Choose time</button>
</form>Let’s Read the Code
- step: Step sets the permitted increments for number or date/time-style inputs.
- <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.
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
Change step to 60 and test which minute or second values are accepted.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- The browser may show a different style of picker and may handle second-level controls differently.
Key Takeaways
- A control needs a clear label and, when submitted, a meaningful name and value.
- step: Step sets the permitted increments for number or date/time-style inputs.
- Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.