I'm a die-hard keyboard user. My browser does not have any chrome. There is no address bar, no menu, no back buttons. My operating system and desktop environment does not have any chrome. There is no task bar and no start menu. The top left pixel on this monitor right now is from the canvas of this site, as is the bottom right. No my browser is not in "full screen" mode, that's just the way every I have the UI configured (Firefox + [Tridactyl](https://github.com/tridactyl/tridactyl) + disable all normal Firefox UI components).

Whenever possible, I _don't_ use the mouse. I do have one, but some days I come to the office and discover about lunch time the battery is dead. It's possible to go for hours withouth touching it. In general I find it's much more convinient for me to stay on the keyboard when possible. Most browser interactions can be mapped to keybindings, and I can navigate most sites withouth the mouse.

As far as I'm concerned one of the coolest things SE ever did was finally integrating the keybindings userscript that floated around for years into the site by default and enabled a profile option to use it across all sites. Unfortunately the keybindings were not very comprehensive, but they did help with the basics.

**I would propose** being careful during even this early phase of development to expose as many settings and user actions as possible through stable documented function calls so that users can map their own keybindings to them. A default set of keybindings might be included in the site out of the box, but it should be easy for a user to come along and rebind the actions to anything they wanat.

I'll be looking into what exactly would be entailed in doing this well, but it would be nice to keep in mind as UI features are conceived.