🧭 Accessibility Scanner Demo

In about 10 minutes, you'll turn user feedback into a GitHub issue and a Copilot pull request. Follow the steps below.

Personas Demo website Resources

🚦 Before you start

  • Pick one persona and follow their barrier all the way through to a merged fix.
  • Scan the QR code for a quick link to the booth resources page, including GitHub accessibility scanner links.
  • If you have questions or get stuck, booth staff are happy to help — just ask.

👀 What you'll learn

  • How the accessibility scanner finds barriers on a live site.
  • How findings turn into GitHub issues with guidance and screenshots.
  • How Copilot turns an issue into a pull request you can review and merge.

📱 Quick access

Scan this QR code to open the booth resources page, including GitHub accessibility scanner links, on your phone.

QR code linking to the booth resources page, including GitHub accessibility scanner links.
Open the resources page

🎯 Your goal: Find → File → Fix

  1. Pick a persona. Open user feedback and choose one persona whose barrier you'd like to follow. Optional: Open the fake demo website and try that persona's path before filing the issue.
  2. File the feedback issue. Select the persona to open a prefilled GitHub issue, then click Create. This kicks off the accessibility scan for that persona.
  3. Watch the scan run. A bot will comment on your issue with a link to the workflow run. Open that link to follow progress, or check the Actions tab if you lose it.
  4. Review the accessibility scanner's issues. When the scan finishes, the bot posts a summary comment with a link to the issues it filed for your session. Open one to read the guidance, screenshot, and suggested fix.
  5. Confirm the Copilot issue selection. The scanner auto-selects one issue in your scan session and assigns Copilot to start drafting a fix. Wait for the first pull request to open from that issue. After it opens, you can assign Copilot to additional scanner issues in the same session.
  6. Open the pull request. Copilot links its PR from the issue when it's ready (usually a few minutes). If you don't see it, check the Pull requests tab for the newest Copilot PR.
  7. Review the fix. Look at the Files changed tab and Copilot's summary to see what changed and why.
  8. Optional: ask Copilot to make changes. Comment on the PR to ask Copilot to:
    • Explain how the fix helps your persona.
    • Check whether the fix introduces any new accessibility issues.
    • Add a test that keeps this issue from coming back.
  9. Merge the PR. When the fix looks good, click Merge pull request.
  10. Close the loop. Head back to the original user feedback issue from step 2 — the persona has posted a thank-you comment for the fix. Thanks for trying the demo!