Improving diversity and inclusion at tech (and other) events

Over the years I’ve attended and organised various conferences, hackathons, and other events, and it’s been interesting to observe the ways in which each of them handle (or don’t handle) diversity.

This post is a collection of notes and pointers about the things I’ve noticed are some of the most important things to help increase diversity at events. When I say diversity, I’m largely referring to the diversity of the attendees at events. People from different walks of life, backgrounds, races, genders, abilities, etc.

Being inclusive at our events is important. If our events only have homogeneous attendees, the things they focus on will only be relevant to those attendees, and not useful to anybody else. As it turns out, not everybody is a neurotypical able-bodied heterosexual middle-class cisgender white male. Those of us who do fit or approximate this description often aren’t aware or appreciative of the issues experienced by anybody different from ourselves.

So, in no particular order, how do we improve diversity? This is by no means an exhaustive list, and there will be things I’ve missed, and perhaps some mistakes. Please check out the references section for more information. There’s also a summary at the end. (EDIT: The summary is also available as a lightning talk.)

Race

Be sensitive to and aware of non-white attendees. Ensure you call out racism in your code of conduct, and that you consider how you can be inclusive of and do outreach to various races and indigenous communities.

Accessibility

Have accessible venues. This means ensuring that all the important areas of your venue, including common areas, theatres, bathrooms and stages (speakers can have disabilities, too, and may have lots to say about them!) are wheelchair accessible.

If you think you may have people with visual or hearing disabilities at your events, consider a sign-language interpreter, or having a hearing-aid loop, so that these people can be involved in presentations too, and encourage presenters to be cognisant of this when making their slides (not assuming everybody can see what their slides say, for example).

Additionally, speakers should be mindful of using ableist language, or abusing terms like “OCD” to mean “fussy,” for example. Ensure your website is accessible for people with screen readers etc.

Dietary requirements

Ask for people’s dietary requirements upon registration for your event. You could have a set of check-boxes for things like vegetarian, vegan, gluten free, lactose free, FODMAP, etc. but regardless of whether or not you do this, you should include a dietary requirements free text field for people to explain the nuances of their situation; don’t assume they’ll fit into your boxes; people are complex.

Gender

There are more than 2 genders, and we want to be inclusive of them all. That means that beyond making our events more accessible to women, we should also be inclusive of trans, non-binary, and gender-non-conforming folks. This should include, wherever possible, gender neutral bathrooms.

If your event will have name badges, and you want to give attendees input into what goes onto their name badge, then instead of permitting a “Twitter handle” text box, have a “free badge text; use for Twitter handle, pronoun, GitHub profile, or whatever you like” field. The mention of pronoun here demonstrates to attendees that you acknowledge people’s pronouns may not match how they look (a femme presenting person may not use she/her/hers pronouns), and improves inclusion.

If you need to ask for gender ensure you allow a free-text field to specify their gender. Again, they may not fit in your boxes. Ask, though, why you are asking for gender? Identifying diversity (e.g. how many non-men do we have at this event) is a valid reason. An argument people have made in the past is that a free text field could result in: man, male, boy, masculine, guy, woman, girl, lady, female, trans man, trans woman, unspecified, etc. This is obviously a bit tricky to aggregate for statistics, so one option is to offer an auto-complete text field that auto-completes to “female” when the user starts typing “f” or other words, for example. This encourages users towards labels that make statistical aggregation easy for you, but lets them break out of your boxes if they wish, and type what they like.

Additionally, “unisex T-shirts” are not unisex. Unisex shirts are not designed properly to fit people with breasts or differently shaped chests. If you’re offering T-shirts, offer women’s cut shirts as well as unisex/men’s cut shirts. This may also mean thinking carefully about the design you print on your shirts to ensure the design looks good on people with larger chests, and that the design isn’t distorted etc. Consider subtle and unintentional use of gendered language, such as words like “guys.”

Names

Not everybody has a first name and a last name. Some have mononyms, other cultures display the family name first. When asking for people’s names on your registration form, have a single field for somebody’s full name. Don’t split it up. Ever. If you want a short or informal name (what we westerners may usually use a first name for), have an additional field for “informal form of address”, and explain this may be used for address in newsletters etc., so people have a context through which they can decide how to be addressed.

Socio-economics

Not everybody will be able to afford to come to your event. People from low socio-economic backgrounds may want to come, and have useful and interesting input and perspectives. We can’t afford to exclude these people. Offer grants or sponsorships to people who can’t afford to attend but wish to.

Childcare and youth programs

Some potential attendees will have children. Offer childcare or youth programs. Childcare is not hard to do, and demonstrates your desire to make your events family-friendly.

Newbies

Going to a new event can be scary. Include details on your event’s website that are easy to find and explain what to expect for your event, possibly offering a contact of whom additional questions can be asked. Once at your event, ensure that newbies are overtly welcomed, and that contempt culture is discouraged.

Code of Conduct

Have a code of conduct. There are plenty of great CoCs available (some of which I’ve mentioned in below in the references) off which you could base yours. It should include consequences for breaches, and details for who to contact if people feel unsafe or need to report an incident.

Summary

Additional references and further reading

See Carina C. Zona’s talk called “Schemas for the real world” for information on how to ask for information from users without squeezing them into boxes into which they don’t feel they fit. Check out the Django Community Code of Conduct, the Hopper Fund’s guide to improving conference diversity, the Geek Feminism anti-harassment policy, and the anti-harassment policy developed by the Ada Initiative.

Regarding inclusive language, the Australian National LGBTI Health Alliance has an excellent guide to inclusive sex and gender diverse language. Feel free to extrapolate the guidelines for size, ability, education and ethnicity. The Australian Network on Disabilities also has a guide to inclusive language you might want to look at.

 

Author: mattcen

Linux sysadmin/advocate, @scoutsvic leader, @okfnau, bisexual/polyamorous geek. He/him. Opinions mine. PGP: DB91 CFEF 322D C608 385F 563C 2F88 1AC6 4A16 1033

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s