Search topics
Date fields that don't say which format to type
A delivery date field reads every date month first and says so nowhere, so 12/11/2026, typed day first, is booked for 11 December without a warning.
<label for="delivery">Delivery date</label> The problem
People who write dates another way can't tell how to type one here, and a date typed day first is booked a month late without a word
A shop's checkout asks for a delivery date, in a text field labelled "Delivery date", with nothing under it. The field came with a date library, left at its default, and the shop's script reads every date as month, day, year. Someone who writes the day first, as most of Europe does, wants Thursday 12 November and types 12/11/2026. The script takes 12 as the month and 11 as the day, and the order goes through for Friday 11 December, a month late. Both readings are real dates, so there is no error and no warning; the only sign is the date in the order summary, if the person reads it closely.
Someone else writes the year first, as the ISO format and much of East Asia do, and types 2026/11/12. The script can't read it, and only now says how it wanted the date: "Enter the date as MM/DD/YYYY." A third person types 12 Nov 2026 and gets the same message. Each of them learns the format by failing first, and the person whose date was misread never learns it at all.
Success Criterion 3.3.2 Labels or Instructions asks for labels or instructions when content needs input from the person, and its Understanding document says these may give the format the data must be in. One of its examples is a single date field with text that says the expected format. Technique G89 does this for a date field in its label: "Date (dd-mm-yyyy)". The test it gives is short: find each field that takes data only in a given format, and check that the field says what that format is.
A date field that takes figures is such a field. Different countries write the day, the month and the year in different orders, and when the day and the month are both 12 or under, 12/11/2026 is a real date in either order. The browser can't help: a text input takes any text, and what the text means is decided by the page's script, here a line that splits it on the slashes and takes the first number as the month. "Delivery date" names the field, but nothing on the page says which order that script reads, and the only place the format appears is the error, after a try has already failed.
Most of the world writes the day first, the United States writes the month first, and the ISO standard and much of East Asia write the year first, so any numeric date with both the day and the month at 12 or under means two different days to two groups of people. A shop that sells across borders has all of them typing into one field.
1 of 10 groups affected
- No vision (not affected)
- Low vision (not affected)
- Colour vision (not affected)
- No hearing (not affected)
- Hard of hearing (not affected)
- No speech (not affected)
- Motor (not affected)
- Reach, strength (not affected)
- Cognitive (affected)
- Seizures (not affected)
- Limited language, cognitive and learning abilities People who find dates or numbers hard to work out, or who write dates in another order, can't tell which order the field wants, and a date read month first moves the delivery a month on with nothing to show it happened.
A scanner such as axe finds a text field with a label and passes it: no rule can tell what order a script reads, or whether a label says enough about the format. The misread date is a valid date, so the shop's own checks pass it too. The audit raises a review lead for a text field whose label, name or autocomplete says it takes a date when no format appears in its label, its description or the text beside it, and says when the only format is a placeholder. A person still has to read the field and type a date to know what it does. Date picker libraries make the mistake easy: jQuery UI's datepicker reads mm/dd/yy by default, bootstrap-datepicker mm/dd/yyyy and react-datepicker MM/dd/yyyy, and none of them writes the format on the page unless the developer does. Date picker issue trackers and forums, for Angular Material and Vue date pickers among others, hold reports of typed dates with the day and month swapped. AI assistants asked for a date field can keep the library's default and leave the label as it is, since nothing in the code looks wrong.
Try it
Book the delivery for 12 November 2026, typing the date the way you usually write it
Type 12/11/2026, day first, and press Continue: see which day the shop books. Change it and try 2026/11/12, year first. Then apply a fix, and read the field before you type.
Broken Can you fix this?
Screen reader says:
(Tab to Delivery date)
The fix
Say how to write the date before it is typed
<form id="checkout"> <label for="delivery">Delivery date</label> <input id="delivery" name="delivery" type="text" aria-describedby="delivery-error"> <p id="delivery-error" class="error"></p> <button type="submit">Continue</button></form>What is wrong3 points
- The label says "Delivery date" and nothing about the order, and nothing else on the page does either.
- The script reads 12/11/2026 as 11 December, and since that is a real date, nothing says it read anything other than what was meant.
- 2026/11/12 and 12 Nov 2026 are refused, and the format appears only then, in the error.
The format in the label
<form id="checkout"> <label for="delivery">Delivery date (month/day/year)</label> <input id="delivery" name="delivery" type="text" aria-describedby="delivery-error"> <p id="delivery-error" class="error"></p> <button type="submit">Continue</button></form>How it is fixed2 steps
- Add the order to the label, in words: "(month/day/year)". It is on screen before anything is typed, and a screen reader reads it as part of the field's name every time it reaches the field.
- Leave the script as it is: it already reads the order the label now states.
This fixes the Before and passes 3.3.2, as G89 does. Words read better aloud than letters, so write "month/day/year" rather than "MM/DD/YYYY"; and keep the format short, since it is part of the name a voice control user says to reach the field.
All five pass 3.3.2. The format in the label is the smallest change, one line of markup, and it is read every time the field is reached; it makes the name longer. A hint with an example is nearly as small, and the example settles the order for anyone unsure what "month, day, year" means. Separate boxes take the order off the person entirely and suit a date people know without a calendar, such as a date of birth; they take more space and their own validation. A native date input needs no format text and no parsing, if the browser's look for the field and its calendar is acceptable. Reading several forms costs the most code and suits a shop whose customers come from many countries; the date said back in words is worth adding to any of the other typed fields as well.
Give the format in text that stays on screen. A placeholder such as DD/MM/YYYY is gone once the first figure is typed, and is often too faint to read; see form fields with missing or mismatched labels. An example works best when its day is over 12 and it is a date that makes sense for the question, as GOV.UK advises.
Choose the order for your readers. A shop that sells mostly in one country can state that country's order; a shop that sells across borders is the one that most needs the stated order, or the read-back, or separate boxes. Whatever the order, keep the label, the hint, the error message and the script in step: a hint that says day first above a script that reads month first is worse than no hint.
Read forgivingly within the stated order: a date with or without leading zeros, and with dashes, dots or spaces instead of slashes, can only mean what it says. GOV.UK's date input also accepts month names typed in its boxes. See convert what people type instead of rejecting it. A date mask that fills in slashes as people type is a different failure, covered in input masks that change a typed or pasted number.
When the date can't be read, the error should say what to do, as the ones above do. Where errors go and how they are announced is covered in form errors that don't say how to fix them.
Verify the fix
4 checks, no mouse.
Test with: Screen reader, Keyboard, Zoom
Record the OS, browser and assistive-technology versions, the build, the date, and the actual result of each step. Repeat after the shared date field component changes.
How screen readers handle role="status" and aria-describedby
Limits
This guide is about saying how to write a single typed date. Choosing a date from a calendar with a keyboard, and hearing its days with a screen reader, is in date pickers that can't be typed in or used by keyboard. It doesn't cover date ranges, times and time zones, or calendars other than the Gregorian one. The snippets leave out checking that the shop delivers on that day. Test the complete journey, with your real dates and the orders your customers write them in, in the browsers and assistive technology you support.
This is a recreated teaching example, not a finding about a named client. The code is a starting pattern: test it in your own product. No completed assistive-technology test is claimed here.
References
- WCAG Understanding: labels-or-instructions (opens in a new tab)
- WCAG Technique G89 (opens in a new tab)
- WCAG Technique ARIA1 (opens in a new tab)
- developer.mozilla.org: date (opens in a new tab)
- design-system.service.gov.uk: date-input (opens in a new tab)
- designsystem.digital.gov: date-picker (opens in a new tab)
EaseWeb service
Fixed it? Keep it from coming back.
I turn guides like this one into rules your coding agents follow and checks your CI runs. Then I retest by hand with a keyboard and screen readers, periodically.