Estimated reading time : 3 min · Published
Describe the operation before the gesture
Separate reordering, moving between groups, copying and attaching a file. Their consequences differ. A document order needs to be expressible without depending on a pointer trajectory.
Choose controls such as Move up, Move down or Move to according to context. Name the item and explain boundaries: list start, prohibited group or denied movement. A long list may need destination selection instead of dozens of button presses.
Support keyboard and pointer without dragging
The W3C criterion on dragging movements calls for a pointer alternative without dragging outside its defined exceptions. Keyboard operation is a complementary check: a keyboard alternative alone does not solve pointer-gesture difficulty.
Visible buttons can support both uses when actions are simple. A file-selection button complements a drop area. Test the alternatives directly rather than starting with the gesture being avoided.
Align position, focus and saving
After movement, focus should remain on a useful control associated with the item and the new position should be understandable. Avoid disagreement between visual and reading order. At a boundary, explain the limit without sending focus somewhere unexpected.
Distinguish provisional and recorded order. Failed saving needs recovery or return to the previous state. Include another user changing the list. Local success must not imply service acceptance when the server rejected the update.
Fictional exercise: documents have identifiers A, B, C, D and E, in that order. Moving E up three times produces A, E, B, C, D. Compare identifiers before and after: nothing should disappear or be duplicated, even when two documents share a title. In a long list, a destination command can move E directly to second place without a lengthy series of repeated actions.
The W3C rearrangeable-list example demonstrates focus and announcements for a listbox; it does not require every card list to become that complex widget. List items and buttons named for their document may be enough. Then test three distinct states: local order, confirmed saved order and unknown outcome when the network response is lost. In the last case, read the service’s state before retrying or overwriting changes.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
| Stage | Observed order | Evidence or recovery |
|---|---|---|
| Initial state | A, B, C, D, E | Five distinct identifiers |
| Three Move up actions on E | A, E, B, C, D | E at position 2; consistent focus and announcement |
| Save confirmed | A, E, B, C, D | Same order after reloading |
| Network response lost | Local order visible; remote state unknown | Read saved order before another action |
Example: arrange a record’s documents
Educational example: five documents have Move up and Move down commands; Save confirms order. Testing moves the last into second position, checks focus, reloads after saving and simulates failure. Compare document identifiers rather than names, which may repeat.
Reference documents
- dragging movements · Source consulted
- Keyboard operation
- W3C WAI : Rearrangeable listbox example · Source consulted
Content updated on
