Accessibility Request - Move files in File Explorer Sidebar for keyboard users #124775
Labels
accessibility
Keyboard, mouse, ARIA, vision, screen readers (non-specific) issues
file-explorer
Explorer widget issues
under-discussion
Issue is under discussion for relevance, priority, approach
Problem:
Currently to move files in and out of folders in side bar file explorer, a user must use a mouse to drag and drop files into desired folder. This poses an accessibility issue to keyboard users - If a user cannot use a mouse, a user cannot drag and drop files.
Solution:
When File Explorer Side Bar is focused, move files up or down with keyboard shortcuts option up or down or with Command Palette "Move File Up" "Move File Down". If Move file up is selected, it will move the file first to the next closest shown folder. If the folder is focused and collapsed, it will be expanded. However, folders that were expanded will collapse once they are no longer focused. As long as the option key is depressed, the file selected for the move will move into each folder directly underneath the containing folder name when the up or down arrow keys are depressed, ignore file name sort order until option key is no longer pressed, at which point the view will focus on the file that has been moved and its position with the folder's file list will be correctly sorted.
Notes
It would be easier to implement "Move File Next (Sibling) Folder", "Move File Previous (Sibling) Folder", "Move File Up Folder (Level)", "Move File Down Folder (Level)", however users are used to using option up or down to move lines in the code editor, and expecting the same / similar behavior in the file explorer would increase user adoption. Or perhaps an alternative solution could be-
"Move File Next (Sibling) Folder" - option down
"Move File Previous (Sibling) Folder" - option up
"Move File Down Folder (Level)" - option right
"Move File Up Folder (Level)" - option left
Something is better than the current status quo though which leaves keyboard users out
The text was updated successfully, but these errors were encountered: