BETA This is a new service — your feedback will help us to improve it.

Back to patterns

Ask users for... Dates

The way you should ask users for dates depends on the types of date you’re asking for, for example:

  • memorable dates (for example, date of birth or marriage)
  • dates from documents or cards (for example, a passport or credit card)
  • approximate dates (like ‘June 1983’)
  • relative dates (like ‘4 days from today’)

Asking for memorable dates

To ask for memorable dates, like dates of birth, use text fields for users to complete.

Example
What is your date of birth? For example, 31 3 1980

Use 3 fields as it’ll be easier for you to validate each part rather than trying to review a single field.

Don’t automatically tab users between fields because this can clash with normal keyboard controls and confuse people.

Calendar controls (visual calendars which can be used to select dates) aren’t particularly useful for known dates and some users struggle to select date boxes.

Get the code for date input.

Triggering the iPhone numeric keyboard

To trigger the numeric keyboard on iPhones, add a pattern attribute to the input element like this: pattern="[0-9]*"

Asking for dates from documents and cards

If you ask for a date exactly as it’s shown on a passport, credit card or similar item, make the fields match the format of the original. This will make it easier for users to copy it across accurately.

Asking for approximate dates

If you don’t need an exact date and you’re asking for one that users might struggle to remember (for example ‘the date your benefits began’), make sure you allow them to enter an approximate date, like ‘June 1983’.

Asking for relative dates

You may need to ask for dates that are relative to today’s date or another date - this is common if a user is booking an appointment.

To do this you should let users enter or select relative dates like ‘tomorrow’ or ‘4 days later’. If the day of the week is important, show this as well.

Example

An accessible calendar control pattern needs developing.

Back to top