# Complete the journey with the keyboard alone

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Complete the journey with the keyboard alone

ID: MHC-D-RESEARCH-1100 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/complete-the-journey-with-the-keyboard-alone

Being able to reach a button is not the same as finishing the task.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A feature works with a mouse but keyboard access has not been checked.

### Avoid when

- Some path-dependent input has specific exceptions. This small check does not replace assistive-technology testing or a full accessibility evaluation.

### Explanation

Try a meaningful journey without the pointer: start, edit, submit, recover and leave. Observe focus and available actions at each step. A keyboard check should expose a blocked task, not merely count controls reached by Tab.

### Checklist

- Can you reach and operate every control needed for the task?
- Can you tell where focus is and follow a sensible order?
- Can you leave a dialog or recover from an error without using the mouse?

### Example

A recording dialog opens from the keyboard, but its close control cannot be reached. The journey fails despite a working Start button.

### Check

Can a fresh tester complete and exit the chosen task without pointer assistance?

### Limits

- Some path-dependent input has specific exceptions. This small check does not replace assistive-technology testing or a full accessibility evaluation.

### Evidence and sources

- supports: WCAG 2.1.1 requires functionality to be operable through a keyboard interface, with an exception for input that depends on the path of movement. — RS-EF6E9CB357047C5B. This card inspects ordinary interface tasks, not every path-dependent interaction or accessibility criterion. (Success criterion and intent.)
- RS-EF6E9CB357047C5B: Understanding Success Criterion 2.1.1: Keyboard — https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/keep-the-field-s-identity-after-the-user-starts-typing
