The undo window needs a visible countdown

What it is

Short undo does not last. The window is moving, and people must see how much time remains, or they will treat “I can still pull that back” as a stable ability and look for it after the bar is gone. A countdown turns a hidden limit into a planable difference. This entry is only about making remaining time visible. It is not about how batches undo, what order the stack uses, or how irreversibility is declared after expiry.

Why it happens

An unshown time bound is estimated with fuzzy words like “just now,” and the estimate is optimistic. Slips are often noticed near the end of the window: people look back at the result as the bar is about to die. Visible remainder turns “still in time” into a judgment, rather than depending on the control happening to still be on screen. A hidden few-second bar can end before the hand has moved from keyboard to pointing device; the window was never really offered. A countdown is also an attention tax, so it belongs on short windows whose miss would hurt, not on every lightweight undo.

Studying it

Compare, on the same short undo: vanishing with no cue, a static “undo available,” and a numeric or bar countdown.

Independent variables: whether remainder is shown, window duration, whether the countdown intensifies in the last seconds. Dependent variables: in-window restore rate, rate of believing undo is still possible after expiry, times the countdown itself interrupts the main task.

Do not make the countdown an audible alarm; that contaminates the measure with startle. Let the main task continue, and see whether people can still find the remaining seconds when they need them.

Where it stops holding

Day-scale trash retention is not this countdown; that is stating a period. Long windows (minutes) are less interruptive as an expiry clock than as ticking seconds. For accessibility, the countdown cannot be only a visually shrinking bar; remainder must be readable, and must not be spoken every second. If a new act refreshes the window, the countdown must follow, or the display is lying.

Applying it

• For undo shorter than a minute, show remaining time next to the result; digits or a bar are both fine if “how long is left” can be read.
• Intensify visibility in the last seconds; do not let the control vanish with no cue.
• Do not speak remaining seconds to a screen reader every second; one non-interruptive status before expiry is enough.
• Verify by having someone take a reversible act, then do something else, and ten seconds later ask “can I still reverse this, and how many seconds are left.” If remainder cannot be answered, the window is dark.

Related

• Within the group: H3.12.2 Batch undo must say whether it is all-or-nothing · H3.12.3 Multi-step undo follows last-in, first-out · H3.12.4 When the window closes, irreversibility must be explicit
• Adjacent: H3.04 Undo over confirm · H3.08 Soft delete and trash · E6.01 Toasts
• Search terms: undo timeout · countdown · undo window