If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.
Checklist – System Framework
Coding Standards
| Test | Priority | Automated test? |
|---|---|---|
| Does the focus order follow the reading order? | High | None |
| Does the page avoid using tabindex values higher than 0? | High | Pending |
Checklist – Components
Accordion
| Test | Priority | Automated test? |
|---|---|---|
| When an accordion is opened via keyboard does the focus move to the next item? | High | None |
| When an accordion is closed via keyboard does the focus stay on that item? | High | None |
Dialogs
| Test | Priority | Automated test? |
|---|---|---|
| Is the focus somewhere reasonable on dialog load? | High | None |
| Does the Close/Cancel/[Negative answer] button return focus to the expected location? | High | None |
| Am I confined to modal dialogs using a keyboard until I dismiss it? | High | None |
Drag-and-drop components
| Test | Priority | Automated test? |
|---|---|---|
| Can content be reordered by mouse, keyboard, voice, and touch? | Medium | None |
Information Bubbles
| Test | Priority | Automated test? |
|---|---|---|
| If an interaction reveals hidden content does the focus move to that content? | High | None |
Tabsets
| Test | Priority | Automated test? |
|---|---|---|
| When a tab is opened via keyboard does the focus move to the next item? | High | None |