[web] keyboard navigation in Spaces overview

[exalate-issue-sync]

Description

Assumption: we have reusable components for keyboard navigation/selection etc.

User Stories

• As an organization who needs to comply with accessibility standards, navigation in the spaces overview needs to be possible without mouse.

Value

Acceptance Criteria

navigation

• via keyboard arrows up/down for moving up and down through the rows of the list (don't cycle to the top when reaching the end, just stay there. similarly, don't cycle to the end when reaching the top, just stay there).

selection

• via keyboard space bar: select / deselect the currently highlighted row
• via keyboard shift + arrows up/down: add a series of rows
• via keyboard cmd/ctrl + a: select all rows. if paginated: only the items of the current page. our selection model doesn't span across pages.
• via keyboard esc: deselect all rows
• via mouse left click anywhere on row (of course except for otherwise interactive elements, e.g. indicators, quick actions, file name): replace the selection with the click row (no other rows selected).
• via mouse holding cmd/ctrl + left click on a row: add/remove the clicked item to/from the current selection model (i.e. toggle selection state of the clicked row)
• via mouse holding shift + left click on a row: add the clicked row and the series of rows towards the most recently clicked row to the current selection model. (this will require to memorize the most recently clicked item). note that this doesn't allow to remove items from the selection model.

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

• Functional requirements
  [ ] functionality described in the user story works
  [ ] acceptance criteria are fulfilled
• Quality
  [ ] code review happened
  [ ] CI is green
  [ ] critical code received unit tests by the developer
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues