Can someone finish the task using only a keyboard?

The payment control looked ready. Eighteen Tab presses never reached it. We replaced it with a native button, reran the same test, and reached PayPal in four key events. Can I Finish makes that before-and-after result repeatable, so a team can catch the same barrier before its next release.

How it works

Define the task and its finish line. A Node.js and Playwright runner executes the keyboard steps in Chromium. Each step records the key, focus target and screenshot. If a task fails, an on-device Qwen2.5-Coder model can review the evidence and relevant source and propose a repair. The browser rerun verifies the outcome. Export the task as a regression test to keep checking it.

What we demonstrated

  • Merchant checkout: The same task fails on an unreachable payment control and reaches PayPal after the native-button repair. Separately, a buyer-approved $1 sandbox purchase is verified through the PayPal Orders API.
  • GOV.UK: The keyboard journey reaches the disabled person’s bus-pass application page in 26 key events.
  • Apple: The keyboard journey reaches the iPhone VoiceOver setup guide.

What we learned and what’s next

Live pages can change, so we made the finish line explicit and kept the exact same task contract across the repair. Twenty automated checks cover contracts, evidence integrity, AI evidence references and payment protections. Next, we’d make it easier for teams to run exported checks in CI and compare results across releases.

Codex assisted with code, design, scripts and editing. Chatterbox generated the narration locally.

Try the live app · Inspect the checkout evidence · Source and setup

Built With

Share this project:

Updates

Submission history