layout | title | permalink |
---|---|---|
page |
OpenGates Checklist |
/checklist/ |
A reference checklist of things to help you avoid gatekeeping in your dev posts, articles, videos, talks, presentations, podcasts, sites, and in any other content.
The checklist is not in order of importance. It is broken down into sections to help us understand how each item helps us open gates and avoid gatekeeping.
Jump To:
- Images should vary in age, ability, race, nationality, gender, body types (ref)
- Example names should be different from the status quo (ref)
- Lists of people should not be homogenous (ref)
- Can everyone who might view this to see someone like themselves represented in it? (ref)
- Are any stereotypes being perpetuated? (ref)
- Who is missing or excluded? (ref)
- item (ref)
- Avoid using gendered words and colloquialisms (ref)
- Have you used “man”, or “men” or words containing them to refer to people who may not be men? (ref)
- Have you used “he,” “him,” “his,” or “himself” to refer to people who may not be men? (ref)
- If you have mentioned someone’s sex or gender, was it necessary to do so? (ref)
- Do you use any occupational (or other) stereotypes? (ref)
- Do you provide the same kinds of information and descriptions when writing about people of different genders? (ref)
- Do make use of "they" as a gender neutral option? (ref)
- Avoid cultural appropriation (ref)
- not
Guru→ expert, teacher (ref) - not
Spirit animal→ personal mascot (ref) - not
Pow-wow→ if you meant "meeting", look up some synonyms). (ref) - not
Tribe→ refrain from use, or replace it with a term without appropriation like "close group of friends" (ref) - not
Totemic animal→ refrain from use (ref)
- not
- Avoid culturally offensives terms and phrases
- not
"Indian giver"→ refrain from use (ref) - not
"Too many chiefs, and not enough Indians"→ refrain from use (ref) - not
"Circle the wagons", "Hold down the fort", "On the warpath"→ refrain from use (ref) - not
"Indian giver"→ refrain from use (ref) - not
"Indian time", "Indian summer"→ refrain from use (ref) - not
"Gypped/Jewed"→ scammed, ripped off (ref) - not
"Gypsy"→ refrain from use (ref) - not
"Karma"→ comeuppance (ref coming soon)
- not
- Avoid inspiration porn (ref)
- When discussing a product, indicate what makes it accessible (ref coming soon)
- Avoid ableist language (ref), (ref)
- not
normal→ common, typical, frequent (ref) - not
Crazy, nuts, spaz, insane→ bizarre, enormous, unfamiliar (ref) - not
Sanity Check→ confidence check, temperature check (ref) - not
Moron, idiot→ TBD (ref) - not
Dumb, stupid→ unreasonable, odd (ref) - not
Derpy→ ridiculous, foolish, silly (ref) - not
R_tard*, *tard→ refrain from use (ref) - not
Lame, crippled→ disabled (ref) - not
Psychopath, lunatic, maniac→ refrain from use (ref) - not
Junkie→ aficionado, fiend, enthusiast (ref) - not
Midget→ Use the person's name, short person (ref)
- not
- Have you used medical diagnoses when not talking about actual medical things? (medical appropriation)
- Ensure capitalization of "Black" (ref)
- Avoid racial appropriation (ref coming soon)
- Refrain from digital Blackface (ref)
- Avoid racially offensive terms and phrases
- not
Grandfathering→ legacy, historical (ref) - not
blacklist / whitelist→ block/allow, deny/trust, exclude/include (ref) - not
Master / slave→ primary/replica, trunk/branch, parent/child (ref) - not
Colorblind, "I don't see color"→ refrain from use (ref) - not
Savage, barbaric→ cruel, cold-blooded (ref), (ref)
- not
- Ensure you have used Latina and Hispanic correctly (ref)
- Ensure explanations will make sense to the age of your audience (ref coming soon)
- Avoid assuming in-depth computer knowledge (ref coming soon)
- Avoid ageist language (ref coming soon)
- not
So easy Grandma could do it→ refrain from use (ref coming soon) - not
Entitled [insert generation]→ refrain from use (ref coming soon)
- not
- Warn before discussion/images of triggering/traumatic topics (ref coming soon)
- Avoid using words that make things sound easy (eg simple, just, straightforward, etc). Instead, qualify the difficulty: "This may be easy if you already know [this thing]." (ref coming soon)
- State required knowledge up front. (eg "We're assuming your familiar with concepts a, b, and c") (ref coming soon)
- If concept knowledge is assumed, offer a place to learn those concepts
- Did you include anything beyond basic math (+ - * / )? If so, mention that there is a specific math prerequisite
- Explain things in ways it will be realatable to as many people as possible
- Give things descriptive names. Avoid
x
,foo
,bar
,baz
etc (ref coming soon)- Where single letter variable names are common practice (eg
i
,k
,v
etc), explain what they stand for
- Where single letter variable names are common practice (eg
- Did you say something is simplified? Demonstrate what was simplified (ref coming soon)
- not
normal→ common, typical, frequent (ref)
- Discuss Code of Conduct (CoC) on event pages and in opening announcements (ref coming soon)
- Include event organizer or CoC team contact info if harassment takes place (ref coming soon)
- Have "no photos" stickers available at badge pickup (ref coming soon)
- Have pronoun stickers available at badge pickup (ref coming soon)
- Avoid sexually explicit branding and humor (ref coming soon)
- Designated sensory-friendly quiet space (ref coming soon)
- alcohol should never be the main part of the social hour (ref coming soon)
- Warn before discussion/images of triggering/traumatic topics AND allow people to leave (ref coming soon)
Accessibility is a right. Yes, literally it is the law in some countries. Many of these items will be guided by: Web Accessibility Laws & Policies
- warn for rapidly-flashing lights (ref)
- warn for loud noises (ref coming soon)
- warn for anything that could make someone dizzy (ref coming soon)
- include timestamps for where to skip to to avoid warned content (ref coming soon)
People should be able see and read even with impaired vision
- Images have Alternative Text (ref)
- Tested with Screen Reader (test here) (ref)
- AA or AAA level color contrast ratios (test here)
- Avoid "fancy lettering" and odd capitalisation (ref)
- Include transcripts for audio content (ref coming soon)
- Include subtitles for video content (ref coming soon)
- Don't rely on bold/italics/strikethrough to convey meaning (ref)
- Use
rem
andem
instead of px (ref)
- Keyboard navigation works (ref coming soon)
- Responsive (ref coming soon)
- Works on different devices and browsers (ref coming soon)
- Works with Assistive Technology (ref coming soon)
Arranged in a way that makes sense and use language that most people understand
- Headings used appropriately (ref coming soon)