You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.
Add a new page with instructions for speakers similar to already existing Instructions for workshop leaders.
It should have a public URL but shouldn't be linked anywhere.
Also it should contain this accessibility tip (shortened if possible):
Speakers, describe what's on your slide
We can't see what a speaker shows on a screen. Therefore, we have to rely on description of potential graphs, pictures or other non-textual content provided by someone else. It can be a speaker or a friend/assistant. I think that speaker is a better choice, because eventual chat between assistant and me could be disturbing for people sitting around us.
Now, don't get me wrong. I don't want a speaker to describe exact parameters of a displayed graph or to exactly spell out every line of displayed source code. It is enough to say what is currently shown on a screen and if it is something more complicated, I know that I can investigate it later in downloaded slides if needed.
So my first recommendation for speakers is to try to describe non-textual objects by few sentences if possible. Luckily, most speakers usually do this quite naturally.
The text was updated successfully, but these errors were encountered:
Add a new page with instructions for speakers similar to already existing Instructions for workshop leaders.
It should have a public URL but shouldn't be linked anywhere.
Also it should contain this accessibility tip (shortened if possible):
The text was updated successfully, but these errors were encountered: