Dynamic timestamps are spoken as their un-rendered value

(#3035) Bug Closed: Fixed accessibility desktop

Reproduction steps

Observed behaviour

It speaks the actual text value i.e. <t:1781557200:R> at <t:1781557200:F>

Build information

Canary Desktop 2026.606.140333, Web 2026.605.11941, Windows 11 10.0.26200 (x64), Electron 41.2.2, Chrome 146.0.7680.188, Node 24.14.1, Locale en-GB

Platform

Windows

Details

Expected behaviour It should speak the rendered value i.e. "in 9 hours at Monday, 15 June 2026..."
  1. Rex changed the status from Needs triage to Confirmed
  2. Tarek changed the status from Awaiting confirmation to Fixed
  1. The pull request fluxer#3896 mentions this post Merged

2 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Confirmed to Awaiting confirmation
This should be fixed in the current version (web 2026.1113.44451, desktop 2026.1113.52631). Could you check and tell us if it still happens?