Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Drag-to-reorder has no keyboard alternative in Grid, Replicator, Bard or structure trees

Aperta
  • Qualcosa non va?
#15,390 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
accessibility, frontend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

accessibility fieldtypes
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:

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
  1. composer create-project statamic/statamic
  2. Add a Grid field with two or more rows to a blueprint, or a Replicator with two sets
  3. Open the entry and Tab to a row's drag handle
  4. 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:

  1. 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.
  2. Wire a keyboard sensor onto ui/DragHandle.vue (Space to lift, arrows to move, Enter to drop, Escape to cancel) with an aria-live announcement 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.

Lingua principale
PHP
Stelle
4.9k
Fork
647
Merge medio
1g 7h
PR unite (30g)
103

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di statamic/cms

Tutte le issue di statamic/cms

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.