The <time> element should do something

Internet roasts the “time” tag: no tooltip, no magic

TLDR: The HTML “time” tag mostly just displays text; browsers don’t auto-tooltip or localize it, though some screen readers do. Commenters split between wanting built-in magic and saying “write a plugin,” with cynics declaring it too late—important because dates touch every app and user experience.

The web’s “time” tag—the little HTML label meant to mark dates—just got dragged across the timeline. The post claims it does, well, almost nothing, and the crowd came swinging. One user gasped, “It doesn’t even show a tooltip?” Meanwhile, dreamers want auto-local time like “4 days ago” or “in 2 hours,” no JavaScript (that’s the code language) required. Another gripe: even the date input box doesn’t automatically add your timezone. Cue the memes and the collective sigh: make it do SOMETHING.

Then the split: the DIY squad says, “Write a browser plugin and move on.” One dev insists they always use the tag and format it themselves with code, because it’s “free” and cleaner than a random span. Accessibility got a small win: screen readers like NVDA and Microsoft’s Narrator actually read the time out loud in human-friendly words—finally, a feature. But for search results, Google hints it looks at many signals, not just this tag, and docs push Schema.org data instead of plain HTML. So the vibe is part resignation, part rebellion: half the comments want built-in magic; the other half say keep it simple and let tools do the work. The finishing jab: maybe it’s been useless for so long it’s impossible to fix.

Key Points

  • The HTML <time> element semantically encodes timestamps but typically triggers no special browser behavior.
  • Screen readers NVDA and Narrator do read <time> timestamps in a human-readable format, offering accessibility benefits.
  • <time> appears on roughly 8% of page loads according to Chrome’s usage tracker.
  • Google’s documentation favors Schema.org datePublished/dateModified for date handling, with no explicit guidance to use <time>.
  • A 2010 CSS-Tricks quote from Bruce Lawson outlines potential advanced uses of dates that remain largely unrealized.

Hottest takes

"It's wild to me that it doesn't even generate a tooltip by default" — aezart
"Then write a browser plugin that does these things to the <time> element" — runarberg
"It has done nothing for so long that it may now be impossible to make it do something useful" — xanthor
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.