copy · ux
Microcopy for errors without sounding like a machine
2026-04-27 · Hana Sorell
Error strings often inherit developer wording because copywriters never see the branch. Pull those strings into a shared sheet before launch.
We recommend leading with the outcome (We could not save your draft) before the reason (Network blip). Follow with a single action (Try again) instead of three equal buttons.
Accessibility-wise, tie aria-live regions to the same copy so assistive tech users hear the same calm explanation sighted users read.
AccessLattice workshops include a fifteen-minute table read where support agents read errors aloud. Awkward phrasing shows up immediately.