Skip to content

Flagship walkthrough video scripts

Production-ready scripts for the three flagship product walkthrough videos. These are internal production artifacts (they live in docs/admin/, not the published help center). Once produced, the finished videos + transcripts get embedded in the matching help pages (Phase 3).

One script per documented product (the seven help-center product sections).

ScriptProductHelp pageTarget
pdf.mdTheAccessiblePDFpdf/getting-started~90s
orgchart.mdTheAccessibleOrgChartorgchart/getting-started~90s
audit.mdTheAccessibleAuditaudit/getting-started~90s
acr.mdTheAccessibleReportCardacr/getting-started~90s
worksheet.mdTheAccessibleWorksheetworksheet/getting-started~90s
workshops.mdTheAccessibleWorkshopworkshops/getting-started~75s
html.mdTheAccessibleWebhtml/getting-started~90s

Product names are the canonical single-token names β€” use them verbatim in voiceover, on-screen text, and the end card. See the name table in the root CLAUDE.md.

Accessibility requirements (non-negotiable)

We sell accessibility β€” our own videos must model it. Every video ships with:

  • Synchronized captions (sidecar .vtt) and a full text transcript linked next to the embed. The transcript is the β€œVoiceover transcript” section in each script.
  • Integrated audio description. The narration itself describes the on-screen action (β€œwe drag the box onto the new manager”) so no separate AD track is needed. Never say β€œclick here” / β€œas you can see.”
  • No flashing content more than 3 times per second (WCAG 2.3.1). Avoid hard cuts to full-screen white; use short cross-fades.
  • Readable on-screen text: β‰₯ 24px equivalent at 1080p, AA contrast against its background, on screen β‰₯ 2 seconds.
  • Not color alone (WCAG 1.4.1): pair every status cue (pass/fail, severity) with a label or icon.
  • Show both input methods where a flow supports them β€” pointer and keyboard β€” so keyboard users see themselves in the product.
  • Respect reduced motion: keep camera/zoom moves gentle; no rapid parallax.

Production spec

  • Format: 1920Γ—1080, 16:9, 30fps. Master with burned-in captions off; ship a toggleable .vtt sidecar plus a burned-in variant for social.
  • Length: 60–90s. Tighten VO to fit; never speed up captions past a comfortable reading rate.
  • Brand: TheAccessible.Org logo bug bottom-right; canonical product name in the end card with its URL.
  • Data: use realistic but synthetic sample data β€” never real customer names, emails, or documents. No dev watermarks or error banners on screen (see the org-chart fixture-screenshot lesson in user-docs-site.md).
  • Audio: VO leveled to about βˆ’16 LUFS; music bed βˆ’6 dB under VO or none.

Shot-list format

Each script has a shot list (Scene / Duration / Visual + on-screen action / Voiceover / On-screen text) followed by the clean Voiceover transcript used for the caption file and the help-page transcript.