Inclusive language
Create experiences that fit everyone and avoid unnecessary barriers.
Design principles for inclusive language
Inclusive language isn't about memorizing a list of "good" and "bad" words. It's an approach to writing that avoids assumptions, challenges stereotypes, and treats every person with respect.
Don't make assumptions about abilities
Avoid phrasing that assumes how someone experiences Davidnet. Claiming that a feature is "easy," "simple," or "quick" is imprecise and can alienate users who navigate the interface differently.
Alternative text helps people who use assistive technology interact with images.
Alternative text helps people with visual disabilities interact with images.
Avoid metaphors and idioms
Metaphors and idioms are non-literal phrases that can confuse non-native speakers, screen-reader users, and neurodivergent readers. Stick to clear, literal language.
- Metaphors compare unrelated things (e.g., "like a fish out of water" ).
- Idioms have meanings you can't deduce from the individual words (e.g., "between a rock and a hard place" ).
We couldn't save your changes. Check your connection and try again.
Looks like we hit a snag! Your changes are stuck between a rock and a hard place.
Describe people accurately and respectfully
Ignoring human differences can reinforce societal prejudices. Mentioning race, ethnicity, disability, age, class, gender, or sexuality is appropriate when relevant—as long as it isn't discriminatory.
- Use broad terms like "people of color" only when you lack the context to be more specific.
- Avoid euphemisms meant to make differences sound "positive." Terms like "differently abled" or "handi-capable" are patronizing and erase real experiences.
- Use they/them pronouns and gender-neutral phrasing when referring to a generic user in UI copy.
When a member joins your workspace, they will receive an email invite.
When a member joins your workspace, he or she will receive an email invite.
Write accurate content, links, and alt text
Clear, descriptive labels reduce cognitive load for everyone and are essential for assistive technologies.
- Include meaningful alt text: If an image conveys information, describe it accurately without being overly wordy. Use identical alt text when the same visual appears multiple times.
- Keep repetitive elements concise: For recurring iconography, keep descriptions brief so screen-reader navigation stays smooth.
- Match visual labels with accessible names: Don't artificially shorten visible button or link text while hiding the real context inside
an
aria-label.
View Davidnet billing settings
Click here
Gather form information thoughtfully
Rigid form fields often fail to reflect real-world diversity and can lock people out of using Davidnet.
- Only ask for what you need: Avoid asking for personal details like gender, pronouns, or titles when they aren't necessary for Davidnet to function.
- How to call users: Call them by display name or genderless pronouns such as they and them etc.
- Avoid pre-selected defaults: Setting a default group or category implies it is the "norm" and forces others to do extra work.
Ask for a single Display name or Full name without titles or unnecessary personal fields.
Require Title (Mr./Mrs.) , First name , Last name , or unrelated profile fields.