Pattern model
Parts that must work together
Selection modelSelected countAction barScope confirmationProgressPartial result and recovery
Why this matters
A pattern is not a screenshot. It is a reusable decision model that must preserve intent, state, recovery, and accessibility as layouts change.
Decision framework
Questions to answer before choosing UI
What is selected?
Distinguish the visible page from the complete filtered set and preserve selection when navigation or filtering changes.
How consequential is the action?
Match confirmation to reversibility, item count, collaboration impact, and data loss.
Can results partially fail?
Report success and failure per item, preserve failed selections, and offer a retry or exportable error list.
Cross-system baseline
End-to-end accessibility
- Associate selection controls with row names
- Announce selected count
- Keep the action bar reachable in logical order
- Return focus after completion or cancellation
Common mistakes
Failure patterns to test
01
Selecting all without naming the scope
02
Losing selection across pages
03
Showing one generic failure
04
Putting destructive bulk actions first