Why Use Inclusive Language?

Language is an important element in designing and developing applications that are inclusive. SAP supports a culture of diversity and inclusion that is free of stereotypes and discrimination. We strive to use unbiased language when referring to people of all ages, cultures, ethnicities, beliefs, genders, and abilities, including in our products and documentation. Over time, we also work to address existing cases of noninclusive language in our products and documentation, wherever it's possible to do so.

Using inclusive language in our products and documentation is part of SAPs commitment to valuing diversity and inclusion. Learn more at Diversity and Inclusion at SAP.

Term List

We update this list when we encounter new terms to evaluate. For some terms, we provide guidance on acceptability of a term when it's combined with another term (compound terms). For example, while we find that some uses of the term "white" carry noninclusive connotations (for example, "whitelist"), other compound terms that include "white" don't carry noninclusive connotation (for example, "whitepaper").

abort

Avoid "abort" when used to denote stopping a running operation that is partially completed. Possible replacements: terminate, stop, cancel, pause, suspend.

agnostic, -agnostic

Acceptable for describing something that's generalized in order to be interoperable or compatible with various systems or devices.

blacklist/black list

Avoid "blacklist", as well as any compound words containing "black" that denote something bad or negative, such as black rating. Possible replacements: blocklist, exclude list, avoid list.

Examples of acceptable terms that include "black": blackout period, blackbox testing.

execute

Use with caution. Avoid "execute" when you can use "start", "launch", "run", "perform", or "do".

“Executable file” and “executable code” are acceptable to use.

final solution

Avoid "final solution", as well as any compound words containing "final solution", such as "final solution walkthrough". Possible replacements: solution, complete solution, end-to-end solution.

gender terms

Where possible, use gender-neutral forms that include people from all genders, or rephrase. Strive to adhere to the following guidelines:

Option	Acceptable Examples
Use gender-neutral nouns where possible.	chairperson, business executive, workforce, person days, working hours
Address the user directly with an imperative form or with “you”.	After 6 months, you'll be required to change your password. [Note: Could also be “… the password.”]
Use the third person in the plural (“they”, “their”, “them”).	Users must enter a password. They need to remember that password for the next page.

grandfather

Avoid "grandfather", "grandfathered", and "grandfathering" to communicate conditions or requirements that are retained or carried over from previous or obsolete systems, for example, "grandfather clause". Possible replacements: exempt, legacy.

gray, grey

Avoid in compound terms that denote an area between good (white) or bad (black), such as gray rating.

kill

Avoid "kill" to denote putting an end to a process. Possible replacements: stop, exit, cancel, end, force quit, force close.

master

Avoid "master" when used to denote the dominance of one object over another (for example, master server, or master database), or for an object that copies are made from (for example, master report). Possible replacements: leading, primary, source.

For guidance on compound terms that include "master", see Compound Terms That Include "master".

purge

In review. If possible, consider avoiding.

see

Acceptable in cross-references (for example, "see Topic A"), where "see" has the wider meaning of "refer to". Acceptable in other contexts in which "see" doesn't denote visual perception.

Avoid "see" as the sole means of perceiving something onscreen. For example, avoid saying "If you see a message...". Instead, say "If a message appears...".

slave

Avoid "slave" when used to denote the subservience of one object to another (for example, slave server), or for a copy of an object. Possible replacements: subordinate, secondary, replica.

stakeholder

Use with caution. Avoid "stakeholder" when addressing certain indigenous peoples. Possible replacements: interested parties, partners/collaborators, or specify who they are when possible.

trigger

Use with caution. Acceptable for describing why a secondary workflow event occurs. For example, when a user performs one action and the system then initiates, or "triggers", a planned follow-up action.

Avoid "trigger" when you can use "initiate", "launch", "perform", or "run".

whitelist/white list

Avoid "whitelist", as well as any compound words containing "white" that denote something good or positive, such as white rating. Possible replacements: allow list, include list, prefer list.

Examples of acceptable terms that include "white": white paper, whitebox testing, whitespace.

Additional Information

• Making the Software Industry a Little More Inclusive