Back to blog
Quiz StrategyNovember 15, 20265 min read

How to Test a Branching Quiz With Only a Keyboard

Find the point where a visitor loses their place, gets stuck on an answer, or can’t reach the next step.

By QuizFlow Labs
A keyboard key leads to a fork in the quiz path, with a bright focus outline around one choice.

Test the transitions as well as the questions

A branching quiz can show the right recommendation and still be hard to finish with a keyboard. A visitor needs to reach and operate each question, find their place when a new step opens, and recover if an answer is missing. Branching makes the handoff especially important because the next step can depend on which answer they chose.

Do a complete walkthrough with your hands off the mouse. Start where a visitor starts, including the page that contains the quiz if it is embedded. Pick a common path and one that introduces a different kind of interaction, such as a required field, an extra question, or a different result action. Two paths that show different wording but use the same controls offer less coverage than two paths that ask the visitor to do different things. Repeat the walkthrough for other distinct interactions before launch.

Check reach, visibility, and operation separately

Use Tab to move forward through controls and Shift+Tab to go back. Watch for the outline or other visual cue that shows which control will respond to your next key. Use Enter to follow a link. Use Enter or Space to activate a standard button and the arrow keys to move through options in a standard radio group. A row of answer cards may behave like buttons or like a radio group, so check which behavior the interface presents. One Tab stop for a whole radio group can be normal.

Record the first point where you need the mouse. If you can reach a choice but have to guess which one has focus, check focus visibility, including whether the marker is clipped or covered. If the focus marker is visible but the expected key does nothing, check how the control operates. If you can never reach a choice, check whether it’s genuinely unavailable or missing from keyboard navigation. A screenshot can show a clipped outline. A short recording with the keys you pressed helps distinguish a skipped control from one you reached but couldn’t operate.

DWP Accessibility Manual: keyboard test instructionsOpens in a new tab

Pause every time the branch changes the screen

After activating an answer or Continue, pause before pressing another key. Look for the new question or result. Then press Tab once and note where it takes you. You should be able to tell which step opened and reach its controls in an order that makes sense. If the first Tab jumps to the site header, record it. If it jumps past a required answer to Continue, check whether you can reach that answer in a sensible sequence without retracing the whole page.

Focus can land on the new heading or on a useful control, depending on how the step is built. A first field can work well when it’s clear which question it belongs to. A transition that brings you straight to a control can be disorienting when there’s important context above it. W3C’s focus order guidance allows different sequences as long as they preserve meaning and operability. Write down what the visitor can discover and do from the new position so the report describes the problem it causes.

W3C: understanding focus orderOpens in a new tab

Example: a workshop finder with two paths

Imagine a ceramics studio quiz that recommends either a beginner workshop or open studio time. The beginner path requires a weekend choice. The open studio path asks whether you’ve used a pottery wheel and also requires an answer. On each path, try to advance without answering, then complete the path and check its result link. If Continue is disabled, check whether the question tells you what you need to do before you can proceed.

Suppose both questions can be answered by keyboard, but the open studio question shows only a red border after you try to continue. That run exposes a problem with error identification. A text message such as “Choose whether you’ve used a pottery wheel” tells the visitor which answer is missing. Check that they can reach the question, supply the answer, and continue using the keyboard. If the text is there but the first Tab after the error takes you out of the quiz, check how many steps it takes to get back to the unanswered question. If it takes a trip through unrelated controls, record that recovery problem separately from the wording of the error.

On a fresh run, use the quiz’s own Back control if it offers one. Switch the initial answer and check that the newly relevant question and its controls are reachable. If focus still goes to something from the previous path, report the transition and the key sequence that produced it. If the controls are usable but the quiz shows the wrong recommendation, investigate the routing rules separately.

W3C: understanding error identificationOpens in a new tab

Retest the stuck point and the next action

For each problem, save the page URL, browser, answers that led there, last key pressed, and what happened on the next Tab. Include the entry page when the quiz is embedded. If an embedded quiz fails while the same path on its hosted page works, repeat the steps on both. Check the surrounding page and the handoff into or out of the embed before changing the quiz questions.

Start the retest from the entry page so the same branch and focus history are in play. After passing the stuck point, keep going to the result. Reach and activate the action the result promises. Use a test destination for actions that would send a message, take a payment, or make a booking. A useful pass is a visitor reaching the intended next step, including after they correct an answer, without needing the mouse.

If your QuizFlow Labs project has a published hosted page, use that link for a comparison when testing the embedded version. Run the walkthrough on the surface your audience will actually use. This keyboard walkthrough covers the paths and browsers you exercised. Include a separate screen reader check for question announcements and errors, which a visual keyboard pass cannot evaluate.

Read the QuizFlow Labs hosted flow guide

Build a Quiz

Guide visitors to the next step

Build a decision flow in QuizFlow Labs, then walk through each route from the first question to its result action.

Create a quiz

More from the blog

Keep reading

View all posts
Share