Developer Relations

Developer Advocacy Handbook (13): Talk Checklist


Author: Christian Heilmann
Translation: Zhuang Qi

This is a checklist for speakers to ensure their talk materials are ready for an inclusive, accessible, and actionable talk. It’s based on years of experience speaking at conferences in many different countries to different audiences, with translations and transcriptions. It’s also available online, and you can fork and contribute on GitHub.

Not all of these things are mandatory for every talk, but considering them will make you a better and more relaxed speaker.

Talk Materials

  • Do the slides have a portable format (HTML, PPTX, PDF) and are independent of your computer?

  • Are there code examples online?

  • Is embedded media (video/audio) operating system independent and does it work offline?

Formatting

  • Does all embedded media have accessible alternatives (captions, alt text, transcripts)?

  • Is the font size large enough to be readable (especially in code examples that can’t be resized)?

  • Is the slide format appropriate for the conference (16:9, 4:3…)?

  • Do all slides have enough contrast to be readable even if the projector fails?

  • Have the slides been checked for color blindness issues?

  • Is there a safety margin around the slides to account for projector cutoff?

  • Is the quality of all embedded media high enough to be shown on a big screen?

  • Are there any flickering and fast animations that could cause discomfort for the audience? If so, is there a warning slide?

  • Are there any font dependencies that might require alternative fonts if you can’t present from your computer?

Content

Working Well With Others

  • Have the slides been checked for potentially offensive content? Are you sure you want to tell that edgy joke?

  • Does the talk contain any trigger content? If so, is there a warning?

  • Are there any mentions of third parties or competitors, and could your content be seen as an attack or unfair criticism?

International Audience Considerations

  • Are the slides understandable for an audience without a certain background? Have you avoided relying on metaphors and pop culture references that need explanation to work?

  • Is there a glossary/explanation of technical terms for translators?

  • Is there a transcript of embedded media for translators?

  • Is there a printable version of the talk to give to translators and transcribers?

Secondary Distribution Considerations

  • Can the slides not be misinterpreted when viewed without the context provided by the speaker? Can a screenshot of a single slide be shared without causing confusion?

  • Does all media in the slides have attribution? Has any questionable, potentially copyrighted content been reviewed?

  • Is any third-party content attributed to the correct author?

Tracking

  • Are your slides available for download, and do you have control over who gets them?

  • Is there a call to action at the end of the slides, and are the resources unique and available?

  • Is there a way to track traffic to the resources you mention (shortURLs, tracking IDs)?

Insurance

  • Do you have all materials offline and computer independent (memory stick, including code examples, fonts, and embedded media)?

  • Have you prepared explanations of embedded media in case video/audio doesn’t work?

Additional Options

  • Can you have automatic captions, and will you use them (Google Slides, Powerpoint both require an online connection)? Have you told the conference organizers?

  • Do you want to provide slides to organizers beforehand for translation/modification?

Reprinted with permission: Developer Relations »


Similar Posts

Content icon
Content