A useful pilot in airports should prove one complete journey. Curbside, check-in, security exit, gate corridor, restroom or service animal relief, baggage, and ground transport. That is more valuable than scattering audio across a venue before anyone knows which messages actually help.
Scope the route
The pilot route should start where visitors naturally arrive, pass through one high-value task, include at least one amenity, and end with a return or exit decision. In airports, that usually means mapping curbside, check-in, security exits, gate corridors, restrooms, concessions, service animal relief areas, baggage claim, and ground transport.
A pilot should include no more than the messages needed to test the journey. Extra stops make the pilot harder to maintain and harder to evaluate.
Test the route
Ask blind and low-vision participants to complete the route without being pre-led to each sign. Watch where they pause, what they replay, and where they still ask for help.
Measure four things: discovery, orientation, completion, and recovery. If the route cannot help someone recover from a wrong turn or a changed condition, the content needs another pass before the project expands.
If an airport team already has a route, message list, and update owner, the next step is comparing implementation options on the site’s check providers page. Use that page after the content plan is clear, not before.
What airport teams should do next
For airport teams, the next step is to define the handoff points. Curbside, check-in, security exit, gate corridors, service animal relief, baggage claim, and ground transport often belong to different owners, so compare tools only after the operating map is clear.
Sources and further reading
We use primary and standards-based sources wherever possible. Accessed for this review on October 8, 2026.
- Wheelchair and Guided Assistance U.S. Department of Transportation
- Blind or Low-Vision Services JFK Airport
- Accessibility MSP Airport