Planning accessible demonstrations for different technical abilities
Your audience includes people who have used the product for years and people who opened it for the first time last week, and a single demonstration will lose one group.
The short answer
Plan each demonstration for a stated level, and say the level in the programme so attendees choose for themselves. Then brief the presenter on pacing, on describing what they do as they do it, and on a fallback if the live demonstration fails.
Accessibility needs such as screen visibility, captions or alternatives to a live demonstration should be asked at registration and passed to the presenter and the venue. Ask your accessibility adviser and venue what applies. The event team coordinates the questions and records the answers, and does not decide what is compliant.
Name the level of each demonstration
Mixed-level demonstrations often please nobody. Label each session with who it is for and what they will be able to do afterwards.
Three levels are usually enough: first steps, everyday use and advanced techniques. Attach prerequisites, such as having used a specific feature, so attendees can choose with confidence.
| Level | Audience | Demonstration approach | Check before the session |
|---|---|---|---|
| First steps | New or occasional users | One task, slow pace, every action spoken aloud | Does the presenter avoid jargon and shortcuts without explaining them? |
| Everyday use | Regular users | Two or three linked tasks, short tips, time for questions | Is there a handout or notes people can use later? |
| Advanced | Experienced users, administrators, developers | Complex scenario, trade-offs, limits of the product | Are prerequisites stated in the programme? |
Make the demonstration followable
- Ask presenters to say what they are doing and why, not only to show it. This helps people who cannot see the screen clearly or are following by audio.
- Increase interface and font sizes on the presentation machine and check legibility from the back of the actual room.
- Pause between steps, and avoid moving fast between windows or pointing at the screen without naming the item.
- Prepare a slide or sheet with the key steps so people can catch up if they lose the thread.
- Plan a recorded or screenshot version of the sequence for the case where the live demonstration fails (see the technical sign-off questions).
Accessibility needs: questions, not conclusions
Do not decide for attendees what they need. Use the registration form to ask, and use the accessibility requirements intake to record requests and route them to the right person.
Questions about whether the venue, the screens or the materials meet a standard belong to qualified advisers and the venue. The accessible stage questions show how to ask.
- Is live captioning available for demonstration sessions, and who orders it?
- Can the screen be seen from every seat and from the wheelchair spaces? Ask the venue to confirm in writing.
- Can slides and handouts be provided in advance in an accessible format, and by whom?
- Does the presenter need to describe on-screen content aloud for those who cannot see it?
- Are there quiet or seated alternatives for people who find a crowded demonstration area difficult?
Presenter briefing and rehearsal
- Send the presenter the level, audience description and time limit with the speaker session brief.
- Ask for the demonstration data and accounts at least a week ahead so a rehearsal can be run.
- In rehearsal, check pace, readability and what happens if a step fails.
- Agree how questions are taken, in the session or at a table afterwards, and who runs the queue.
- For hands-on follow-up, see coordinating software labs with conference operations.
Common failure points
- A demonstration labelled for everyone that suits only the presenter's own level.
- Text on screen too small for the back rows, discovered on the day.
- A live demonstration that depends on connectivity nobody tested.
- Accessibility requests collected and then not passed to the presenter or the venue.
- Questions taken only from the front of the room.
Worked example · Fictional example
A fictional procurement-software demonstration track
Fictional organisation and figures, for illustration only.
Belian Pro, a fictional procurement-software company, runs six demonstration sessions across a one-day user conference for 280 attendees. The first programme lists them all as Product demo.
The event owner relabels them as two first-steps sessions, three everyday-use sessions and one advanced administrator session, with prerequisites stated. Registration asks about access needs, a request for live captions is passed to the venue and a captioning supplier, and presenters are asked to rehearse once with enlarged interface settings and recorded fallback clips.
Use this yourself
Demonstration planning table
Copy one row per demonstration and complete each column before the programme is published.
| Session | Level and prerequisites | Presenter | Fallback if live demo fails | Access questions passed to venue or adviser | Handout in advance? |
|---|---|---|---|---|---|
| Name and time | First steps, everyday or advanced | Name | Recording or screenshots | Captions, screen visibility, seating | Yes or no, with format |
Handle it in-house, or bring in help?
Your team can usually handle this when
- One or two demonstrations in a room the team knows well.
- Presenters are experienced and already work at a deliberate pace.
- Access requests are few and can be handled by one person.
Outside planning help earns its fee when
- Many demonstrations across rooms with different levels, presenters and screens.
- Access requests must reach presenters, the venue and suppliers consistently.
- Rehearsal, fallback clips and handout deadlines need tracking across many speakers.
Need the demonstrations briefed and tracked?
A conference project lead can set the level labels with your product team, send presenter briefs, track rehearsal and fallback materials, and make sure access requests reach the venue and your advisers with a recorded answer. Compliance judgements and technical production stay with qualified specialists.
Questions organisers ask
Should we simply run one demo for everyone?
Only for a small group with similar experience. For mixed audiences, labelled levels usually serve people better.
Can the event team confirm that a demonstration is accessible?
No. The event team collects requests and questions and passes them on. Ask your accessibility adviser and the venue what applies.
What if a live demonstration fails?
Prepare a recorded or screenshot sequence beforehand and agree who decides to switch.
How early should handouts be ready?
Ask presenters for materials by a fixed date so they can be shared in advance and in the format attendees need.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.