The language used in the system to describe roles, processes, statuses etc. should conform to any pre-existing vocabulary relating to the tasks at hand.
- Know your audience, and only use language you’re confident they’ll understand
- Use active voice, e.g. say: “please complete all fields” not “all fields must be filled in" - this places the emphasis on the action rather than the object.
- Use pronouns - “you” for the user, “we” to represent the organisation.
Ensure that cultural norms and expectations are considered in the design to make the software accessible and user-friendly for users of any cultural background.
- Proofread content to ensure language is clear and appropriate for a diverse global audience.
- Avoid acronyms that are University specific.
- Use plain language, avoid jargon.
- Avoid gendering in theoretical examples (use ‘they’ rather than ‘he’ or ‘she’).
- Be mindful of terms related to race, ethnicity, nationality and culture.
- Be mindful of medical conditions and ability terms.
- Use person first language. For example, people with disabilities as opposed to disabled people or the disabled.
