# Inclusive language Language that includes everyone: gender, disability and terms to avoid. Section: content Docs: https://nebula.kaluza.com/content/inclusive-language --- These guidelines apply to all content written for Nebula components and Kaluza products. ## Gender Use gender-neutral language throughout. Default to `they/them` when referring to a person whose pronouns are unknown. **Do:** Ask your team lead. They can approve this. **Don't:** Ask your team lead. She can approve this. When asking for pronoun information, use "pronouns" not "preferred pronouns". Pronouns are not a preference. **Do:** What are your pronouns? **Don't:** What are your preferred pronouns? Avoid gendered role language. Use neutral job titles and descriptions. | Avoid | Use instead | |---|---| | Waitress | Server | | Businessman | Businessperson | | Stewardess | Flight attendant | | Mailman | Mail carrier | | Manpower | Workforce | | Man-made | Synthetic, manufactured | | Guys (group) | Everyone, team, people | | Ladies | People, everyone | ## Disability Use person-first language when describing people with disabilities or other characteristics, unless you know someone's preference. **Do:** People with accessibility needs **Don't:** Disabled people Do not use euphemisms like "differently abled". Do not use article-plus-adjective constructions like "the disabled" or "the blind". Do not use "handicap" or "handicapped" to describe a person's disability. Be specific about the need or context. "Deaf" is acceptable when referring to actual hearing loss. Use lowercase unless referring to the Deaf community as a cultural or identity group. Do not imply a person is suffering from a condition. Use "has" or "uses", not "suffers from" or "is confined to". **Do:** Amir uses a wheelchair. **Don't:** Amir is confined to a wheelchair. **Do:** This customer has a visual impairment. **Don't:** This customer suffers from a visual impairment. Avoid age-related descriptors such as "elderly", "young", or "older customer". Use a specific age or describe the eligibility criterion directly. **Do:** Customers aged 75 and over are eligible for this support. **Don't:** Elderly customers are eligible for this support. When referencing medical or mental health conditions, for example, in PSR or vulnerability contexts, describe the need rather than the condition. **Do:** This customer has a medical dependency on powered equipment. **Don't:** This customer is severely ill and relies on medical equipment. ## Ableist language These terms use disability or impairment as a negative metaphor. Avoid them. | Avoid | Use instead | |---|---| | Crazy, insane, nuts | Unexpected, unusual, significant | | Blind to, blind spot | Unaware of, gap in | | Dumb, stupid | Unclear, unhelpful | | Crippled, paralysed | Unavailable, blocked | | Sanity check | Check, review | | Tone-deaf | Inconsiderate | | OCD (casual use) | Organised, thorough | Words related to disability are not inherently negative. Terms like `view`, `see`, `enable`, `disable` are acceptable when accurate. Avoid using `disabled` to imply a broken or negative state, prefer `unavailable`, `turned off`, or `inactive`. ## Terms with cultural or racial history These are in common tech use but carry cultural or racial history that makes them exclusionary. | Avoid | Use instead | |---|---| | Whitelist | Allowlist | | Blacklist | Blocklist, denylist | | Black hat, white hat | Unethical hacking, ethical hacking | | Master/slave | Primary/secondary | | Grandfather clause | Legacy, exempt | | Grayed out | Unavailable, locked, turned off | | Guru, ninja, wizard | Authority, expert | | Pow wow | Meeting | | Spirit animal | Role model, inspiration | | Death march | Futile undertaking | ## Idioms and colloquialisms Avoid idioms, metaphors, and colloquialisms. They reduce clarity, do not translate well, and can have cultural or racial origins that make them exclusionary. Avoid assumptions about ability or ease of use. Do not imply that something is difficult or simple. ## Related - [Content guidelines](/content/basics)