Choosing a date on a website: a calendar does not always help
Choose date entry for the task, explain errors and confirm appointments without inventing precision.
Article language: English

In this article
You want to enter a date from a report: 18 February 2021. The site opens a calendar at October 2026. Dozens of arrow clicks lie ahead unless you discover the hidden year selector. The calendar looks tidy. The journey into the past is less appealing.
The same control can be excellent for someone looking for a free Tuesday to visit a studio. The difference is the task: one person knows the answer; the other is still looking for it. Start choosing how to enter dates with that distinction, before designing a small window filled with thirty numbers.
Three questions that happen to look alike
In a fictional workshop-equipment service, a customer reports a faulty worktable. They give the day they noticed the problem, the approximate purchase period and a proposed collection appointment. A designer could use three identical fields: each must contain a date. Yet the answers arise in very different ways.
The customer remembers the day they noticed the problem or checks a note. They know the purchase period roughly: spring last year. The collection appointment must fit the service's availability and their own plans. A single tool could force them to search unnecessarily, invent precision and guess whether a clicked day is really available.
GOV.UK recommends its Date input component for dates people already know or can easily check. Its example separates day, month and year. This is a useful reference when copying information; the presence of a date in a form does not itself establish a need for a calendar.
Ask the process owner what precision is needed for the next decision. If an approximate period is enough to route the request to the right person, demanding an exact day creates falsely precise data. The first of January may simply mean “I had to choose something”. A report will retain an exact date while losing the fact that the customer guessed.
Prepare a separate example answer for each question. For the first: “18 February 2021”. For the second: “around spring 2025”. For the third: “Tuesday 3 November, collection between 10 and 12”. The third choice also contains a time window and an organisational commitment. It cannot honestly be reduced to a day number alone.
For an approximate period, design a separate answer, for example a year with an option to say the month is unknown. Do not internally store it as an exact first day of the month if someone will later read that value as fact. “Approximately” should remain visible in the summary, and the person handling the request should know the same limit of precision.
This distinction is part of designing a form with a clear purpose for its fields (in Polish). A label should explain which date is being requested. “Date” beside three similar controls leaves the customer to resolve a question the design should have answered.
A known date should be easy to type
When copying a date from a document, the short path from the written information to a correct value matters. You can design separate fields or one field with a clear hint. Test actual keyboard entry, pasting and correction in the middle of the value. Do not judge convenience solely by how quickly the interface author enters their own example.
Show the format hint before an error and keep it by the field during entry. “03/04/2026” does not mean the same day to everyone. If the site supports several languages, agree the order of parts, month names and an example for each. Acceptance of website language versions (in Polish) should include this small part of the interaction.
Once the value is accepted, you can show it in words, for example “4 March 2026”, if that is the agreed meaning of the input. The person can then notice a mistake before submission. Do not rearrange parts of the date while they type in a way that makes correcting a previous character difficult.
Distinguish a formatting error from an impossible date and a date not allowed by the service. “31 April” requires a corrected day. A valid date before the service began needs an explanation of the permitted range. A generic “invalid value” makes people experiment even though the system knows why it rejected the input.
After rejecting a date, preserve the entered value so one part can be corrected. If it is split into parts, the message should concern the whole question and guide the correction to the right part. Do not require the year to be selected again for a day error.
In a test, use an end-of-month date, correct only the month and check the result: changing March to April may leave an impossible thirty-first. The system should allow a deliberate correction rather than silently moving the request to another date.
Do not require a leading zero for a single-digit day merely for appearance if the solution can accept either form. Such details belong in design and acceptance. A designer sees even alignment; a customer sees another obstacle between them and the request they were ready to send.
When someone is looking for a day, show reasons to choose
When arranging collection, a customer needs to compare appointments. A calendar can show weekdays and distances between dates. With only a few choices, a short list may be simpler: Tuesday morning, Thursday afternoon, next Monday. Do not hide three answers inside a tool for browsing an entire year.
Marking a selected date should mean something different from indicating today. Also distinguish an unavailable day from one not yet checked. Grey alone cannot explain whether a slot is booked, outside the service range or waiting for availability data. If loading follows a month change, show that state rather than leaving old days visible as a current offer.

