Slides are not speaker notes pasted onto a screen. Use them for diagrams, examples, comparisons, demonstrations, and key phrases the audience needs to hold. Keep contrast strong, type large, and visual hierarchy obvious. Caption meaningful video, describe important visuals aloud, and provide an accessible resource afterward.
What you will learn
- Create a clear slide system
- Design demos for learning
- Improve accessibility and mobile readability
Core concepts
One visual job: A slide should orient, explain, compare, demonstrate, or prompt action. If it does none of these, the presenter can probably say it without a slide.
Progressive disclosure: Reveal complex diagrams in meaningful steps so the audience knows where to look.
Accessible redundancy: Do not rely on color, sound, or a tiny visual alone. Use labels, narration, captions, and a readable handout.
The practical method
- 01
1. Create the visual language Choose type sizes, colors, diagram shapes, image treatment, and spacing once.
- 02
2. Storyboard before polishing Use simple boxes for every slide and test the teaching arc first.
- 03
3. Simplify screens Remove paragraphs, decorative charts, and interface details not needed for the decision.
- 04
4. Script the demo path Use clean data, stable accounts, hidden notifications, zoomed interfaces, and a recorded backup.
- 05
5. Test real conditions Review on a laptop and phone through the event platform, not only in presentation software.
Worked example
A dashboard demo is unreadable in the webinar recording. The presenter replaces the full interface with a three-step diagram, then opens only the relevant report at 150% zoom. A captioned backup clip covers the same path if the live account fails.
Build the template
- Slide visual rules
- Storyboard
- Demo script and clean data
- Caption and narration checklist
- Mobile screenshot review
Quality checklist
- Slides support rather than duplicate speech
- Type is readable
- Color is not the only signal
- Videos are captioned
- Demos have backups
Failure drill
The accessible replay does not fix an inaccessible event
The case
Registration opens without an accommodation field. Slides use small screenshots, live captions are unassigned, and the producer plans to correct the transcript two days later. An attendee who relies on captions cannot follow the live demonstration.
Your call
- What must be decided before registration opens?
- Which access needs require a named owner during the event?
- What equivalent should exist when a visual carries the meaning?
Reveal a defensible response
Response: Treat access as part of production from invitation through replay. Ask for accommodations, test captions and keyboard paths, describe meaningful visuals, share usable materials, and assign someone to watch access failures live. A corrected recording does not replace equal access to the event itself.
Lesson progress
Finished this lesson?
Save your place on this device so it is easy to pick up where you left off.
Not marked complete yet.
Build it in practice
Turn the lesson into a working system.
Use Spacebrain to implement the next step in one connected workspace.