Inclusive Language in IT

The Research Education Networks Information Sharing and Analysis Center (REN-ISAC) is a community of professionals coming together to achieve a common goal: strengthen the information security structure of higher education. The language we use as a community is important to who we are and how we are perceived. Unfortunately, some IT technical jargon and professional shorthand have highly negative connotations.

For that reason, the REN-ISAC is encouraging our member institutions and member representatives to create a more inclusive professional community by using inclusive language. The following guidelines provide alternatives for problematic words and phrases, especially those frequently used in a professional technology environment.

• Avoiding Ableist Language
• Avoiding Ageist Language
• Avoiding Loaded Terminology
• Pronoun Usage and Gendered Language
• Additional Resources

Inclusive Language is a Process

This document provides suggested guidelines for the language of disability, age, race, culture, gender, etc. The terms and phrases below have been chosen because they lessen the chance for unintended micro-aggressions in a professional setting. We understand, however, that the individuals may have personal language preferences, and no guidance will fit all people and all preferences.

While the REN-ISAC has worked to create a full listing of language alternatives, we readily admit that creating a new, more inclusive professional vocabulary takes time and collaboration. If you have comments, questions, or suggestions, please email us at membership@ren-isac.net.

This document is TLP:CLEAR so please feel free to share with others in your professional community.

When referring to a person with a disability, the best practice is to use the terms preferred by the individual you are speaking or referring to. When preference is unknown or undeclared, use person-first, not ability- or disability-first, terminology.

Often, references to disabilities are used metaphorically to negatively remark on a situation or event, such as “Due to the attack, the system was crippled,” or “Hey, can you do a sanity-check on this for me?” This type of language equates physical, mental, and psychological disabilities with bad or aberrant qualities and thus can be harmful and upsetting. Writing best practices include avoiding disability-based metaphors.

Ageist language shows up quite often in more relaxed technical discourse, especially when the speaker assumes the person’s age tells the speaker something about the person’s technological knowledge. When writing or speaking, avoid ageist terminology like these.

Information technology has a history of using terminology that is loaded with racial, cultural, and gendered bias or words the connote violence. In order to make our organization a more inclusive space for all IT professionals, we suggest using the following replacement guidelines for avoiding loaded terminology.

One of the easiest ways to create a gender inclusive atmosphere at your organization is through thoughtful use of pronouns. When creating content, always use gender neutral pronouns when referring to an unnamed or unspecified person (examples: IoT user, malicious actor, or university student).

• Avoid: Help desk scams tend to target the older technology user because he lacks technology skills.
• Preferred: Help desk scams tend to target the older technology user because they lack technology skills.

When referring to a specific person, use their preferred pronouns when known. Remember, do not assume you know a person’s gender based on their name or outward appearance. Offering up your own preferred pronouns is a good way to signal both your own identity and that your organization is an inclusive space.

• Google Developer Documentation Style Guide
• Microsoft Writing Style Guide
• EDUCAUSE Inclusive Language Guide
• Inclusive IT Language Guide—University of California Irvine