Display help when pressing '?'

[hacdias]

Current shortcuts:

• ESC - Unselect everything.
• F2 - Rename selected.
• Del - Delete selected.
• Enter or Meta+Arrow Right - Open selected.
• Arrow up/down - Focus files.

/cc @lidel

[olizilla]

What help are you thinking of here? A list of keyboard commands?

[lidel]

@olizilla Yes, supported keyboard shortcuts.
My idea was to do something similar to pressing ? in Gmail, but less ugly ✨
(we could also add there a note about IPFS Docs at http://docs.ipfs.io)

[lidel]

I wonder if we could support moving to menu navigation via left/right arrows.
Right now if I want to open Files screen I need to use mouse, would be super useful to switch between screens with keyboard alone.

cc @terichadbourne https://github.com/protocol/design/issues/145

[terichadbourne]

I love the focus on keyboard users here.

In general, I presume that sticking to the common methods they use (for example, tab to focus on the next thing on the site and enter to select it) will be better than creating new site-specific shortcuts, but I'm not clear on what part of the site interaction you're referring to, so feel free to ignore this comment if it's irrelevant.

[lidel]

To illustrate:

• What works right now is the pink arrow on the right – user can navigate between files using up/down arrows.

• What we are missing is a way to switch to and from left menu (greens) and move between screens (left pink arrow).

  • I tested pressing Tab and Tab+Shift and it seems to work, but it acts as a global iterator and gets confused on some screens such as Files (where selection disappears the moment it enters the file list). Perhaps all we need to do here is to polish use of Tab, to ensure it works everywhere?

[ericronne]

Do we have any accessibility gurus? I'm not one, but i know that tabbing is core to the way keyboard-based users get around, so that's also a consideration.

[terichadbourne]

My accessibility training is minimal, but what I would have expected on a page like this with left-side nav is that when you tabbed from the top of the page you would first cycle through all of the nav options (where then clicking or hitting enter would change the content on the right) and then cycle through all of the clickable content on the right side of the page (main content). I don't think it's necessary to build a special command to tab from left to right. Just think of nav as top in the cycling, and make sure it's in nav tags so people with various accessibility tools can skip it or access it in the ways they're used to.

[jessicaschilling]

Closing in favor of accessibility master issue ipfs/ipfs-gui#28 -- this discussion has been linked to from there so we avoid it getting lost to history.