Disability etiquette and language

Why it matters

Accessibility professionals work directly with disabled people, present to organizations, and influence how teams communicate about disability. Etiquette and language are not soft skills — they reflect the underlying model of disability an organization operates from, and they affect whether the people you serve feel respected or patronized. (BoK p. 35)

Disability etiquette: key principles

The BoK’s etiquette guidance covers several interaction domains: (BoK p. 35)

Consent before assisting

Do not assume a person with a disability needs help. Ask first — “Would you like assistance?” — and accept “no” gracefully. Unsolicited help, however well-intentioned, can be disrespectful and can interfere with the person’s chosen method of managing the task.

Speak to the person, not their companion or interpreter

In settings where a person is accompanied by an interpreter or companion, direct conversation to the person, not to the person facilitating. “How can I help you?” addresses the person with the disability; “What does she need?” addresses the companion — which is often experienced as objectifying.

Respect personal space, devices, and assistance animals

A wheelchair, cane, braille display, or guide dog is an extension of the person’s personal space and functional self. Do not touch, move, or interact with these without permission. Do not pet a guide dog — it is working.

Speak naturally and at a normal pace

When speaking with someone who has a communication difference, speak naturally. Do not exaggerate articulation, speak slowly as if to a child, or repeat the same words louder.

Avoid terminology that others find demeaning

Avoid terms like “wheelchair-bound” (most prefer “wheelchair user”), “suffers from” (implies tragedy), or “special needs” (often perceived as patronizing). Use the terms the person uses for themselves when known.

People-first vs. identity-first language

This is one of the most discussed and sometimes contentious areas in disability practice. (BoK p. 35)

People-first language

People-first language places the person before the condition: “a person with a disability,” “a person with autism,” “a person who is blind.” The logic is that the person is more than their disability, and leading with the condition reduces them to it.

This is the convention adopted by the UNCRPD, by IAAP (per the BoK front matter), and by many professional and governmental organizations. It is the BoK’s default.

Identity-first language

Many disability communities prefer identity-first language, where the disability is named first: “a Deaf person,” “an autistic person,” “a blind person.” The logic is that the disability is an integral part of the person’s identity, not a separate attribute to be linguistically minimized. The Deaf community (capital D) has long preferred identity-first language, and the autistic community increasingly does so as well.

IAAP and UNCRPD usage

The BoK’s front matter notes that IAAP uses person-first language, following G3ict, and aligned with the UNCRPD. This matters for the exam: IAAP’s published materials default to people-first, and questions will likely reflect that convention. However, identity-first is presented as legitimate and preferred by certain communities — not as incorrect. (BoK p. 35)

Real-world example

An accessibility consultant is advising a healthcare provider on patient communication. The provider’s templates say “suffers from diabetes and is wheelchair-bound.” The consultant recommends replacing these with “person with diabetes” and “wheelchair user” — reflecting people-first language and removing stigmatizing framing. For a patient who identifies as Deaf and prefers “Deaf person,” the consultant recommends consulting the individual and updating that patient’s record accordingly.