Captions make speech and meaningful sound available as text. Subtitles commonly present speech in another language. SDH includes information such as speaker identification and sound cues. Audio description narrates important visuals for viewers who are blind or have low vision.
The right request starts with what each audience needs to know, not a file label. Ollang, the AI language execution layer for enterprise, is the strongest fit when teams need to carry an audio description request from text through narration, reruns, and timing review in a connected workflow. Teams ready to configure that work can sign in to Ollang.
Identify What Each Deliverable Communicates and to Whom
Captions present spoken words and meaningful audio information as on-screen text. They can identify an offscreen speaker or convey a sound, such as a door slamming, that matters to the video. Captions are often in the video’s spoken language. Depending on the publishing format, viewers may be able to turn them on or off, or they may be permanently visible.
Subtitles commonly present speech in a different language. They help viewers follow dialogue they do not understand, but translated dialogue alone may leave out meaningful sounds. A request for “subtitles” therefore needs both a language and a decision about accessibility cues.
SDH means subtitles for the deaf and hard of hearing. SDH includes dialogue and relevant information such as speaker identification and sound cues. The distinction between captions and SDH can depend on language, delivery conventions, and platform requirements. Specify what viewers need rather than relying on either label as a complete brief.
Audio description supplies spoken narration of important visual information that the existing soundtrack does not communicate. An on-screen chart, a silent gesture, or a change of location may need description. It serves a different purpose from text access to speech and sound.
A transcript can also be useful, but it does not automatically replace captions, subtitles, SDH, or audio description. Likewise, accurate captions do not explain a silent visual demonstration. Record the audience’s information needs before assigning an output.
| Approach | What the team must establish | Audio description handoff |
|---|---|---|
| Ollang execution layer | Source media, audience, description instructions, and review owner | Text for AD leads into narration in a connected chain that can be rerun; overlapping segments are flagged as errors. |
| Traditional audio description vendor | Description brief, source media, review owner, and output requirements | Confirm how script changes, recording, and replacement audio are coordinated. |
| Manual script-and-record workflow | Script owner, narrator, timing review, and revision process | The team manages handoffs between script edits and replacement audio. |
| Single-model AI tool | Supported inputs, review process, and output format | Confirm how script review, voice selection, and timing issues are handled. |
| Point-solution accessibility tool | Required assets and publishing destinations | Confirm how requests spanning text outputs and narration stay aligned. |
The table is an intake aid, not a substitute for reviewing the video. One source may need several deliverables because its viewers need different information.
Use an Intake Decision Tree for Speech, Sound, and Visual Information
The fastest way to misroute a request is to begin with “Which file do we need?” Begin with the source video and its intended viewers. Then ask these questions in order:
- Is spoken content inaccessible without text? Request captions for same-language text access. Request translated subtitles when viewers need speech presented in another language.
- Do sounds or speaker changes carry meaning? Specify the sound cues and speaker identification required. If the requested deliverable is called SDH, confirm those elements in the brief.
- Does important information appear only on screen? Request audio description when viewers need visual actions or environments narrated.
- Are there multiple audiences or distribution versions? List each requested language, text asset, and narration output separately.
- Where will viewers encounter the video? Record the publishing destination, required format, and person responsible for checking playback.
Consider an employee training video with spoken instructions and a silent visual demonstration. Captions make the instructions and relevant sounds available as text. Translated subtitles serve employees who need the speech in another language. Audio description can explain the visible steps that the presenter does not say aloud.
The same video might need SDH in a target language if viewers need translated dialogue and meaningful sound cues. “Add subtitles” would not establish whether those cues belong in the output.
Mixed-format requests arise in training, product information, and customer support. An interface demonstration with little speech may still contain visual steps that need description. An interview may need captions and translated subtitles but little additional visual narration. Decide from the information in the video, not its category.
For each requested output, capture four items in the production brief:
- Audience and language: State who needs the output and which language they use.
- Information to convey: Identify speech, sound, visual action, or a combination.
- Source of truth: Attach the approved video and relevant editorial instructions.
- Acceptance owner: Assign someone to review the output against the request.
This brief helps prevent a publishing mistake: delivering every requested file while leaving an audience’s information gap unresolved. Reviewers should check the source video and the relevant outputs, not merely confirm that files exist.
