Inclusive
Our mission is to protect everyone’s security posture. To do that, our content must be inclusive, respectful, and accessible to a diverse global audience of engineers, analysts, and executives.
Section titled “Our mission is to protect everyone’s security posture. To do that, our content must be inclusive, respectful, and accessible to a diverse global audience of engineers, analysts, and executives.”
Person-First Language
Section titled “Person-First Language”Focus on the individual rather than a condition or characteristic. We prioritize the human element in security.
Guideline: Use person-first phrasing unless a specific community has expressed a preference for identity-first language.
- Correct: “People with disabilities.”
- Avoid: “Disabled people.”
Gender-Neutral Language
Section titled “Gender-Neutral Language”Security is a diverse field, and our language should reflect that. We avoid gendered assumptions in all documentation and UI scenarios.
Guideline: Use “they/them” as a singular pronoun when the gender of a user or adversary is unknown or irrelevant.
- Correct: “Once the analyst logs in, they can view the coverage report.”
- Avoid: “Once the analyst logs in, he can view his report.”
Localization-Friendly Writing
Section titled “Localization-Friendly Writing”Prelude is used by global teams. Our writing must be clear to non-native English speakers and compatible with translation software and screen readers.
Avoid Idioms and Slang: Expressions like “low-hanging fruit,” “hit the ground running,” or “silver bullet” often fail to translate and can obscure technical meaning.
Limit Abbreviations: While “e.g.” and “i.e.” are common, they can be confusing for screen readers and certain translation layers.
- Prefer: “For example” instead of “e.g.”
- Prefer: “That is” instead of “i.e.”
Global Technical Standards: When referencing dates, times, or measurements, use international standards (ISO 8601) to avoid regional confusion (for example, YYYY-MM-DD).
Accessible Technical Content
Section titled “Accessible Technical Content”Inclusivity also means ensuring our technical data is reachable for everyone.
Alt-Text for Technical Diagrams: Every chart, graph, and network map must include descriptive alt-text so users with visual impairments can understand the security insights.
Color-Independent Meaning: Never use color as the only way to convey security status.
- Correct: A red “Critical” badge that includes both the color and a distinct “X” or ”!” icon.
© 2025 Prelude Research, Inc. All rights reserved. Prelude, its logo and other trademarks are trademarks of Prelude Research, Inc. and may not be used without permission.