Skip to content

Commit

Permalink
Add sections on native interactive elements and tab order.
Browse files Browse the repository at this point in the history
  • Loading branch information
cjcenizal committed Jun 8, 2017
1 parent 20cf042 commit cd2c862
Showing 1 changed file with 10 additions and 1 deletion.
11 changes: 10 additions & 1 deletion style_guides/html_style_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,4 +62,13 @@ described element can point to with the `aria-describedby` attribute. For exampl
<button aria-describedby="visualizationsTooltip">
Visualizations
</button>
```
```

### Use `button` and `a` to make interactive elements keyboard-accessible

If something is meant to be clickable, favor using a `button` or `a` tag before over the `kui-accessible-click` directive or `KuiKeyboardAccessible` component. These tools are useful as they augment non-clickable elements with `onkeypress` and `onkeyup` handlers, allowing non-clickable elements to become keyboard accessible. However, `button` and `a` tags provide this functionality natively.

### Use `tabindex` to make elements tabbable

When added to the tab order, elements become focusable via non-sticky-mode keyboard navigation.
To add an element to the tab order, you must add an `id` attribute as well as a `tabindex` attribute. If you don't know which number to use for the tab index, or if you simply want to add it to the general flow of the document, use `tabindex="0"`.

0 comments on commit cd2c862

Please sign in to comment.