feat: add keyboard accessibility to drag and drop components#221
Merged
RUKAYAT-CODER merged 1 commit intoApr 26, 2026
Merged
Conversation
|
@Babigdk Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds keyboard accessibility support to the drag-and-drop components built with
react-dnd.Since the project does not use
dnd-kit, accessibility was implemented by layering keyboard interactions on top of the existing drag system instead of introducing a new library.Key improvements:
tabIndexrole,aria-grabbed)These changes improve usability for keyboard-only users while preserving existing mouse drag behavior.
Related Issue
Closes #192
Type of change
Screenshots / Recording (if UI)
Optional – recommend adding a short recording showing:
Testing
Tested manually with keyboard interactions:
Commands run:
npm run type-checknpm run lintnpm run testnpm run buildQuality gate checklist