Define the complete keyboard task
Put the mouse aside and start from the published service page. Can you reach the quote form, choose a service, move to the next step, return to review an answer and submit? Record where you stop and what control has focus. Testing only the first screen misses failures introduced by dynamic steps and custom selection widgets.
Use progress and focus as part of the journey
W3C keyboard guidance addresses operation through a keyboard interface, and its multi-page form tutorial discusses progress and preserved answers. Apply those principles to your form's actual sequence. Standard controls often provide useful expected behavior, but custom components still need verification. A short owner test is a diagnostic, not a complete conformance assessment.
Use the receiving evidence your system actually provides. If it stores submissions, inspect the marked record there. Otherwise ask the maintainer to verify server acceptance and the intended receiving destination through supported logs or delivery evidence. A thank-you screen alone is not proof. Wix-specific submission-table names belong to the Wix example.
Source checks: W3C: Understanding Keyboard · W3C WAI: Multi-page Forms · W3C: Understanding Focus Order
Walk through normal and error paths
Use marked fictional answers and test at least one missing required field. Observe whether changing steps makes the next task understandable or leaves focus on an unrelated hidden control. Review earlier answers without losing them. Ask the maintainer to reproduce any blockage and provide a specific repair rather than adding arbitrary tab-order numbers.
- Tab from the published service page into the first step and identify the focused control.
- Operate each selector and use the labeled Next action without the mouse.
- Leave one required answer missing and check that correction is reachable and understandable.
- Return to a previous step, review retained answers and continue through the final request.
- Submit a marked valid request and verify the receipt against supported acceptance and delivery evidence.
Avoid a visually working but keyboard-only dead end
A custom service tile may respond to a click but not keyboard activation. Hidden controls from earlier steps can remain in the tab sequence. Moving focus to the top navigation after Next can make progress confusing. Do not declare the form accessible merely because Tab reaches several inputs; the customer task needs an end-to-end path.
Record blocked tasks rather than vague scores
Record each blocked action with the step name, control and expected outcome. Retest those actions after repair and retain the marked submission identifier. Invite appropriate specialist review for broader accessibility needs. These observations establish which tested keyboard tasks work; they do not predict usage rates or certify every assistive-technology combination.
Retest after adding a form step
Keep the keyboard test sequence with the form's maintenance checklist. Repeat it after adding fields, changing conditional steps or replacing a widget. Preserve the expected progress labels and review behavior in the handoff note. A future editor should understand that Back and error recovery are part of the quote journey, not optional decoration.
Worked example: an illustrative customer journey
For example, a three-step repair form has service, details and contact stages. A custom service tile can be selected with a mouse but not from the keyboard, so the customer cannot activate Next. The maintainer replaces or repairs the control using supported keyboard behavior.
TEST-KEYBOARD-3001 then moves through all stages, reviews an earlier answer and submits successfully. A missing contact field is tested separately. This verifies the specific journey and error case, not every aspect of the website's accessibility.
Keyboard checks across three steps
Service
Select the task without a mouse
Details
Correct errors and retain answers
Contact
Review required information
Receipt
Complete and verify the request
Your practical checklist
- Start from the service page rather than a direct input.
- Operate service choices without clicking.
- Test Next, Back and the final submission.
- Confirm previous answers survive review.
- Check an error path with a missing required answer.
- Verify the final receipt matches an accepted marked test.
Your next action
Complete your published multi-step quote form with the mouse set aside and record the first blocked action.
Questions about this task
Can I test only with Tab?
Tab checks movement, but also activate controls using their expected keys and complete the actual task.
Do more steps always help customers?
No. Use steps only when they organize necessary information, then verify the whole journey.
Sources and editorial notes
Prepared with AI-assisted research. Official sources are linked below; worked examples and checklists are Getting Found Local recommendations, not measured client outcomes.
Sources checked October 13, 2026. Platform interfaces and local resources may change; follow the current instructions on the linked official page.
How we research, illustrate, and update these guides · Suggest a correction