Truncated copy still needs a path to the full string

What it is

Ellipsis is compression at paint time, not deletion from the model. The source string is still there. If the interface offers no way to fetch it back — a hover, a tap-to-expand, a long-press copy, a detail view — compression has become deletion. Access to truncated content is not about where the cut landed. It is about whether the discarded span can be reclaimed after the cut.

Why it happens

Layout clips glyphs; the data layer usually still holds the full value. Reopening that one-way valve takes an interaction. Desktop muscle memory reaches for a hover bubble, but touch has no hover, and a title attribute is often unreachable from a phone or a keyboard. If “see all” means leaving the list for a detail screen three steps away, the comparison that needed the missing characters is already broken — people want those characters in situ, among neighbours, not as a dossier on one row. A marquee rolls the full string past, which is a kind of recovery, but it cannot pause, cannot be selected, and will not stop on the distinguishing span when the user needs it. Truncation without a reclaim path is the system deciding the user is not entitled to the complete fact.

Where it stops holding

When a title is being used as texture (a half-sentence on a poster, a brand name in a background), reclaim has no task value. Legal copy, dosages, and the email an account is bound to are not optional to recover; a missing fragment is a wrong action waiting to happen. Virtualized lists that mount only the visible substring make the detail view a fake door — “more” still shows the stub. The reclaim path has to return the source string, not another clipped copy.

Applying it

• Register a reclaim action for every field that can show an ellipsis: expand, bubble, copy, or detail — at least one that can finish inside the current task.
• Turn the pointer hover off and walk that action with finger and keyboard. If it fails, or if it forces the user out of a side-by-side scan, it does not count for comparison work.
• An expanded row must collapse again, otherwise reading one item destroys the twelve-item scan.

Related

• Same group: F4.10.1 Where a string is cut decides whether the leftover is still usable · F4.10.2 Middle ellipsis keeps the distinctive start and end · F4.10.4 Decision-critical text such as prices and warnings must not be truncated · F4.10.5 Assistive technology must still receive the untruncated string · F4.10.6 CJK characters pack more meaning per glyph, so the same character budget loses more · F4.10.7 Multiline clamp must recast with type size, not a fixed pixel height
• Nearby: F2.16 Extreme content and overflow · E4.02 List items
• Search terms: access to truncated content · expand truncated text · overflow affordance