When is a numeric date actually ambiguous?

A date like 04/05/2025 is ambiguous because the first two numbers are both 12 or less, so they could be month-then-day (US) or day-then-month (most of the world). When either number exceeds 12, such as 25/05/2025, the order is forced and the date is unambiguous even if you do not know the locale.

Why does ISO 8601 solve this?

ISO 8601 writes dates as YYYY-MM-DD, biggest unit first, with a four-digit year that can never be confused for a day or month. It has a single global meaning, sorts correctly as text, and is recommended for any date that crosses locale boundaries or appears in data exports.

Is an ambiguous date an accessibility issue?

Yes, under cognitive accessibility. Forcing a reader to guess or compute which number is the month adds cognitive load and risks real errors, like booking the wrong day. Clear, unambiguous dates support WCAG's understandable principle and reduce mistakes for everyone.

Does the tool understand two-digit years?

It detects them and flags them as a separate ambiguity, because a value like 05 could be a day, a month, or a year depending on position and could be read as 1905 or 2005. The recommended fix is always a four-digit year in ISO order.

Is anything sent to a server?

No. Every date is parsed and analysed in your browser. Nothing you paste is uploaded, which is useful when checking dates inside otherwise confidential content.

Locale Date Format Accessibility Checker

The same numeric date can mean two different days depending on the reader’s locale. 04/05/2025 is April 5 to an American and 4 May to almost everyone else, and there is nothing in the string to disambiguate it. This checker scans your date strings, identifies which are genuinely ambiguous, and offers an unambiguous rewrite.

How it works

For each date string the tool extracts the numeric components and the separators, then reasons about whether the order can be determined:

Detect the shape. It recognises slash, dash, and dot-separated numeric dates, as well as dates with a spelled-out or three-letter month (5 Apr 2025), and ISO 8601 (2025-04-05).
Test for a forcing value. If any of the first two numeric fields is greater than 12, only one reading is possible (a 25 cannot be a month), so the date is unambiguous regardless of locale.
Flag genuine ambiguity. If both candidate fields are 12 or less, the date could be MM/DD or DD/MM, so the tool lists both interpretations (for example “April 5, 2025” versus “4 May 2025”).
Flag year ambiguity. A two-digit year is called out separately, because its century and even its role (day, month, or year) can be unclear.

Spelled-month and ISO dates are reported as already unambiguous. For everything flagged, the tool builds the ISO 8601 equivalent for at least one plausible reading and recommends it as the safe rewrite.

Example

04/05/2025 has both leading fields at or under 12, so it is ambiguous. The tool shows the two readings — 2025-04-05 (April 5, US MM/DD) and 2025-05-04 (4 May, DD/MM) — and recommends choosing the intended one and writing it in ISO form so no reader has to guess.

Tips and notes

Default to ISO 8601 (YYYY-MM-DD) for any machine-readable or cross-locale context; it is unambiguous and sorts correctly.
For human-facing prose, a spelled-out month (5 April 2025) is also unambiguous and often friendlier.
Always use a four-digit year; two-digit years reintroduce ambiguity and century guessing.
All parsing is local to your browser; nothing you paste leaves the page.