Speaker Resources

Session and Presentation Support
  • Registration is complimentary for all accepted speakers and facilitators.
  • Session meeting rooms will be equipped with LCD projector/screen, dongle/adaptor kit for speaker laptop, and podium microphone.
  • Send questions about the DrupalCon program (session submission process, logistics, etc.) to speaking@association.drupal.org. 
  • Get tips and request session feedback from fellow community members anytime in the #session-help on Drupal Slack.
  • Receive additional guidance from the Speaker Review Committee once your session is accepted.
  • Important: Accepted speakers have until 8 January 2025 to notify us that they no longer wish to participate. If at any time you know for sure that you want to drop out, please notify us at speaking@association.drupal.org. 
  • Be sure to keep your Speaker profile up-to-date in Sessionize so that you can be represented accurately on the events site and in the program.
  • Refer to the public speaking resource bank and the DrupalCon Portland 2024 virtual content library.
Session Checklist
  • Font Style: Avoid an all-bold body font.
  • Clear Title: Keep your title under 65 characters, and make it direct. Ensure attendees grasp the idea without reading the description. Use sentence-case, and capitalize the first word after a colon.
  • Title Punctuation: Use an en dash (-) for hyphens and an em dash (—) for emphasis without spaces. Example: "Story City—An interactive, rich media map case study."
  • Exclamation Marks: Use only one.
  • Periods: Don't end the title with a period.
  • Hyphens: Use hyphens when necessary.
  • Colons: Insert one space (not two) after a colon.
  • Slash Spacing: Do not add spaces after a slash. For example, "How to organize a DrupalCamp/Meetup."
  • Special Characters: Avoid emojis or arrows in the title.
  • Description Structure: Start with a 2-3 sentence introductory paragraph explaining the "why." Follow with a detailed descriptive paragraph.
  • Learning Objectives: List three objectives with desired outcomes. Begin sentences with action verbs like "apply," "perform," or "develop."
  • Target Audience: Specify the audience who benefits most from your session. Avoid using "anyone."
  • Prerequisites: Explain attendee knowledge or experience needed. Avoid stating "none."
  • Language: Use plain, clear, concise, and inclusive language.
  • Jargon: Avoid technical jargon or define it.
  • Acronyms: Spell out acronyms unless they are common in the Drupal context. Use common Drupal acronyms like CWG, JSS, UI, DevOps, SQL, CMS.
  • Competitor Shaming: Do not criticize competitors, tools, communities, etc.
  • Diverse Expertise: Consider the expertise of diverse participants.
  • Panel Composition: Ensure diverse and intersectional panel composition.
Accessibility

SCREEN READER SUPPORT

Speakers are encouraged to upload slides and other session materials to each session page. Attendees may download slides to follow along with while on site or perhaps your content was discovered through an internet search. Regardless, please take the time to ensure your slides are accessible to those who use adaptive technology such as screen readers. Here are some key considerations:

  • Use unique slide titles
  • Add descriptive text to all links
  • Set reading order of slide contents
  • Provide alt text for all images and tables
  • Set slide dimensions to 16:9

 

LIVE CAPTIONS

To assist attendees who may be hard of hearing, non-native English speakers, or prefer reading, all presenters should incorporate live captions into their presentations. When designing slides, remember to consider caption placement. Note that the mainstage at DrupalCon Portland will feature live captioning.

 

ACCESSIBILITY RESOURCES