Overview
Accessibility is usually introduced to students as a rule to comply with, which is both dull and the wrong framing. Taught as craft (captions as an editorial task, contrast as a design decision, audio description as writing) it is genuinely interesting and it produces better work for everyone. It is also far easier to build in at the start than to retrofit, which makes school the ideal place to establish the habit. This guide covers how to fold it into projects students are already doing.
What You Need
- Projects students are already producing. This adds to them rather than replacing them
- Captioning tools, most of which are free and built into editors and platforms
- A contrast checker, or the accessibility checklist on this site
- A rubric that includes accessibility, so it counts
- One good and one poor example of each element, to compare
- A willingness to let students experience the problem before being told the rule
Steps
Let them experience the problem first
Play a clip with the sound off and no captions, or a graphic with poor contrast at small size, and ask what they can follow. Ten seconds of not being able to use something is worth more than any explanation of why accessibility matters, and it reframes the whole topic from imposition to problem-solving.
Teach captions as an editorial skill
Correcting automatic captions requires deciding how to punctuate speech, where to break lines, how to identify speakers, and which sounds carry meaning. That is genuinely a language and editing exercise, and framing it that way makes it a legitimate piece of coursework rather than an administrative chore appended to the real work.
Fold contrast and legibility into design lessons
When students design titles, thumbnails, or lower thirds, make contrast and minimum text size part of the design criteria alongside aesthetics. Checking contrast becomes as routine as checking spelling, and it improves the work for every viewer rather than only those who need it.
Introduce audio description as writing
Asking students to describe, in a fixed number of seconds, what a viewer who cannot see the screen needs to know is a precise and demanding writing exercise. It also teaches them something about their own film, students routinely discover that key information exists only on screen and is never said aloud.
Put it in the rubric
Accessibility that is encouraged but not assessed is deprioritised, exactly like audio. Include specific, observable criteria (captions present and accurate, on-screen text meets contrast requirements) so it is part of what a good submission means rather than optional extra credit.
Require it from the first project, not the last
Retrofitting accessibility is tedious and teaches that it is an add-on. Building it in from the first assignment establishes it as part of what finishing means, and students who learn it that way carry the habit into work where nobody is checking.
Pro Tips
- Have students correct automatic captions rather than typing from scratch. Correction is faster and teaches the same judgement.
- A screen reader demonstration lands hard with students and takes five minutes. Every school computer has one.
- Ask students to watch each other's work muted. Peer discovery is more persuasive than teacher instruction.
- Frame it as reaching more people rather than as compliance: it is true, and students respond to it.
- Captioning is a legitimate literacy activity. It is easy to justify in curriculum terms if you need to.
Knowledge Base
What You'll Learn
Accessibility taught as craft is more engaging and more durable than accessibility taught as rules. Below: why school is the right place for this habit, and how it maps onto curriculum you may already be delivering.
Why the Habit Is Best Formed at School
Professionals who did not learn accessibility early treat it as an extra task added under deadline pressure, which is exactly the condition in which it gets dropped. Students who learn it as part of what finishing means never experience it as an addition at all.
The practical difference is significant. Retrofitting captions to a finished video means transcribing speech that was already scripted, and adding audio description means describing visuals whose intent nobody wrote down. Building it in means the script is most of the caption file already, and a presenter who has been taught to say what is on screen removes much of the need for description.
There is also a straightforward employability argument worth making to students: accessibility is increasingly written into client contracts and public sector procurement, and being able to deliver it competently is a marketable skill rather than a moral position. Students respond to that framing, and it happens to be true.
Mapping This Onto Curriculum You Already Teach
Accessibility work maps cleanly onto existing curriculum objectives, which makes it easy to justify rather than an additional burden.
Captioning is literacy. It requires punctuation decisions, sentence boundary judgements, register, and editing for readability under a strict constraint. It is defensible as a language exercise on its own terms.
Audio description is descriptive writing with an unusually tight brief, convey necessary visual information in the gaps between dialogue, in a fixed number of seconds. Few writing exercises have constraints that concrete.
Contrast and legibility are design and numeracy. Contrast ratios are a ratio calculation with a real-world consequence, which is a more motivating context than most.
The underlying discussion is citizenship and media literacy, who gets to participate in media, and what it means to make something usable by everyone.
Framed this way, accessibility is not competing with your curriculum for time. It is a delivery vehicle for parts of it.
Where This Fits
This guide covers one specific part of classroom video production. The wider picture, assessing process rather than only the finished video, rotating roles, managing devices and storage, and consent for publishing student work, is in Teaching Video Production: A Classroom Workflow That Works, which frames the discipline as a whole and links out to the detailed guides underneath it, including this one. If you are starting from scratch rather than solving a specific problem, read that first and come back here.
FAQ
Q: At what age should students learn about accessibility?
A: From the first media project they make, at whatever age that is. The concepts scale down easily, younger students readily understand that some people cannot hear the sound or see the screen, and building it in from the start means they never experience it as an extra task bolted onto finished work.
Q: Is captioning too tedious for students?
A: Correcting automatic captions rather than typing from scratch removes most of the tedium and keeps the valuable part, which is the editorial judgement about punctuation, line breaks, speaker identification, and which sounds carry meaning. Framed as an editing exercise it is a legitimate and defensible piece of coursework.
Q: How do I convince students this matters?
A: Let them experience the problem before you explain the rule: a clip played muted without captions, or a low-contrast graphic viewed small. Then frame it as reaching more people and as a marketable professional skill rather than as compliance. Both framings are accurate and both land better than obligation.
Q: Should accessibility be in the assessment rubric?
A: Yes, with specific observable criteria such as captions present and accurate, and on-screen text meeting contrast requirements. Anything encouraged but not assessed gets deprioritised under deadline. The same pattern as audio. Including it makes it part of what a finished piece means.
Translate this page
- Español
- 简体中文
- हिन्दी
- العربية
- Português
- Français
- Deutsch
- 日本語
- Русский
- Bahasa Indonesia
- 한국어
- Italiano
- Türkçe
- Tiếng Việt
- Polski
- Nederlands
Machine translation provided by Google Translate, on Google’s servers. We do not check these translations and they will get technical terms wrong. The English page is the authoritative one. Following a link sends this page’s address to Google. Your browser may also offer to translate this page itself, which keeps the request on your device.