Keyboard setup deserves a complete work test. An employee may be able to type a document but still struggle to reach a toolbar, select a date, or leave a dialog. Those are different problems, and they need different support notes.
Use this procedure alongside the office workstation accessibility plan. Start with the person's preferred way of working and existing tools. The goal is to verify a useful route through everyday tasks without changing an established setup unnecessarily.
Choose a small, representative workflow
Ask the employee to name a task they perform frequently and a step that interrupts it. Use harmless sample material: a test document, a training form, or a demonstration record that cannot trigger a customer message or transaction.
Write down the application, operating-system version, keyboard layout, and any assistive software already in use. Include the normal browser if the task runs on the web. Agree what completion looks like, such as entering three fields, saving the sample, and returning to the task list.
Avoid timing the person against someone else's typing speed. A better first decision is whether the route is understandable, repeatable, and acceptable to the person using it.
Match the adjustment to the barrier
When key combinations are difficult
Microsoft's input-device guidance describes Sticky Keys for entering multi-key commands one key at a time and Filter Keys for adjusting sensitivity to brief or repeated presses. In Windows 11, find these options under Settings > Accessibility > Keyboard.
Try the relevant option individually, with permission, then repeat the same short text-entry task. If intentional characters disappear or a shortcut behaves unexpectedly, stop and review the setting rather than adding more adjustments.
When moving between controls is difficult
On Mac, Full Keyboard Access is available under System Settings > Accessibility > Keyboard. Its default commands include Tab, Shift-Tab, Space, and arrow keys; Tab-H opens command help. Apple also offers a simpler Keyboard navigation option. Check which mode the employee needs before enabling the broader command set.
Follow the task from start to finish
Use the application's documented commands where available. Microsoft's Windows shortcut reference covers system navigation, but individual applications can have their own conventions.
- Open the application and reach the starting screen.
- Move forward and backward between relevant controls. Confirm the person can identify the current focus.
- Enter and correct sample text, including punctuation and an intentional repeated character.
- Operate a menu, list, or date selector used in the job.
- Open a harmless dialog, then cancel it and return to the previous task.
- Save the test work and reopen it using the normal keyboard route.
For sighted keyboard navigation, watch the focus indicator through the entire sequence, including after scrolling or opening a panel. W3C's Focus Visible explanation explains why users need to know which control will receive the next action.
For employees who spend time in calls, add a practice meeting. Check the route to mute, chat, and leave, then return to the document. A successful typing test does not cover those separate controls.
Turn failures into specific decisions
If a date selector opens but the person cannot select a date, record the exact application, control, keys tried, and documented alternatives. Test an approved alternative input route if one exists. Do not describe the whole keyboard as faulty from one control's behavior.
If Tab remains inside a dialog, check its Cancel control and documented exit. W3C's No Keyboard Trap guidance distinguishes an escapable modal dialog from content that prevents keyboard users from leaving.
If a shortcut works in one application but starts another action elsewhere, investigate the scope and command conflict. Avoid a global remapping before checking the application's own settings.
Use the pointer-options guide when pointer operation remains part of the employee's preferred workflow. A mixed approach may be appropriate; the test should reflect the actual requirement.
Close with a usable handoff
For a replacement laptop or shared desk, carry those details into the accessibility handoff. Retest in the actual account and workstation rather than assuming preferences transferred.
If several staff workflows need coordinated review, discuss the device and application scope through managed IT services. Clarify any specialist-tool requirements before agreeing on support work.
Reviewed October 23, 2026. Check current vendor instructions for the installed versions. These task checks are practical planning aids, not an accessibility certification.