Rehearse a complete workshop contribution using a keyboard

Define the whole contribution

A workshop can offer readable materials while leaving its contribution task unusable without a pointer. Rehearse the work someone must complete, including how they recognize its recorded result and leave the interaction. This is a manual planning exercise, not a report of an actual trial or a guarantee about Kiguri controls.

In this fictional workshop, the facilitator asks people to arrange agenda cards K1, K2 and K3 and give one reason. The planned rehearsal response is K2, K1, K3 because the dependency question should be discussed first. That is an invented practice response, not a correct ranking for every workshop. Completion requires the order and reason to be recorded where the facilitator will review them, followed by a return to the workshop instructions.

Follow focus through function

Make a participation run sheet in an ordinary document. Record the starting location, required action, documented keyboard route, observed focus, function, result and exit. Leave observations blank until someone actually performs the rehearsal. Agree that checking a known route is the purpose; this is not an uncoached prototype study.

W3C WAI's Keyboard guidance distinguishes comparable keyboard functionality from reproducing a pointer gesture. Use the application's documented route rather than prescribing one universal sequence of keys. In the fictional interface, dragging appears to be the only visible way to reorder cards. Reaching a card and reading K2 would establish access to its label, not the ability to move it. Look for a documented alternative that changes the order, then check the resulting sequence. An undocumented or unavailable route remains a blocker, not an invitation to guess indefinitely.

Confirm the result and the way out

Continue the planned trace beyond reordering: enter the reason, complete the required recording action, inspect the recorded order and reason, and return to the instructions. Text still visible in an editing field does not by itself establish that the facilitator can retrieve the contribution. Identify what confirmation the chosen tool actually offers and what would remain unverified.

W3C WAI's No Keyboard Trap guidance also makes leaving a component part of the check. Record where focus goes after leaving and whether the next required action can be reached. If someone can enter the card interaction but cannot leave it using the documented route, the complete contribution has not passed. Do not assume a particular exit key works everywhere.

Keep assistance visible

If a facilitator uses a pointer to put K2 first, label that step as assisted. A finished-looking response does not turn the attempt into keyboard completion. Keep the blocked action and the assistance beside the result so another host does not mistake a rescued attempt for an independently usable route.

An alternate writable document is only a candidate. It must accept K2, K1, K3 and the same reason, not merely a comment while someone else decides the order. Agree where that response will count alongside other contributions. A listening-only role would remove the requested work rather than provide another way to perform it.

Check the alternative from start to exit

Rehearse that alternate document's complete route separately: reach it from the instructions, enter the order and reason, confirm the recorded response, and leave for the next workshop step. Preserve any unchecked transition as unresolved. If no complete route is established, change or defer the task instead of announcing that participation is ready.

The finished run sheet identifies the agreed route, assistance and remaining blockers. It establishes neither accessibility of the original card control nor usability for every participant. No contribution or rehearsal has been performed in this example.