A webpage can display “9 October” while marking the date in its underlying HTML as 2026-10-09. The visible wording and the structured value serve different readers, and they should agree.
The HTML time element supports a datetime attribute for this structured representation. Its accepted formats include dates, times, and other defined forms; it is not a free-text note field.
Check both sides after an edit
Imagine an event moves from Friday to Saturday. An editor changes the visible sentence but leaves the old datetime value in place. A human reader and software inspecting the markup can now encounter conflicting dates.
In a practice page, keep the readable date, year, and structured date together during review. If a time is involved, decide whether the value includes a time-zone offset rather than assuming every local time identifies a unique instant.
The element does not itself send invitations or guarantee that every application will create a calendar entry. It supplies a defined way to mark the information.
For visitors checking an event, follow the organiser’s current details and explicit time-zone information. Structured markup is useful evidence about the page, but an inconsistency should be resolved rather than treated as proof that one representation must automatically be correct.
Editorial illustration from this site’s image library; not documentary evidence of the example or object discussed.