HTML Appointment Booking Form with Date and Time Inputs

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 example puts a readable label next to each control and gives each submitted value a name.

Try the Example

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

<form action="/submit-appointment" method="post">
    <label for="appointment-date">Date</label>
    <input id="appointment-date" name="appointment-date" type="date" required>
    <label for="appointment-time">Time</label>
    <input id="appointment-time" name="appointment-time" type="time" required>
    <button type="submit">Continue</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.

What the example shows: A browser can display and check the fields, but an address such as /submit-contact needs server code to actually save a response.

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 one label and one name attribute. Which change affects what people see, and which changes the name sent to the server?

Common Beginner Mistakes

Copying the example without giving the fields a clear label and a usable name.
If this page is opened as a local file, it will display, but its submit destination is only an example until you build a server endpoint.

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.