Finding Out Last: A Deaf Traveler's Experience on 9/11

Description

The plane landed hard and fast. No explanation appeared anywhere. I looked around and saw passengers with panicked faces, some crying. I tapped a stranger on the shoulder and wrote on a piece of paper asking what was going on. He wrote back: plane delayed, accident in New York. That was it. I still didn't understand the scale of what had happened. It wasn't until I found a television in the terminal that I saw the towers fall. My husband worked in a federal building in Washington, D.C. I used a small pager to reach a coworker there, because that was the only way I could.

Hours later, I made my way to a car rental counter. The man looked at my reservation and asked if I knew where I was. I told him Minneapolis. He wrote to me and said no, Grand Rapids, Michigan. The plane had been rerouted. Every hearing passenger around me had known for hours. 

I eventually got a bus to a hotel and stayed for three days before renting a car and driving home.

The core problem was not just the chaos of that day. It was that every critical update, the landing, the reroute, the instructions from staff, was communicated through audio. Nothing appeared on a screen. Without visual communication tools, I had to chase down every piece of information myself.

Airlines have improved in some ways. On a recent flight I notified staff I was Deaf upon boarding, and a flight attendant was assigned to my area and checked in with me directly. It was the best experience I had in 25 years. But captioned announcements are still rare. Gate changes still go up as audio only. I have missed flights because of it.

What I want is straightforward: captions on screens, visual alerts for gate and flight changes, and staff who know how to communicate with Deaf passengers. Not every Deaf traveler communicates the same way. But all of us deserve to know where we are.

Main Takeaway

On the morning of September 11, 2001, I boarded a flight from Washington, D.C. to Minneapolis. I was representing Gallaudet University at a Deaf conference. Born Deaf and a Gallaudet graduate, I was used to filling in gaps that hearing people never have to think about. That morning, the gaps were enormous.

How is my profile information used on ICAAT?

FAQ Category
Answer

Profile information is used only to support community interaction on ICAAT. Your name and basic profile details may appear next to your posts or comments in the ICAAT Tech Forum, so other users know who is participating in discussions. 

 

For users who register as industry or research participants, ICAAT may use profile information internally to verify affiliation or role. This verification is administrative only and is not publicly displayed or shared.

When Accessible Systems Cannot Be Confirmed

Description

When the film started, my receiver was silent.

That moment is familiar to many people with hearing loss. I adjusted the controls, wondering whether I had done something wrong. I quietly asked others if their receivers were working. They shrugged, unsure. This uncertainty is common. People with hearing loss often do not trust themselves to know whether the problem is the system, their hearing devices, or their own settings. When there is no clear confirmation that assistive listening is active and functioning, effective communication breaks down quietly.

What stands out is how invisible this failure was to everyone else. From the outside, access appeared to be in place. Assistive listening was labeled as available. Yet there was no routine verification as part of setup and no feedback during use. Staff had no clear signal that anything was wrong, and users were left guessing. Over time, that uncertainty leads people to disengage from shared experiences rather than continually advocate or troubleshoot in public.

From a user perspective, technology that supports communication must support staff as well. Systems need simple, built-in ways to confirm that microphones, audio feeds, and assistive listening outputs are working as intended. Relying on memory, informal training, or user self-report is not enough.

Communication does not exist as a single audio feed. It moves through speakers, staff, systems, and listeners. When any link in that chain is weak, access breaks, even in spaces that believe they are inclusive.

Main Takeaway

After church, I went to a movie with a group of friends. Several of us picked up assistive listening receivers at the front desk. The staff said the system was working. As is typical, there was no way to verify this beforehand since no audio was playing.

How was ICAAT developed?

FAQ Category
Answer

ICAAT was developed through a collaborative effort between Gallaudet University, the Hearing Loss Association of America (HLAA), and the American Institutes for Research (AIR). After completion of the development phase, ICAAT has operated under the sole direction of the Hearing Loss Association of America.

Seed funding for the development of ICAAT was provided by the Deaf and Hard of Hearing Technology Rehabilitation Engineering Research Center (DHH-RERC), funded by the National Institute on Disability, Independent Living, and Rehabilitation Research (NIDILRR), a center within the Administration for Community Living (ACL) of the U.S. Department of Health and Human Services (HHS), grant number 90REGE0013. The DHH-RERC was led by Gallaudet University.

The contents of this site do not necessarily represent the policy of NIDILRR, ACL, or HHS and should not be assumed to reflect endorsement by the Federal Government.

Who should consider participating in ICAAT?

FAQ Category
Answer

ICAAT welcomes consumers and consumer advocates, along with participants from industry and research.

Consumers and consumer advocates include people with hearing loss, caregivers and family members, clinicians, educators, and others who advocate for effective, technology-based communication access solutions.

Participants from industry and research include professionals from companies that develop, sell, or market communication access technologies or services, and researchers who study new and existing technologies.

ICAAT supports collaboration across all participants, keeps consumer experience at the center, and maintains a non-endorsing environment.

Access Starts Before the Event Begins

Description

The pastor spoke from the ambo using a fixed gooseneck microphone that was positioned too high. His voice was not captured as clearly or as strongly as it could have been, which forced me to strain to follow along and rely more heavily on lip-reading. That level of effort is tiring and distracting, and it pulls attention away from the meaning of the sermon itself.

What stood out was how easily this barrier could have been avoided. No equipment was broken. The system was present and functioning. What was missing was consistent microphone practice and a way for speakers to know, in real time, whether their voice was being picked up effectively. Other parts of the service use head-worn microphones, which provide far more reliable audio. The contrast made clear how much access depends on small, upstream decisions that speakers and staff may not even realize they are making.

Later in the same service, another access issue emerged. Right before the service began, the choir leader removed the hymn numbers from the board and did not replace them. For most of the congregation, this likely made no difference. For me, those visual cues are essential. I often catch only part of what is announced, and the numbers allow me to find my place and understand how the music connects to the message of the day. Without them, I felt disconnected from the meaning that others were receiving with far less effort.

This kind of barrier rarely comes from bad intentions. It reflects gaps in awareness and training about how people with hearing loss actually experience communication, and how much they rely on visual structure to stay oriented and engaged.

Main Takeaway

Yesterday was a reminder of how often communication breaks down long before a speaker begins to talk or a film starts.