Currently there is a
keyboard component for navigation according to spatial and sequence navigation arrows.
There could be other navigation forms for the keyboard component‚ like zooming and panning.
The possible actions as well as the keys / combinations of keys for those actions should be determined.
When implemented each action category should be a separate handler that can be enabled / disabled like for the mouse component.
Potential handlers (initial suggestion):
KeyboardService should be created to ensure that only a single event listener is registered.