SPEAKER RESOURCES

Accessibility & inclusive delivery

Make technical knowledge understandable and usable for more people.

PRACTICAL SPEAKER GUIDE

This guidance helps you prepare. Final program decisions and individual arrangements are confirmed by the Open Source Week organizing team.

01

Design accessible slides

Use strong text/background contrast, readable font sizes, clear headings, and uncluttered layouts. Do not rely on red versus green alone to convey status. Label charts directly and provide meaningful alternative text when distributing digital materials.

Practical example / takeaway

Replace β€œthe red line shows the problem” with β€œthe error rate rises sharply after deployment.”

02

Explain visual information aloud

Describe the conclusion of charts, diagrams, and demonstrations rather than saying β€œas you can see.” When presenting code, explain the goal and result, not just the keystrokes. Expand acronyms at first mention.

Practical example / takeaway

For a complex diagram, describe the main components and how information flows between them.

03

Make spoken content easier to follow

Speak into the microphone at a measured pace. Pause after important points. Repeat audience questions before answering. Avoid talking while facing the projected screen. If using video, prefer captions and avoid relying on audio alone.

Practical example / takeaway

Provide a brief verbal recap before moving to the next topic.

04

Plan inclusive participation

Offer more than one way to participate when possible: spoken questions, written questions, or short reflection time. Avoid assuming every attendee has a laptop, reliable connectivity, or advanced technical background.

Practical example / takeaway

For workshops, explain required software and prerequisites in advance.

05

Prepare shareable materials

Use descriptive links rather than β€œclick here,” meaningful document headings, accessible PDF exports, and text equivalents for essential visual information. Remove private information from handouts.

Practical example / takeaway

Check the reading order of exported PDFs and the contrast of diagrams.

06

Ask rather than assume

Accessibility needs vary. Invite participants to communicate requirements through the event organizers and follow the team’s confirmed arrangements. Do not promise captioning, interpretation, or assistive services until they are arranged.

Practical example / takeaway

The objective is thoughtful preparation and clear communication, not guessing anyone’s needs.

Continue preparing

Explore the other speaker guides or return to the main centre.

Speaker Centre β†’