A day's availability and a reservation are separate stages. Choosing Tuesday may merely open the available hours; choosing an hour may still need confirmation. Group workshop registration (in Polish) adds the number of participants. A free slot for one person does not prove the whole group will fit.
Name the selected option precisely in the summary. “3 November, 10:00 to 12:00, collection at the studio on Słoneczna Street” can be checked. “3 November” alone leaves several arrangements invisible. If changing the date removes the selected time, show that consequence and allow it to be selected again.
When no days are available, identify a next route. Depending on the actual offer, a customer might see the first later appointment, change the service or ask the team. An empty calendar does not explain whether slots are full, the wrong period was selected or data temporarily failed to load. Those are three different messages and three different actions.
For services spanning time zones, state the location used for the time. Do not add that explanation to every local form out of habit. It should resolve real uncertainty, such as a remote meeting with someone abroad, not decorate the screen with terminology.
Viewing a day need not mean selecting it
Decide what happens when a calendar opens with no previous value. It could show the current month or the first period with availability. Those are different choices. Merely opening an empty control should not silently accept today's date if the person has confirmed nothing.
Treat cancellation similarly. Someone who opens the calendar, looks at the following month and presses “cancel” should recognise the earlier choice on return. If a choice takes effect immediately, show that rule in the interaction and name the closing button for its role. “Confirm” suggests the earlier indication can still be rejected.
This is the same distinction encountered with suggestions leading to selection of a specific record (in Polish). Seeing a suggestion, pointing to it by keyboard and finally accepting a value need not be one event. The design should define each moment.
W3C WAI's date-picker dialog example is illustrative material, not a production-ready component. Its authors say to test with assistive technologies before use. Copying its appearance does not prove your own control works with a keyboard and screen reader.
On a small screen, open the calendar after scrolling the form. Check whether the question and closing method remain visible. The on-screen keyboard, an error hint and an expanded control can together cover the result. An empty-field test alone will not reveal this state, so also prepare a form with retained answers and an error beside the date.
Without a mouse, test entering the control, moving between days, changing month, confirming and closing it. After leaving, the person should find the field with the result. Reaching the chosen square is not the end: they still need to know which value was accepted and where to correct it.
Time passes outside the screen too
“Tomorrow” is convenient at the moment of selection. Open the draft the next day and it means something else. If the customer chose a specific appointment, retain its actual date and show it on return. A relative label can supplement it but should not alone define the commitment.
A range needs another decision. When choosing several days, explain whether the last day is included in the service or marks the end and return. A highlighted calendar strip looks unambiguous until two parties arrive on the same morning for the same equipment. The summary can show start and end dates with their roles named.
If the start moves after the end, show the relationship between the values. You might ask for the end to be selected again or propose keeping the previous duration if that makes sense for the service. Do not hide an automatic change in the second field: the customer should notice it before confirming.
During a long process, availability can change between selection and form submission. The design needs a message for the actual result of the recheck. If the selected time is gone, retain the other data and ask for a new time. Do not send the person back to an empty form as though all their earlier work were only a warm-up.
If a service proposes an appointment automatically, also check the source and currency of its constraints. A convenient calendar cannot repair a suggestion that conflicts with working hours. Assessing the feasibility of AI calendar planning (in Polish) is a separate topic: a proposal must follow real rules and data.
Accept dates people will actually provide
Give the project a few short tasks: copy an old date, select the first available appointment, correct the month and return to a draft the following day. Rather than leading a person through buttons, give them a situation and expected outcome. You can then see whether they understand the question, not merely operate the demonstrated mechanism.
Also test the absence of an exact answer. A customer who remembers only the year needs a route appropriate to the required precision. If the process really requires a day, explain how to find it or get help. Do not judge the form only with examples whose data fit every field perfectly.
In Aeneia Design's website and interaction work, such cases help establish the scope before implementation. The result should be a choice of control together with behaviour after an error and on return. A calendar image without those decisions shows only the most photogenic moment of the process.
Finally, ask the person testing which appointment they just selected and what is supposed to happen then. They should be able to answer from the view they received. If they only remember clicking a blue Wednesday, the design needs another correction.








