Skip to main content
Visual Arts & DesignUX Design Patterns32 lines

Audit Interface Microcopy Across Interaction States

Write accessible action, error, progress, empty, help, and confirmation text and verify it through one real interface flow.

Quick Summary10 lines
Trace one task from entry to completion. Record the user goal, actual effect of each action, objects involved, and which states a person can encounter. Include loading, no data, no matches, validation failure, unavailable service, and success where they can actually occur. Write a single line for each state describing what happened, what the person can do, and whether previously entered work remains available. Keep explanatory text only where it resolves a real decision.

## Key Points

- [WCAG error suggestion](https://www.w3.org/WAI/WCAG22/Understanding/error-suggestion.html)
- [WCAG status messages](https://www.w3.org/WAI/WCAG22/Understanding/status-messages.html)
- [GOV.UK design system error message](https://design-system.service.gov.uk/components/error-message/)
- [GOV.UK design system button](https://design-system.service.gov.uk/components/button/)
skilldb get ux-design-patterns-skills/interface-microcopy-auditFull skill: 32 lines
Paste into your CLAUDE.md or agent config

Audit Interface Microcopy Across Interaction States

Inventory what the interface already communicates

Trace one task from entry to completion. Record the user goal, actual effect of each action, objects involved, and which states a person can encounter. Include loading, no data, no matches, validation failure, unavailable service, and success where they can actually occur. Write a single line for each state describing what happened, what the person can do, and whether previously entered work remains available. Keep explanatory text only where it resolves a real decision.

Name each action with a verb and object where the object would otherwise be ambiguous. “Save billing address” communicates more than “Submit.” For irreversible actions, name the affected object and consequence in the confirmation, and choose a button label that matches the action. Distinguish removal from a list, revocation of access and permanent deletion. Keep any remaining reversible or cancel option easy to find.

Write for recovery and changing states

On a validation failure, explain the problem and specific correction in language the user can act on. Retain valid data and preserve entered values where safe. Attach a field-specific message and add a summary when errors can be far apart. A security-sensitive or unknown failure may need a general message plus a support path rather than exposing internal detail. Do not promise that a retry is safe if the prior action may have succeeded.

Distinguish first-use empty states from filtered-out results. Offer an appropriate action such as creating the first record or clearing a filter. Write onboarding in the order someone needs to act. Use help text for constraints and format, not as the sole label. A tooltip cannot carry information essential to completing a task unless that information is also accessible through an equivalent path. For progress, report actual status or meaningful milestones. Avoid made-up percentages.

Verify the copy in the actual flow

Check the interface by keyboard and with an appropriate screen reader. Confirm labels and messages identify the right controls, appear in logical order, and announce the outcome where a focus change is unnecessary. Test long localized text and narrow layout. Ask a reviewer what the button will do and how they would recover before giving the expected answer. Revise copy when their answer differs from actual behavior.

Record before and after text with the state and evidence used to accept it. Keep ownership with the feature so future changes to consequences or validation rules trigger a copy review.

References

Install this skill directly: skilldb add ux-design-patterns-skills

Get CLI access →