A video is not accessible simply because it has subtitles. People may also need accurate captions, a transcript, descriptions of important visual information and controls they can operate without a mouse.
Whether you publish a training video, webinar, product demonstration or social media clip, accessibility works best when it is planned before filming. The aim is for people with different hearing, vision, motor and cognitive needs to access the information—not merely for the video to reach more viewers.
This guide explains eight practical steps, the difference between common accessibility formats and how to check your work before publishing. The requirements depend on the type of media and the applicable accessibility standard or policy.
The short answer
To make a video more accessible, plan for accessibility, provide accurate captions, offer a suitable transcript, describe important visuals, use an accessible player, make on-screen text readable, consider sign language and other languages, and test the finished video. The W3C's media accessibility guidance is an authoritative starting point.
Plan for accessibility before recording
Accessibility decisions made at the scripting and storyboard stage are easier to carry through than fixes added after release. Decide who needs access to the content, where it will appear and which accessibility formats are relevant to the video.
Ask speakers to identify themselves clearly, explain essential charts aloud, leave space for captions and avoid relying on colour, position or images alone to convey instructions. Record clear audio with limited background noise and prepare a script or outline that can become the basis of captions and transcripts.
Instead of saying “Click the green button on the right,” say “Select the button labelled Submit application.” The instruction remains meaningful when the video is heard without being seen.
W3C recommends planning accessibility at the start and identifies different requirements for prerecorded, live, audio-only and video-only content.
Add accurate, synchronised captions
Captions give viewers access to spoken dialogue and meaningful non-speech audio. Good captions also identify speakers when needed and convey sounds such as a door closing, laughter or an alarm when those sounds matter to understanding the scene.
Synchronise captions with the soundtrack and review automated caption drafts against the recording. Check names, accents, specialist terminology, punctuation, timing, reading pace and whether captions obscure important on-screen content.
Speaker: “Please evacuate the building.” Sound cue: [alarm sounding]. The cue explains important information for someone who cannot hear the audio.
Closed captions can generally be turned on or off; open captions are always visible. “Subtitles” is also used for same-language captions in many regions, so the label alone does not tell you whether meaningful sound cues are included. W3C explains accessible captioning in more detail.
Provide a transcript people can read and navigate
A transcript is useful for people who cannot hear the soundtrack, people who prefer reading, and visitors who need to search, quote or revisit information. It should contain the spoken material and important non-speech audio, not just a shortened video summary.
For videos where visuals carry essential information, create a descriptive transcript that also explains those visuals. Use meaningful headings, speaker labels and links where appropriate; publish it as accessible text near the video rather than only as a picture of text.
Narrator: “Sales increased during the year.” Visual description: “A bar chart rises from 12 to 18 million pounds between 2024 and 2025.” The description communicates information otherwise available only by looking at the chart.
W3C distinguishes basic transcripts from descriptive transcripts. A transcript and timed captions serve different needs; providing one does not automatically replace the other under a particular WCAG success criterion.
Explain important visual information with audio description
Audio description makes important visual content available to viewers who are blind or cannot see the video adequately. It can describe on-screen text, actions, location changes, charts and other details that the original dialogue does not already explain.
The simplest approach is often to integrate essential visual information into the main narration while scripting. If the finished soundtrack leaves key events undescribed, the video may need a separate audio-described version or an additional description track. Where there is not enough room between dialogue, extended description may require pauses.
If a safety video shows an employee tightening a valve without explaining it, narration could say, “The technician turns the red emergency valve clockwise until it locks.” That information should not depend on vision alone.
See W3C's description of visual information guidance.
Choose a media player people can control
Even a video with good captions may be difficult to access if the player cannot be operated with a keyboard. Test whether viewers can reach play, pause, volume, captions, playback controls and full-screen options without using a mouse.
Controls should have understandable labels, visible keyboard focus and a predictable order. Avoid unexpected autoplay, inaccessible custom menus and controls that disappear before a keyboard user can activate them. Check compatibility with screen readers and whether captions and audio-described versions can actually be selected.
A user should be able to pause content and access any required text alternatives. The W3C media guide includes accessible player considerations; a video host's accessibility features still need to be tested in your actual embed.
Make on-screen text legible and understandable
Text inside video can be hard to read when it is small, flashes past quickly or sits over a busy background. Use readable type sizes, strong contrast and enough display time for people to read and process each message.
Avoid conveying essential meaning only through colour. Labels, spoken explanations and other cues can make diagrams understandable to people with colour-vision differences or those watching on small screens. Check captions against their changing backgrounds too.
A financial video should not say “The red category is the problem” without also naming the category. Label the data, explain the trend in speech and include the values in the transcript.
WCAG has contrast requirements for relevant text and visual information, but the exact criterion and exception depend on the content. Use W3C's WCAG 2.2 Quick Reference rather than assuming one size or colour treatment works in every situation.
Consider sign language and multilingual access
Some viewers benefit from sign-language interpretation, including people whose primary language is a sign language. If this is needed for your audience or delivery requirements, allow sufficient screen space and consider how the interpreter will remain visible throughout the video.
For multilingual audiences, translated subtitles, translated transcripts and appropriately produced voiceovers can help viewers understand a language they do not speak. These are language-access options, not substitutes for same-language accessible captions or description of visual information.
Test the video before and after publication
Review the final exported video and the embedded player—not just the original project file. Automatic captioning, auto-translation and built-in player settings can introduce errors that do not appear until publication.
- Watch with the sound off: can you follow speech and significant sound cues?
- Listen without watching: do you understand important actions, visuals and on-screen instructions?
- Read the transcript: is it complete, structured and easy to locate?
- Use only a keyboard: can you reach, operate and understand every relevant player control?
- Check mobile: are captions and text legible, timed correctly and unobstructed?
- Ask representative users to test wherever practical; automated checks alone will not reveal every barrier.
When you update the video or change platforms, review its accessibility again. Timing, caption display and player compatibility can change during re-encoding or embedding.
Captions, subtitles, transcripts and audio description: which do you need?
These formats solve overlapping but distinct access problems. Choose them based on the media and its audience, not just the name of a supplier service.
| Format | Primary purpose | Typical content |
|---|---|---|
| Same-language captions | Make meaningful audio information available as text | Speech, speaker identification and important sound cues |
| Translated subtitles | Support viewers who speak another language | Translated dialogue; may need further cues for deaf and hard-of-hearing access |
| Basic transcript | Provide a readable version of audio information | Speech and meaningful non-speech audio |
| Descriptive transcript | Make audio and key visuals available as structured text | Audio content plus visual events and on-screen information |
| Audio description | Make essential visual information available by listening | Spoken description of important actions, text, diagrams and scene changes |
| Sign-language interpretation | Support viewers who communicate in a sign language | An interpreter conveying the spoken information in sign language |
For a detailed explanation of naming conventions, read Closed Captions vs Subtitles.
What does WCAG 2.2 require for accessible video?
WCAG is a technical accessibility standard, not a universal declaration of legal compliance. Requirements differ depending on whether the video is live or prerecorded, has audio or is silent, and which conformance level applies to the service or organisation.
- SC 1.2.2, Captions (Prerecorded), Level A: captions for prerecorded audio content in synchronised media, with the criterion's stated exception.
- SC 1.2.4, Captions (Live), Level AA: captions for live audio content in synchronised media.
- SC 1.2.3, Audio Description or Media Alternative (Prerecorded), Level A: audio description or a suitable media alternative for prerecorded video content in synchronised media, subject to the criterion's conditions.
- SC 1.2.5, Audio Description (Prerecorded), Level AA: audio description for prerecorded video content in synchronised media.
- SC 1.2.6, Sign Language (Prerecorded), Level AAA: sign-language interpretation for prerecorded audio content in synchronised media.
Video accessibility checklist before you publish
Use this final review alongside the requirements that apply to your organisation and type of media.
- Important instructions can be understood without relying only on sight or colour.
- Captions are accurate, synchronised and include meaningful non-speech sound information.
- Any machine-generated captions and translated subtitles have been reviewed.
- A suitable transcript is available, with visual description where necessary.
- Important visual information is conveyed in narration or an audio-described version as applicable.
- On-screen text and captions remain readable on mobile and desktop.
- Player controls work with a keyboard and have usable labels and focus.
- Sign-language and language-access requirements have been considered for the audience.
- The published video and embedded player have been tested, not only the source file.
Frequently asked questions
Are subtitles enough to make a video accessible?
Not necessarily. Dialogue-only translated subtitles may leave out important sounds, while visually conveyed information might also need audio description or a descriptive transcript. The player itself also needs accessible controls.
Can I use automatic captions?
They can be a useful draft, but review them against the source recording for missed words, inaccurate names, specialist terms, speaker changes and timing. Publishing unchecked captions can leave viewers with incorrect information.
Do I need a transcript if my video already has captions?
A transcript can serve people who prefer to read or navigate content outside a timed video. The applicable WCAG requirements depend on the media; a descriptive transcript can also communicate important visual information. Captions and transcripts are not automatically interchangeable.
Does every video need audio description?
It depends on the information conveyed and the applicable criteria. If important visual information is already explained within the existing audio, additional description may not be necessary. Where essential visual details are otherwise missing, description may be required.
Are translated subtitles the same as closed captions?
No. Translated subtitles primarily serve a language barrier, while accessibility captions include meaningful audio cues and speaker identification as needed. Some subtitle formats, including SDH, are specifically designed to serve deaf and hard-of-hearing audiences.
Official resources
- W3C WAI — Making Audio and Video Media Accessible, the main guide to media accessibility.
- W3C — Captions and Subtitles, including timing, content and caption types.
- W3C — Transcripts, including descriptive transcripts.
- W3C — Description of Visual Information.
- W3C — Planning Audio and Video Media, with accessibility checklists and WCAG levels.
- WCAG 2.2 Quick Reference, for additional success criteria.
These are general technical guidelines. Whether specific legal duties apply depends on your organisation, service, audience and jurisdiction.
Need captions, subtitles or a transcript for your video?
Tell us about the video, its languages, intended audience and delivery format. We can review your subtitling, captioning, transcription or voiceover requirements and confirm the services and options appropriate to the project.
Explore subtitling and voiceover services →Already have a file and requirements? Request a project quotation.