You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Accessibility: dnd-kit drag instructions and announcements are English-only and expose internal IDs #18635
Payload version: 3.90.2 (Next.js 16.3.3, @payloadcms/db-postgres, admin language German)
In blocks and array fields, the keyboard drag instructions ("To pick up a draggable item, press the space bar…") and the live announcements ("Draggable item 6ac65a… was moved over droppable area…") are hard-coded English and use internal row IDs (WCAG 3.1.2, 4.1.3).
Steps to reproduce: set the admin language to German, focus a row's drag handle, press Space and an arrow key with a screen reader running.
Expected: pass translated accessibility.screenReaderInstructions and accessibility.announcements to DndContext, naming rows by their number/label (e.g. "Block 2 (Notice) moved to position 1").
We can only translate the static instructions via DOM patching; the announcements cannot be worked around.
How we found it: axe-core (tags wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa) via @axe-core/playwright plus keyboard-only tests of the admin. Our current workaround is a client provider (admin.components.providers) that patches the missing attributes into the DOM.
Happy to help with a PR if the direction is agreed.
Thanks for reporting. Leaving the same comment as I did here:
We’re currently working through an internal accessibility audit, and these reports overlap with findings we already have tracked and underway. I’ll keep these issues open until that work is complete so we can cross-reference your reports and make sure nothing was missed.
Activity
JessRynkar commentedon Oct 9, 2026
Thanks for reporting. Leaving the same comment as I did here:
We’re currently working through an internal accessibility audit, and these reports overlap with findings we already have tracked and underway. I’ll keep these issues open until that work is complete so we can cross-reference your reports and make sure nothing was missed.