# Accessibility check list for each format of contribution

# UseR! 2021 accessibility standards for Keynotes

For Keynotes, we kindly ask that prospective presenters:

- [ ] Prefer text-based slides platforms such as markdown or Beamer
- [ ] Avoid transitions, animations, and complicated layouts
- [ ] Add alt-text to images that explain completely the features in the image
- [ ] If you still need to present in MS PowerPoint or similar, keep the original file
- [ ] Add speaker notes to your slides
- [ ] Make available all the materials in accessible formats beforehand
- [ ] If you are giving a Keynote in a language different from English, provide the English transcript beforehand.
- [ ] The slides and other material should still be in English.

## Other reminders

- Speak as clearly as possible, looking at the camera, and try not to go too fast
- Be aware of clues in the chat that signal if your pace is letting everyone follow your instructions
- During the session, comment briefly on what it is that you are showing and why. Avoid explanations that rely only on obvious features that may not be obvious for everyone, such as "As you can see" or "The image speaks for itself"

For more information, check the useR!2021 [Accessibility Standards](https://gitlab.com/user-2021-team/user-2021-global/-/blob/master/diversity/accessibility_standards.md) or contact [user2021-accessibility[at]r-project.org](mailto:[e-mail])

# UseR! 2021 accessibility standards for Tutorial

For tutorial, we kindly ask that prospective instructors:

- [ ] Prefer text-based slides platforms such as markdown or Beamer
- [ ] Avoid transitions, animations, and complicated layouts
- [ ] Add alt-text to images that explain completely the features in the image. Include explanation of how the code relates to the visual output.
- [ ] If you still need to present in MS PowerPoint or similar, keep the original file
- [ ] Add speaker notes to your slides
- [ ] Make available all the materials in accessible formats beforehand

## Other reminders

- Speak as clearly as possible, looking at the camera, and try not to go too fast
- Be aware of clues in the chat that signal if your pace is letting everyone follow your instructions
- During the session, comment briefly on what it is that you are showing and why. Avoid explanations that rely only on obvious features that may not be obvious for everyone, such as "As you can see" or "The image speaks for itself"

For more information, check the useR!2021 [Accessibility Standards](https://gitlab.com/user-2021-team/user-2021-global/-/blob/master/diversity/accessibility_standards.md) or contact [user2021-accessibility[at]r-project.org](mailto:[e-mail])

# UseR! 2021 accessibility standards for Chaired, Parallel Sessions (Regular Talks)

For Chaired, Parallel Sessions, we kindly ask that prospective presenters:

- [ ] Prefer text-based slides platforms such as markdown or Beamer
- [ ] Avoid transitions, animations, and complicated layouts
- [ ] Add alt-text to images that explain completely the features in the image
- [ ] If you still need to present in MS PowerPoint or similar, keep the original file
- [ ] Add speaker notes to your slides
- [ ] Make available all the materials in accessible formats beforehand.
- [ ] If you are giving a talk in a language different from English, provide the English transcript beforehand.
- [ ] The slides and other material should still be in English.

## Other reminders

- Speak as clearly as possible, looking at the camera, and try not to go too fast
- During the session, comment briefly on what it is that you are showing and why. Avoid explanations that rely only on obvious features that may not be obvious for everyone, such as "As you can see" or "The image speaks for itself"

For more information, check the useR!2021 [Accessibility Standards](https://gitlab.com/user-2021-team/user-2021-global/-/blob/master/diversity/accessibility_standards.md) or contact [user2021-accessibility[at]r-project.org](mailto:[e-mail])

# UseR! 2021 accessibility standards for Elevator Pitches

For lightning talks, we kindly ask that prospective presenters:

- [ ] Prefer text-based slides platforms such as markdown or Beamer
- [ ] Avoid transitions, animations, and complicated layouts
- [ ] Add alt-text to images that explain completely the features in the image
- [ ] If you still need to present in MS PowerPoint or similar, keep the original file
- [ ] Add speaker notes to your slides
- [ ] Make available all the materials in accessible formats beforehand

For technical notes, we kindly ask that prospective presenters:
- [ ] Prefer text-based platforms such as markdown or Beamer
- [ ] Add alt-text to images that explain completely the features in the image
- [ ] Make available all the materials in accessible formats beforehand

## Other reminders for oral presentation and Q&A sessions

- Speak as clearly as possible, looking at the camera, and try not to go too fast
- During the session, comment briefly on what it is that you are showing and why. Avoid explanations that rely only on obvious features that may not be obvious for everyone, such as "As you can see" or "The image speaks for itself"

For more information, check the useR!2021 [Accessibility Standards](https://gitlab.com/user-2021-team/user-2021-global/-/blob/master/diversity/accessibility_standards.md) or contact [user2021-accessibility[at]r-project.org](mailto:[e-mail])

# UseR! 2021 accessibility standards for Panels and Incubators (former: Panels and Workshops)

For Panels and Incubators, we kindly ask that prospective organisers of a panel/incubator session:

- [ ] Prefer text-based slides platforms such as markdown or Beamer
- [ ] Avoid transitions, animations, and complicated layouts
- [ ] Add alt-text to images that explain completely the features in the image
- [ ] If you still need to present in MS PowerPoint or similar, keep the original file
- [ ] Add speaker notes to your slides
- [ ] Make available all the materials in accessible formats beforehand
- [ ] If the incubator's goal is to generate an output, the organisers ensure that the output is accessible too.

## Other reminders

- Speak as clearly as possible, looking at the camera, and try not to go too fast
- Be aware of clues in the chat that signal if your pace is letting everyone follow your instructions
- During the session, comment briefly on what it is that you are showing and why. Avoid explanations that rely only on obvious features that may not be obvious for everyone, such as "As you can see" or "The image speaks for itself"

For more information, check the useR!2021 [Accessibility Standards](https://gitlab.com/user-2021-team/user-2021-global/-/blob/master/diversity/accessibility_standards.md) or contact [user2021-accessibility[at]r-project.org](mailto:[e-mail])