Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#15,390 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript
Área
accessibility, frontend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
PHP
Estrellas
4.9k
Forks
647
Merge medio
1 d 20 h
PR fusionados (30 d)
113

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de statamic/cms

Todos los issues de statamic/cms

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.