GenderMag Design Catalog

(We don't have design examples for this category yet, but we have a checklist!)

Conference Inclusivity Checklist

Version: Febuary 5th 2021.

The following inclusivity guidelines for conference sites have been developed based on Gendermag session evaluations conducted on ASE’19, ICSE’18, ICPC’21.

Landing/Main Page

  1. Add a lot more information about the conference topic.
  2. Make sure the conference logo/image isn’t too big or move it down to the bottom so that it doesn’t take up too much space when first arriving on the landing page.
  3. Make Call For Paper (CFP) available from the landing page.
  4. PC list should be ordered so that it's not all men in the beginning/first viewable half of the page.
  5. Add a link to the “How to submit” page in the landing page (see First Timers).
  6. Change “Tracks” to “Submitting” in the main menu in the landing page (if the drop downs there are about submitting to the different tracks).
  7. Have the main menu items ordered based on temporality of tasks (e.g., first have “Submitting” information instead of “Attending” in the menu).
  8. Track orders should be consistent between the menu and the “How to submit” page.

First Timers

  1. Add a how-to-submit paper page, modeled after the ASE’19 site.
  2. Make sure Acronyms (NIER, JSEET, etc.) are spelled out.
  3. Post sample papers accepted at previous conferences.
  4. Have a section/page geared towards 1st time submitters (e.g. to help decide to attend).
  5. For double-blind instructions, you can use:
  6. Make clear how authors of specific tracks can submit papers (links to the submission site).


  1. In the visa and registration pages, add information about whether the cost of registration would be refunded if visa is denied.
  2. The registration link/button needs to be clearly visible on the screen.

Program (if a large conference like ICSE)

  1. Need some way to help first timers navigate sessions/understand the program in a lightweight way.
  2. Advice on how to create your own program (e.g. instructions for navigation, instructions on how to see what others are favoring).
  3. “Programmer picks”: section of various program committee members saying what they think is going to be particularly interesting at the upcoming site/event.
  4. More structuring for going through the sessions (e.g., filtering through days, session timeline to see session topics at a glance, filtering through tracks, filtering through industry program).
  5. Emphasize session titles and not track type.
  6. Instructions on where to find room (e.g., click on a room and see a map that highlights: location of room? add map to the page?).
  7. A way to filter through different tracks to make it easier to find sessions.
  8. Relate D&I (Diversity and Inclusion) to mentoring/social events (e.g, link to mentoring page as in ICSE’18).


  1. Make sure D&I (Diversity and Inclusion plan) is aimed at population that wants to feel included and not too boilerplate
  2. Have pages organized to facilitate the tasks the user needs to do in that page and not just have to read. Information only text should be condensed.
  3. Multi-step actions (e.g., registration) should have progress bars.
  4. Ability to save data/progress when multiple steps are involved, with this information given at the start of the page.