Person-First vs Identity-First Language: Interactive Discussion Guide
Top TLDR:
Person-first vs identity-first language is not a rule to memorize but a conversation to navigate — both approaches are valid, and the right one depends on the person and community. The principle that works: ask the person what they prefer and follow their lead, with autistic and Deaf communities generally favoring identity-first and intellectual disability communities often favoring person-first. Update style guides to replace blanket rules with this ask-then-follow framework.
Why This Conversation Matters
Most workplace inclusion training touches the question of language at some point — and most of it gets stuck on a single rule: "use person-first language." Say "person with a disability," not "disabled person." Say "employee with autism," not "autistic employee." For two decades, this guidance has shaped style guides, HR handbooks, and well-meaning corporate communications.
The problem is that the disability community itself doesn't agree with the rule. Many disabled people — including some of the most active self-advocates and disability community leaders — strongly prefer identity-first language. Many others prefer person-first. Some use both interchangeably. The "always use person-first" guidance, applied universally, ends up overriding the actual preferences of the people it's supposed to respect.
This is one of the situations where well-intentioned policy crosses into the territory it was designed to prevent: speaking over the people whose identity is being named. The right response isn't to memorize a different rule. It's to learn how to navigate the conversation — to understand the history, the community context, and the principle that consistently lands well across both camps: ask people what they prefer, and follow their lead.
This guide gives you a working model and a structured discussion framework you can use in disability awareness training, team conversations, or one-on-one onboarding. For the broader pedagogical context, the 10 essential elements of disability awareness training in the workplace framework outlines where language work fits in a complete program.
What the Two Approaches Actually Mean
Person-first language puts the person before the disability: "person with a disability," "child with autism," "employee with bipolar disorder," "individual with a visual impairment." The structure is: person + with + disability descriptor.
The reasoning behind person-first language emerged in the late 1980s and early 1990s, primarily in the parent-advocacy and intellectual disability communities. The argument: when you lead with the disability, you imply that the disability is the most important thing about the person. Putting the person first emphasizes shared humanity and resists reducing someone to a single trait.
Person-first language was a meaningful shift at the time. It replaced phrases like "the disabled," "the handicapped," "the mentally retarded" — language that erased individuality. Person-first language gave families and self-advocates a tool to push back against dehumanizing framing.
Identity-first language puts the disability descriptor first: "disabled person," "autistic person," "Deaf woman," "blind man." The structure is: disability descriptor + person.
The reasoning behind identity-first language emerged primarily from disability rights and disability justice movements, and from specific community traditions — most prominently the Deaf community and the autistic self-advocacy movement. The argument: my disability isn't separable from me. It's not something I "have" alongside who I am; it's part of who I am, and refusing to name it directly implies that it's something to be ashamed of or distanced from. Saying "autistic person" rather than "person with autism" is, for many, an act of pride and self-naming — the same way we say "Black woman" rather than "woman with Blackness."
Both approaches share a goal — respect — and reach it through different theories of how language and identity interact.
What Different Communities Tend to Prefer
Preferences vary significantly across disability communities, and across individuals within them. A few patterns worth knowing:
Autistic community. Strong preference for identity-first ("autistic person," "autistic adult"). Major self-advocacy organizations including the Autistic Self Advocacy Network (ASAN) explicitly advocate for identity-first language and have for over a decade. Many autistic advocates describe person-first ("person with autism") as feeling distancing or pathologizing. There are exceptions, but identity-first is the dominant community preference.
Deaf community. Deaf people who identify culturally as Deaf (capital D, indicating cultural identity rather than just audiological status) consistently use identity-first language: "Deaf person," "Deaf community." Sign language interpreters, Deaf-led organizations, and the National Association of the Deaf use this convention.
Blind community. More mixed. The American Council of the Blind has historically used both. The National Federation of the Blind has often favored identity-first ("blind person") but isn't doctrinaire. Individual preferences vary widely.
Physical disability communities. Wheelchair users, amputees, and people with mobility-related disabilities are split. "Wheelchair user" is broadly preferred over "wheelchair-bound" (which is rejected as inaccurate and pity-laden). Both "disabled person" and "person with a physical disability" appear in self-advocacy spaces.
Chronic illness, mental health, and invisible disability communities. Often more comfortable with person-first ("person with chronic pain," "person living with depression"), though many self-advocates from these communities also use identity-first depending on context.
Intellectual and developmental disability communities. The original home of person-first language. Major self-advocacy organizations like Self Advocates Becoming Empowered (SABE) and The Arc have generally maintained person-first preferences ("person with an intellectual disability," "person with Down syndrome"). Some individual self-advocates use identity-first.
Disability rights and disability justice movements broadly. Tend to use identity-first ("disabled people"), particularly when speaking collectively about the political category of disability.
These are tendencies, not rules. Within every community, individuals vary, and the right move is always to ask the specific person whose identity is being discussed.
The Principle That Works Across Both
Here is the principle that consistently lands well: ask, then follow.
Ask the person whose identity is being named what they prefer. Use what they tell you. When you don't know an individual's preference and need to write or speak about a community in general, use the language the relevant community uses about itself in its own publications and self-advocacy materials. When in doubt about a specific phrase, name your uncertainty and ask: "I want to use the language you prefer — would you say 'autistic' or 'with autism'?"
This principle works because it shifts the focus from getting the rule right to respecting the person. It treats language as relational rather than as a static policy. And it produces consistently better outcomes than either "always use person-first" or "always use identity-first" applied universally.
The companion materials at disability language guide: what to say and what to avoid provide more detailed guidance on specific terminology — including the phrases that are universally rejected ("wheelchair-bound," "suffers from," "victim of," "afflicted with," "the disabled," "differently abled").
A Discussion Framework You Can Use
The most effective way to handle this conversation in a workplace context is structured discussion rather than lecture. Below is a 60-minute facilitator framework you can adapt for team meetings, training sessions, or onboarding conversations.
Opening (10 minutes)
Frame the conversation. "We're going to talk about language — specifically about the difference between person-first and identity-first language for disability. There isn't a single right answer here. There's a range of preferences within the disability community, and the goal of this conversation isn't to memorize a rule. It's to build the skill of navigating language thoughtfully and respectfully."
Acknowledge complexity up front. Many participants will have been taught a single rule and will be surprised to learn that the rule isn't universal. That surprise is useful — it opens the door to the actual conversation.
Background (15 minutes)
Walk through the history and reasoning behind both approaches. Use the framing in the previous section. Emphasize that both approaches emerged from genuine disability community advocacy, and both were and are responses to specific harms in how disability had been talked about previously.
A few discussion prompts to surface participant assumptions:
"Before today, what was your understanding of the 'right' way to talk about disability?"
"Where did you first learn that — a workplace policy, school, family, media?"
"What did you assume about why that was the rule?"
Examples and Practice (20 minutes)
Provide a worksheet with sample sentences and ask participants to flag both person-first and identity-first versions:
"Our team has welcomed three new colleagues with disabilities this quarter."
"Our team has welcomed three new disabled colleagues this quarter."
"The training will support employees on the autism spectrum."
"The training will support autistic employees."
"Several of our customers are wheelchair users."
"Several of our customers use wheelchairs."
Discuss the differences. Point out the cases where the two phrasings carry slightly different connotations even when they mean roughly the same thing. Surface participants' instincts and discuss where those instincts came from.
Then provide a short list of phrases that are universally rejected and discuss why: "wheelchair-bound," "suffers from autism," "victim of cerebral palsy," "afflicted with depression," "the disabled," "differently abled," "special needs." These are not preference issues — they are objected to across both person-first and identity-first communities.
The "Ask, Then Follow" Practice (10 minutes)
Pair participants for short role-play scenarios. One person plays a colleague meeting a new disabled coworker, an HR professional processing an accommodation request, or a manager writing a performance review. The other plays a coach offering real-time feedback.
Practice scripts:
"I want to use the language you prefer — what works for you?"
"I noticed your bio uses 'autistic.' Should I use that in the team announcement, or do you have a different preference for that context?"
"I wasn't sure how to phrase this — would you say 'employee with a disability' or 'disabled employee'?"
The goal of the role-play is to build comfort with naming uncertainty rather than guessing. Most missteps in this area come from people trying to get the rule right rather than asking. Practicing the ask removes that friction.
Closing Commitment (5 minutes)
Each participant identifies one specific change they'll make in how they handle language going forward. Examples: "I'll update our team's onboarding doc to remove the blanket 'use person-first' instruction." "I'll ask the new hire on my team what language they prefer for the team announcement." "I'll review our marketing copy for inspiration porn framings and outdated terminology."
Pair participants with accountability partners. A 30-day follow-up email asks each person to report whether they completed their commitment. The framework in DEI training metrics that matter beyond attendance tracking covers how to track behavior change beyond satisfaction surveys.
Common Sticking Points
A few questions come up in almost every workplace discussion of this topic.
"Isn't it safer to default to person-first if I don't know?" It's safer in the sense that person-first is less likely to cause active offense from people who prefer it. It's not safer in the sense of being correct or respectful — applying person-first universally overrides the explicit preferences of communities like the autistic, Deaf, and disability-rights communities. The truly safe default is to ask. When asking isn't possible (writing about a community in general), use the language the community's own self-advocacy materials use.
"What do I do when one autistic colleague prefers identity-first and another prefers person-first?" Use each person's preferred language when speaking about or to them. Yes, this requires a small amount of memory and care. That's part of the skill. The principle is that individuals get to name themselves; your job is to use what they tell you.
"What about parents of disabled children — they often prefer person-first." This is one of the most contested areas. Parent-advocacy communities have historically favored person-first language; many adult disabled self-advocates of the same conditions prefer identity-first and have explicitly asked that the language about their community shift. The right move is to follow the lead of disabled adults speaking about their own community, while respecting the language individual parents use about their own children.
"What about clinical or medical contexts?" Clinical settings often default to person-first ("patient with autism") for documentation reasons. That's reasonable in the chart. It's not a reason to override an individual's stated preference in conversation, performance reviews, team announcements, or any setting where you're speaking about them as a person rather than recording diagnostic information. The framework in disability training for healthcare organizations covers how clinical conventions and patient-respect language interact.
"What about avoiding the word 'disability' entirely — like 'differently abled' or 'special needs'?" Don't. Both phrases are widely rejected by the disability community as euphemistic and patronizing. They suggest that "disability" is a word too uncomfortable to use, which reinforces the very stigma the euphemisms were meant to soften. "Disabled" and "person with a disability" are the appropriate terms.
Updating Your Organization's Style Guide
Many organizations have style guides that codify "always use person-first" as a rule. Updating these documents is one of the more durable changes you can make.
A workable style-guide framing:
Disability language. Use the language individuals prefer for themselves. When speaking about a community in general, use the language that community uses in its own self-advocacy materials — for example, identity-first ("autistic," "Deaf") for the autistic and Deaf communities, mixed for many other disability communities. Avoid "wheelchair-bound," "suffers from," "victim of," "afflicted with," "the disabled," "differently abled," and "special needs." When uncertain about a specific phrase, ask the person being described.
This framing replaces a rigid rule with a principle that travels across contexts. It also signals to disabled employees and external readers that the organization has done its homework — a signal that matters.
For the broader practice of integrating language work into HR, marketing, and internal communications, the disability inclusion training for HR professionals and building a disability-inclusive culture beyond compliance training frameworks cover the full architecture this language work supports.
Why This Skill Matters Beyond Language
This discussion is foundational because the ask-then-follow principle scales beyond language. The same skill — recognizing that disability community preferences vary, that individuals have authority over their own naming, and that humility is more useful than confident rule-following — applies across accommodations, hiring, accessibility design, and almost every other area of disability inclusion work.
If your organization's training only ever produces a static set of rules to memorize, you've built a brittle skill set that breaks the moment a person doesn't fit the rules. If your training builds the skill of relating to people as individuals with authority over their own identity and experience, you've built something durable. The exercises in disability sensitivity exercises that actually work and the implicit-bias work in implicit bias activities for disability awareness training sit on top of this foundation.
Working With Kintsugi Consulting
Kintsugi Consulting works with organizations across healthcare, education, government, nonprofit, and corporate sectors to design and deliver disability training that builds real skill rather than rule-memorization. Founder Rachel Kaplan, MPH, is a disability consultant whose practice integrates lived experience, public health rigor, and trauma-informed design.
If you're updating your organization's language conventions, training, or style guide, the Kintsugi Consulting services page outlines training, consultation, and program design offerings. The contact page is the fastest way to schedule a discovery conversation. For comparing internal vs. external delivery options, the in-house vs external disability training providers framework can structure the decision.
Bottom TLDR:
Person-first vs identity-first language is best handled as a relational skill rather than a static policy. Use the discussion guide above with your team — work through history, examples, and ask-then-follow role-plays. Replace blanket "use person-first" rules in your style guide with community-specific guidance and the principle of asking individuals what they prefer. Avoid "wheelchair-bound," "suffers from," and "differently abled" entirely.