Operator ready

Show the full accessibility loop

Open the demo

A roughly 90-second, seven-screen walkthrough for non-technical visitors. The opening screen says Find barriers. Fix what matters. and lets visitors choose one of three people. Five numbered steps – Bug report, Find, File, Fix, Final check – lead to a standalone Explore the scanner screen with takeaways and a QR code. Every screen after the opening screen carries a Back button, so nobody is trapped.

Before visitors arrive

  1. Open the demo and choose the display theme and motion setting that read best in the venue lighting.
  2. Confirm the screen, touch input, and recording controls work, then complete one scenario end to end.
  3. Select Restart to leave the demo on the opening screen, and keep this guide open on a staff device.
  4. If Wi-Fi is unavailable, run npm start on the booth laptop and open http://localhost:4173.

Invite and guide

  1. Start on the opening screen: it introduces the AI-powered accessibility scanner from GitHub and shows the three people on the same screen.
  2. Invite visitors to choose a person based on their job and access needs.
  3. At Bug report, read the blocked task and the person’s report, then watch the illustrative recording. The recording control pauses, resumes, and replays it. No code detail appears yet.
  4. At Find, explain that the report triggered a scan of the code. The scanner shows its three progress beats, the issue it found, the rule, the WCAG standard, and the highlighted source.
  5. At File, the scan’s finding becomes a bug that carries the rule, location, standard, reporter, and blocked task, plus labels and a GitHub Copilot assignee.
  6. At Fix, read what GitHub Copilot was asked, the steps it took, the summary of what changed, and the original and proposed code side by side. Select Confirm fix to continue.
  7. At Final check, read the person’s re-test and watch the fixed recording to confirm that their task is unblocked.
  8. On the Explore the scanner screen, read the Find, File, and Fix takeaways, then point to the QR code for visitors who want the scanner repository. Select Restart for the next visitor.
  9. If a visitor wants to revisit a step, select Back; the story and every choice are kept.

What to say: cheat sheet

When someone walks up“Want to see an accessibility issue go from a real person’s feedback to a verified fix in about two minutes?”

When they ask what this is“It is a guided example of the Find → File → Fix loop: a person reports a blocker, a scan finds it in the code and files a bug, GitHub Copilot proposes a reviewed fix, then the person re-tests.”

At the filed bug“The goal is not just passing a check. One report becomes one bug, and it keeps the person, blocked task, rule, and code location attached to the finding.”

At the fix screen“Review the original code, the proposed change, and Copilot’s reasoning, then confirm with the reporter that it helps them finish their task.” The steps and the code arrive slowly on purpose – let visitors watch it write.

When they ask whether it is live“This is an offline simulation built for the booth, using representative accessibility findings and fixes. It makes the workflow easy to explore.”

When they are ready to leave“One small, verified fix closes the bug and makes a whole flow work for more people. Thanks for taking the sprint.”

What verification means“This example resolves one barrier. A passing automated check is not a full accessibility audit; real fixes also need human and assistive-technology testing.”

Quick visitor tryout

Ask a non-technical visitor to finish without coaching. Target 1–2 minutes; the scan details, the filed bug, the proposed code change, and the scanner takeaways are already on screen. Afterwards, ask: What was the person trying to do? What did they report, what bug did the scan file, what changed, and how did we know it worked?

Repeat for all three stories and check keyboard navigation, both themes, reduced motion, and narrow screens. Visitor timing still needs to be observed in person; the 90-second target is not a measured guarantee.

The demo never advances a step on its own. After three minutes without input or scrolling, a dialog warns before returning to the opening screen. Select Keep exploring or press Escape within 30 seconds to keep the current story.