JS and Keyboard interaction

[woylie]

After completing the initial component set (#20) on the semantic level, the next step will be to add (keyboard) interaction where applicable. We'll mainly follow the APG patterns.

• [ ] tabs
  • [ ] left arrow: move focus to previous tab
  • [ ] right arrow: move focus to next tab
  • [ ] home: move focus to first tab
  • [ ] end: move focus to last tab
• [x] accordion
  • [x] toggle visibility on click
• [x] toggle button
  • [x] allow client-side state handling
• [x] disclosure button
  • [x] toggle visibility and aria-expanded
• [ ] tree (see https://www.w3.org/WAI/ARIA/apg/patterns/treeview/)
  • [ ] keyboard navigation, tabindex
  • [ ] select (single, multiple; leaf only or parent and leaf)
  • [ ] expand/collapse
  • [ ] lazy load children
• [ ] toolbar (see https://www.w3.org/WAI/ARIA/apg/patterns/toolbar/)
  • [ ] move focus with left/right arrow key
• [ ] carousel
  • [ ] Handle previous/next buttons
  • [ ] Handle pagination tabs
  • [ ] Auto rotation
  • [ ] Disable auto rotation when controls are used
  • [ ] Disable previous/next button on first/last item.
  • [ ] Focus management and keyboard support for pagination
• [ ] combobox
• [ ] menu, menubar, menubutton
• [ ] split pane
• [ ] action bar
• [ ] menu
• [ ] menu bar
• [ ] menu group
• [ ] menu item checkbox
• [ ] menu item radio group

[iampeter]

What are you plans with this @woylie? Also, do you have a roadmap where we can see your priorities for the whole project?

Thanks!

[woylie]

Hi @iampeter, current focus after the last refactoring is to add styles for the remaining components as used in the Demo storybook and to refine the component semantics, storybooks and configuration. After that, I'll start working on the JS for the components listed here. The primary goal for now is to move up all components to at least the refining level.