EXPLORATION
To avoid narrowing our design concept too early, we brainstormed 100 ideas—both good and bad—which were then evaluated and refined into 10 strong concepts.
"An enjoyable travel experience is one where I don't have to worry too much about where to go next. I find that time can be wasted when plans are not made ahead of the trip"
Among the 10 design concepts, one focused on the public transit experience stood out
After weighing the pros and cons of each design concept, we revisited the recurring theme of insufficient audio accessibility in public transit, which emerged from our semi-structured interviews with the DHH community.
"An enjoyable travel experience is one where I don't have to worry too much about where to go next. I find that time can be wasted when plans are not made ahead of the trip"
(2) Participatory Design Sessions: Evolving our concept into designs via expert and user critiques
Recommendations focused on reducing text reliance, using visual symbols for alerts, and limiting cues to a small set of high-priority options.
Designing an entirely new product was unnecessary, especially since most users already relied on Google Maps for their transportation journeys.
DESIGN DECISIONS
There were contextual nuances determining the optimal placement of our audio accessibility feature
A comprehensive audit of a transportation journey on Google Maps allowed us to identify key events where our feature could be implemented.
View past cues, whether due to their phone being away, the journey being inactive, or simply overlooking the notification.
This is particularly useful for announcements, which are often not visually indicated, with users citing the lack of visual information and signage as detriments to their journey.
Detection and transcription of alerts and cues, such as approaching trains, fire alarms, or announcements.
The ability to visually perceive audio cues is the core functionality of our feature, which users identified as a critical need in interviews, highlighting its absence in public spaces.
Validating audio feedback transcription via crowdsourced feedback from hearing individuals
We aim to avoid misinforming users, which is why this validation flow is included—a concern also highlighted by our co-design participant.