Trying the AccessTrip walkthrough

About 20 minutes. Seven short web pages copy the phone screens of our prototype, because Figma frames can't be explored with a screen reader. Do as much or as little as you like. A single sentence back helps us.

Open the walkthrough overview. It explains how the pages are laid out. Each page has one heading that starts with “Walkthrough” and its number, and the phone screen is in a region whose name starts with “App screen”.

The scenario

Maya is blind, uses VoiceOver and flies with her guide dog, Juno: Delta, LaGuardia to O’Hare, Friday, November 13. The pages go from setup, to an AI call to Delta on November 5, to the airport on the day. Nothing you type is sent or saved.

Five things to try

  1. Walkthrough 2: what the call shares

    Before the AI calls Delta, find what Delta will hear and what it won’t. Would you trust this list?

  2. Walkthrough 3: a decision during the call

    The agent offers help only to baggage claim, not to the exit. You have a 2-minute countdown and three answers. Pick one, or ask for more time. Did the countdown or the announcements get in your way?

  3. Walkthrough 4: what Delta agreed to

    Find what changed on the call and what is still not covered.

  4. Walkthrough 5: check-in

    Delta says to meet staff at door C4, but a traveler report from Nov 12 says the podium moved to C6. Would you act on a dated, unverified report like this?

  5. Walkthroughs 6 and 7: security and the rights card

    At security, open the rights card and use “Show to staff” to step through the four rules. Is this something you would hold up to a TSA officer?

What we most want to know

Rough notes are fine. Reply to the email, or tell us on a short call if that’s easier.

This is a student prototype for INFO 5265 at Cornell, Group 5. Delta details are illustrative; they are not Delta’s actual process.