Imagine asking a friend for some information on a webpage. The field should explain exactly what you need.
What You Need to Know
A week value uses the year-Wweek format and may not match a simple calendar month.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/planning" method="get">
<label for="work-week">Choose an ISO week</label>
<input id="work-week" type="week" name="work-week" min="2026-W01" max="2026-W52">
<button type="submit">Save week</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
Choose week 1 and explain how ISO week dates differ from ordinary month dates.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- ISO weeks can cross year boundaries; avoid treating the week number as a month.
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.