Research Guides
Check Character Shortcuts Before They Interrupt Research
A research interface offers a convenient single-letter shortcut. While reading a source, someone accidentally presses that letter and the interface changes state. A feature intended to save effort has interrupted the task instead.
This worksheet reviews character-only shortcuts in an authorized interface or prototype. It does not describe a Colquhoun.shop shortcut feature or claim that keyboard and assistive-technology testing has been completed on this site.
1. Identify the shortcuts that need review
W3C's Character Key Shortcuts guidance covers shortcuts using only printable characters, including character sequences. It requires a way to turn them off, remap them to include a non-printable key, or restrict a component's shortcut to when that component has focus. The guidance addresses accidental activation, including problems for some speech-input users. W3C: Character Key Shortcuts
Inventory the commands actually implemented, not only those described in help text. Record the trigger, action and scope. A shortcut active everywhere deserves different investigation from character selection within a focused control.
2. Use a safe task and disposable content
Choose a bounded research activity, such as browsing a fictional source list. Avoid testing destructive or externally consequential commands against real records. If a shortcut can delete, publish or send, use an authorized test environment with harmless fixtures.
Record the browser, platform and any assistive technology used. A test with an ordinary keyboard is valuable, but it does not establish what a particular speech-input or screen-reader setup will do.
3. Check the context where activation occurs
In an invented source viewer, pressing “N” advances to the next source even when focus is outside the viewer. A reviewer records the unexpected transition and checks whether the user can disable or reconfigure that character-only command.
If the design instead limits the shortcut to a component's focus, test both conditions: while that component has focus and after focus moves elsewhere. A description saying “viewer shortcut” is not proof that its actual behavior is restricted to the viewer.
Also test ordinary text entry in the relevant fields. Record whether entering a query or note invokes an unrelated command. Keep the exact focus state with the result so the implementer can reproduce it.
4. Verify the alternative path still works
After an authorized change, disable the shortcut or apply the intended remapping and repeat the task. Confirm that an ordinary control still provides the action. Removing a problematic trigger should not leave the operation available only through an undocumented replacement.
Check the help text against the new behavior. A remapped command paired with an obsolete instruction creates a fresh usability problem. Document the tested key combination rather than assuming it behaves identically on every keyboard layout.
5. Copy this shortcut review card
- Command: trigger characters and resulting action.
- Scope: page-wide or limited to a named component.
- Focus: exact location before activation.
- User control: disable, remap or focus-based behavior.
- Alternative: ordinary control that performs the action.
- Environment: browser, platform and input method tested.
- Retest: observed result and unresolved combinations.
Preserve the before-and-after task record, especially when a change affects navigation or selection. Check whether the reader can resume the original research activity without losing their place.
The useful outcome is a documented shortcut behavior with a practical way to avoid accidental activation. It is not a blanket accessibility certification, and an untested input method should remain explicitly untested.