Skip to content
easeweb
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.

WCAG 2.2
SC 3.3.2A
Required by
Section 508 · EN 301 549 (EU)
Broken <label for="delivery">Delivery date</label>
The accessibility problem illustrated: Cognitive:Day first, or month first?
01

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

02

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?

BrokenA text field that reads month first and says nothing

Screen reader says:

(Tab to Delivery date)

A recreated demo. The broken version is intentionally inaccessible.

03

The fix

Say how to write the date before it is typed

Before
BrokenA text field that reads month first and says nothing
<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.
After

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
  1. 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.
  2. 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.

04

Verify the fix

4 checks, no mouse.

Test with: Screen reader, Keyboard, Zoom

0 of 4 checked

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.

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.

See the service