FUNNEL KEYBOARD PATH WORKSHEET

Purpose: inspect one identified interaction route and give its owner a reproducible
issue/recheck record. This is a bounded keyboard review, not full accessibility
evaluation, certification, a legal assessment or proof of stored/delivered outcomes.

1. DEFINE THE REVIEW
Visitor task:
Exact page address and version:
Date/time and time zone:
Reviewer:
Operating system/version:
Browser/version:
Keyboard-navigation settings checked:
Other relevant assistive setup (or none used):
Permitted environment and responsible person:
What activation/submission can trigger:
How those effects were established:
Stopping point if effects or permission are unknown:
Controlled test inputs / where they are recorded:
Evidence location without unrelated personal information:

2. PREPARE A ROUTE
Create one row per meaningful checkpoint. Do not expect every static paragraph to
be a Tab stop. Record any use of a mouse to recover. Leave unrun observations blank.

Checkpoint ID:
Starting state / focused control:
Control label and intended purpose:
Exact keys/actions:
Expected visible result and next focused control:
Actual result:
Focus visible and location understandable:
Could the task continue using the keyboard:
Mouse recovery, if used:
Status: not run / blocked / observed as expected / issue observed
Reason and evidence:

3. FICTIONAL WORKED ROUTE — NOT AN ACTUAL TEST
Page: Garden Tool Care Enquiry, version A.
Task: inspect service details, select a service, correct a missing description and
reach the visible enquiry result. Submission effects are assumed controlled only
for this fictional exercise; that assumption must be verified for a real check.

K01 | Open "What can be serviced?" | Trigger reached; dialog opens.
K02 | Close details and continue | Focus returns to trigger; next Tab reaches service.
K03 | Choose "Hand-tool sharpening" | Choice changes without submission/navigation.
K04 | Leave Description empty; activate "Send enquiry" | Error appears; focus not
visible; reviewer uses mouse to find field. Keyboard route interrupted.
K05 | Correct Description and continue | NOT RUN in keyboard pass due to K04.

All notes above are invented. No saved request, email, booking or CFAI behavior has
been observed. A later mouse-assisted action would not complete this keyboard case.

4. ISSUE HANDOFF
Issue ID / checkpoint:
Exact page and version:
Environment and input record:
Starting state:
Steps to reproduce, including exact keys:
Expected behavior:
Observed symptom:
Where the visitor gets stuck or loses their place:
Mouse recovery / stopping point:
Evidence:
Technical cause: unknown unless independently established
Responsible person:
Proposed correction (not a completed fix):

Fictional K04 record:
Starting at Reply address, leave Description empty and activate Send enquiry with
Enter. Description error appears; focus indicator is not visible. Repeated Tab
presses do not make the correction path clear. Reviewer uses mouse; keyboard case
stops. Expected: visible, understandable route to correct Description and continue.
Cause: unknown. Proposed next step: owner reproduces and inspects the implementation.

5. RECHECK
Changed version / date:
What changed and who changed it:
Same starting state recreated:
Original checkpoint result and evidence:
Next checkpoint result and evidence:
Related controls to recheck if shared components changed:
Remaining issues / blocked checks:
Responsible person and next action:

6. SCOPE OF THE RESULT
Routes and environments actually reviewed:
Routes not reviewed:
Additional accessibility evaluation needed:
Separate saved-record / delivery / booking checks and their owners:
Never summarize a single keyboard pass as full accessibility or product acceptance.

Guidance:
https://www.w3.org/WAI/test-evaluate/preliminary/
https://www.w3.org/WAI/ARIA/apg/patterns/dialog-modal/
https://www.w3.org/WAI/tutorials/forms/notifications/
ClickFunnels AI workflow/access: https://www.clickfunnels.ai/agents