Inventory the information before writing

Our original teaching example is a short equipment introduction. A presenter explains its purpose, the camera points to a connector and a warning sounds during a demonstration. This is an illustrative scenario. Make three lists: speech, meaningful audio and information communicated only visually. Not every decorative sound needs description; concentrate on information that changes understanding. Then decide which alternative will carry each important detail, rather than assuming a speech-recognition export contains the whole explanation.

Treat captions as more than recognised words

The W3C captions guidance explains synchronised speech and non-speech audio needed for understanding. If our warning sound communicates the result of an action, its meaning should be available to the viewer. Changes of speaker should also be understandable. Do not accept automatic output as the finished delivery: review product names, technical terms, negative statements and timing. A small transcription error can change the meaning of an instruction.

Review translation as a separate editorial task

Turning Turkish dialogue into English requires more than changing a filename. Check that technical terms match the product names used elsewhere on the website. Meaning and negation should survive the division into short readable lines. Present language choices with clear names in the player. Consider whether meaningful audio descriptions also need translation. The presence of two files does not prove that both have been checked; keep a separate review record for each language and version.

Complete the transcript with essential visual details

The W3C transcript guidance explains that a descriptive transcript includes important visual information. If the camera silently points to a connector, copying dialogue alone leaves a gap. Add a necessary description such as the connector being shown on the right side of the housing, without inventing specifications that the material does not establish. Speaker names and section headings can make longer text easier to scan. Put the transcript where visitors can discover it near the video.

Check synchronisation in the actual player

Loading a caption file is one check; displaying readable text at the right moment is another. Inspect lines that vanish before the speech finishes or obscure the demonstrated component. Try the phone layout with player controls visible. Check language switching, pausing and seeking to another section. Verify the file formats supported by the chosen player. Permanently embedded text and a selectable caption track have different consequences, so agree the intended delivery format before exporting everything.

Test silent watching and independent reading

Ask a participant to identify the connector while watching with sound off, then summarise the process using only the transcript. The two tasks may reveal different omissions. Their result is an observation about this content, not a general accessibility certification. In the website handover, preserve the video, caption files and transcript together. For loading and playback decisions, see the separate guide to video that does not block content.

Frequently asked questions

Can automatic captions be published immediately?

Review accuracy and timing first. Technical terms, names and small words that can reverse meaning deserve particular attention.

Does a transcript replace captions?

They serve different purposes. Captions accompany viewing; a transcript can be read independently. Depending on the content, both may be needed.

Sources & further reading

W3C WAI — Captions W3C WAI — Transcripts
Web design & developmentLet’s discuss this service