Drag-to-reorder has no keyboard alternative in Grid, Replicator, Bard or structure trees
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- accessibility, frontend
Research direction
Start by reading resources/js/components/sortable/SortableList.vue and Sortable.js, then inspect ui/DragHandle.vue and the affected row, set, and tree components named in the issue. The issue proposes menu-based Move Up/Move Down actions as a first step, with keyboard drag handling and announcements as a further step. Done means reordering is possible without a pointer across the affected controls and keyboard users receive the expected feedback.
Written by the indexing model from the issue text.
Description
Bug description
Reordering in the CP is implemented entirely through @shopify/draggable pointer events. There is no keyboard handling anywhere in the sortable layer and no menu-based alternative, so reordering is mouse-only across the whole Control Panel.
Affected: Grid rows, Replicator sets, Bard sets, the page tree, the navigation tree, blueprint fields and tabs, Table rows, List items.
Verified:
grep -c 'keydown\|ArrowUp\|ArrowDown'in https://github.com/statamic/cms/blob/v6.31.0/resources/js/components/sortable/SortableList.vue -> 0- Same in https://github.com/statamic/cms/blob/v6.31.0/resources/js/components/sortable/Sortable.js -> 0
- The Grid row menu offers only Duplicate Row and Delete Row, no move actions: https://github.com/statamic/cms/blob/v6.31.0/resources/js/components/fieldtypes/grid/Row.vue#L18-L19
- The Bard set handle is not even focusable. It is a
<span>with amousedownlistener: https://github.com/statamic/cms/blob/v6.31.0/resources/js/components/fieldtypes/bard/Set.vue#L29
ui/DragHandle.vue is a real <button> with aria-label="Drag to reorder", so it announces itself as actionable, but pressing Space, Enter or arrow keys on it does nothing and emits nothing to any live region.
WCAG 2.1 SC 2.1.1 Keyboard (Level A). Under WCAG 2.2 this would also fail SC 2.5.7 Dragging Movements.
How to reproduce
composer create-project statamic/statamic- Add a Grid field with two or more rows to a blueprint, or a Replicator with two sets
- Open the entry and Tab to a row's drag handle
- Press Space, then ArrowDown, then Enter
Expected: the row moves. Actual: row order is unchanged and nothing is announced.
Suggested fix
Two steps, and the first is worth shipping on its own:
- Add Move Up / Move Down items to every row and set dropdown menu. Grid rows, Replicator sets, Bard sets, tree branches. This alone satisfies 2.1.1 and needs no new drag machinery.
- Wire a keyboard sensor onto
ui/DragHandle.vue(Space to lift, arrows to move, Enter to drop, Escape to cancel) with anaria-liveannouncement of the new position.
Also worth making the Bard set handle a <button> so it is at least reachable.
Environment
Environment
Laravel Version: 13.30.1
PHP Version: 8.4.23
Composer Version: 2.10.2
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file
Storage
public/storage: NOT LINKED
Statamic
Addons: 0
License Key: Not set
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 6.31.0 PRO
Installation
Fresh statamic/statamic site via CLI
Additional details
Found during a WCAG 2.1 AA audit of a vanilla composer create-project statamic/statamic install with no addons and no custom code. Tested with axe-core 4.x on Chromium 153 at 1440x1000, plus manual keyboard traversal. Source references point at v6.31.0.
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 647
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 113
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from statamic/cms
-
preferences
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[7.x] Reintroduce parser error for mixed pipe/shorthand modifier syntaxPossibly taken A pull request linked to this issue is open or already merged. Openantlers
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
navigations
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
matomo-org/device-detector#8405 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 4 days