Skip to main content

Inclusive Access

The playbook should be usable by people with different levels of technical background, literacy, language, and connectivity. This page guides coordinators on adapting it for diverse audiences.

Adapting for Non-Technical Audiences

Many contributors — annotators, voice recorders, translators — are not researchers. When introducing the playbook to them:

  • Share only the sections relevant to their task; do not link to the full playbook
  • Replace technical terms with plain-language equivalents, or walk through the Glossary first
  • Demonstrate tasks live (screen share or in-person) before asking contributors to read independently
  • Use concrete examples from the contributor's own language and domain

Adapting for Low-Literacy Contributors

  • Convert key instructions into short numbered steps with screenshots or illustrations
  • Offer oral walkthroughs as an alternative to written reading — a coordinator reads through the section and takes questions
  • Prepare a printed quick-reference card (A5, one side) with the most important steps for the specific task
  • Test materials with community members before finalizing — contributors with low literacy often surface genuine clarity problems that polished prose hides

Gender-Inclusive Facilitation

  • Actively invite women and underrepresented participants to contribute examples and ask questions
  • Use training examples that reflect diverse speakers, topics, and perspectives — avoid stereotyped scenarios
  • Offer flexible session timing to accommodate caregiving responsibilities
  • Track participation by gender and adjust facilitation if one group dominates

Multilingual Access

  • Translate the sections relevant to your project before the training session — do not rely on machine translation for consent forms or contributor agreements
  • Maintain a local glossary of key annotation terms in the community's working language
  • Invite a bilingual co-facilitator for sessions where participants have limited English

Offline and Low-Connectivity Access

For contributors working without reliable internet:

  • Use Download PDF in the navbar to get the full playbook as a single file — suitable for printing or sharing via WhatsApp or USB
  • For workshops in low-connectivity venues, pre-download or print only the relevant chapter pages before traveling
  • Ensure the annotation tool being demonstrated also supports offline or low-bandwidth use — see Tooling

When distributing printed copies, note the version number and date on the cover. The live site always reflects the latest version.

Collecting Feedback on Usability

After each training session, ask participants:

  • Was there anything you did not understand after reading the relevant section?
  • Were the examples relevant to your language and context?
  • What would you change to make it easier to follow?

Submit responses to the playbook maintainers — the playbook improves through exactly this kind of community use.

Loading comments…