Identity-first language

Identity comes first grammatically

“Autistic child,” “autistic adult,” and “disabled person” are identity-first constructions. Supporters may use them to express pride, community membership, and the view that autism shapes experience rather than sitting apart from the person.

Identity-first wording can be neutral and affirming. Tone, context, surrounding claims, and respect still matter. A preferred adjective never licenses stereotypes or assumptions about support needs.

Preferences vary within the community

The NIH autism style page says some people prefer person-first language while others prefer identity-first language. The separate NIH person-first and destigmatizing-language guide recommends asking when possible.

A 2025 systematic review included 19 online studies with 6,350 autistic adult participants. Ten of 14 studies assessing a top preference found more participants favored identity-first language, while person-first endorsement and no-preference responses remained substantial. Samples represented limited portions of the autism spectrum, and language and culture influenced results. A group trend cannot answer for one person.

Ask with a usable question

Try: “Which words would you like us to use when we talk or write about autism?” Offer examples only when helpful. Accept identity-first, person-first, both, neither, or context-specific preferences.

Ask the person directly through their communication method. A caregiver can share history or support access while leaving the person’s preference authored by the person whenever direct input is possible.

Group language needs a declared approach

When writing about several people, a publication may use identity-first language, alternate forms, or follow a community advisory group’s choice. State the convention briefly and avoid implying unanimity. Quote individuals with their own terms and preserve context when a source uses official diagnostic wording.

Translation requires another check. A preferred construction in English may feel different or lack an exact equivalent in another language. Ask a qualified language partner and the person instead of translating the word order mechanically.

Record preference where people will see it

Place the chosen wording in a respectful, role-appropriate field used by clinicians, intake staff, educators, and communication partners. Avoid burying it in a long note.

Record who expressed the preference, the date, the settings it covers, and any distinction between private conversation, clinical documentation, school, work, or public writing. Recheck during review rather than treating it as permanent.

Privacy also matters. A language preference never authorizes disclosure of diagnosis or disability. Confirm which audiences may receive that information and under what valid route. Someone can prefer “autistic person” among trusted people while declining any autism reference at work, school, or in public material.

A fictional intake example

Jordan types “autistic adult” in an accessible intake form and chooses identity-first language for conversation and records. The coordinator repeats the preference back for confirmation and enters it in the shared communication field.

Across six documents due that month, five use Jordan’s recorded wording. Preference fidelity is 5 of 6, or 83.3%. The sixth is corrected with Jordan’s knowledge. This measure tracks documentation practice, not respect as a whole.

Correct errors without making the person teach

When someone uses the wrong term, a brief correction is enough: “Jordan uses autistic person.” Update templates or copied text that caused the error. Repeated mistakes call for a workflow fix rather than repeated explanations from the person.

Families may use different language for themselves. Respect each person’s preference and avoid turning terminology into a loyalty test. A young person’s choice can differ from a parent’s wording.

Language carries no diagnostic or clinical conclusion

Identity-first wording says nothing about diagnosis validity, intellectual ability, speech, AAC use, independence, support needs, prognosis, or treatment choice. Describe concrete strengths and support needs separately.

The CDC autism signs and symptoms page describes autism-related characteristics and variation. It serves as the manifest starter rather than a terminology rule.

Use direct language about access

Avoid euphemisms such as “special abilities” when a clear disability or accommodation term better serves the person. Say what support is needed: quiet space, AAC access, written instructions, extra processing time, mobility access, or help with a transition.

Respectful language works best when paired with respectful action. Using “autistic person” while ignoring communication, consent, pain, or accommodation preferences misses the purpose.

Build correction into ordinary quality review. Sample current documents due in a defined period, keep every eligible item in the denominator, and fix template defaults that override the person. Pair document accuracy with direct feedback, since a percentage cannot reveal whether interactions feel respectful.