Apply Universal Design for Learning and basic accessibility practice so materials work for every learner.
Why it matters
In any group you teach, some people have disabilities (visible or not), some are working in a second language, some join on a phone in a noisy space, and some are tired or anxious. If accessibility is an afterthought, these learners hit barriers: an untagged PDF, an uncaptioned video, a color-only diagram, a timed quiz. Designing for this variety from the start is cheaper than retrofitting, often helps everyone, and in many workplaces and schools it is also a legal requirement.
Universal Design for Learning
Universal Design for Learning (UDL) is a framework developed by CAST, a US nonprofit, beginning in the 1980s and 1990s (David Rose and Anne Meyer were among its founders). It takes its name from universal design in architecture, where curb cuts built for wheelchair users turned out to help people with strollers, carts and luggage too.
UDL asks designers to provide options along three principles (CAST released version 3.0 of the UDL Guidelines in 2024):
| Principle | The "why", "what" or "how" of learning | Examples in a Git workshop |
|---|---|---|
| Multiple means of engagement | Why: interest, effort, self-regulation | Choice of practice scenario; clear goals; a safe practice repo where mistakes cost nothing |
| Multiple means of representation | What: how information is presented | Diagram plus spoken explanation plus written handout; captions; commands available as copyable text; key terms defined |
| Multiple means of action and expression | How: how learners show what they know | Use the terminal or a graphical client; explain a resolution verbally or in writing; keyboard-accessible tools |
UDL is not about lowering standards. The objective stays "resolve a merge conflict so tests pass"; UDL removes barriers that are not part of that objective. If the objective is about Git, then reading a low-contrast screenshot is not a fair part of the test.
A note on evidence: UDL is a design framework with broad adoption and a growing research base, but reviews describe the evidence for its overall effect on learning outcomes as still developing. Its concrete accessibility practices (captions, alt text, structure) rest on firmer ground and on legal standards.
Accessibility standards you will meet
- WCAG (Web Content Accessibility Guidelines) from the W3C, currently version 2.2, organized around content being perceivable, operable, understandable and robust. Most organizations aim for level AA.
- In the US, Section 508 (federal agencies and their vendors) and the ADA; in the EU, the European Accessibility Act. Requirements and deadlines differ by country and change over time, so check with your organization's accessibility or legal team.
A practical checklist for training materials
Documents and slides
- Use real headings, lists and built-in layouts so screen readers can navigate.
- Add meaningful alt text to informative images; mark decorative ones as decorative.
- Contrast at least 4.5:1 for normal text; never rely on color alone (add labels or patterns).
- Use the accessibility checker built into Word, PowerPoint or Google tools.
Video and audio
- Accurate captions (correct technical terms); transcripts for audio.
- Describe important visual actions in the narration.
E-learning and quizzes
- Everything works with a keyboard; focus is visible.
- Avoid time limits unless speed is the skill; if used, allow extensions.
- Clear instructions and error messages.
Live and virtual sessions
- Share materials in advance so people can preview or enlarge them.
- Turn on live captions in the meeting tool; speak one at a time.
- Offer several ways to participate: speak, chat, poll, or follow-up message.
- Ask, privately and early, whether anyone needs adjustments.
Applying UDL to a lesson: example
Original plan: 40-minute lecture with dense slides, a live demo in small font, and a timed 10-question quiz.
UDL revision:
- Share slides and the worked example sheet the day before (representation, engagement).
- State the goal and show what success looks like (engagement).
- Demo in large font with narration, captions on, commands pasted into chat (representation).
- Practice in pairs or solo, terminal or graphical client (action and expression).
- Untimed practical task instead of a timed quiz; learners can explain their resolution in writing or out loud (action and expression).
- Recording with corrected captions posted afterwards.
Common mistakes
- Treating accessibility as a final check instead of a design input.
- Equating UDL with "learning styles": UDL is about removing barriers and offering options, not diagnosing learner types.
- Fixing only what an automated checker flags; also test with a keyboard and a screen reader.
- Assuming no one in the group needs accommodations because no one said so.
Quick recap
- UDL: multiple means of engagement, representation, and action and expression.
- Keep the objective fixed; remove barriers that are not part of it.
- WCAG 2.2 AA is the common target; legal requirements vary, so check locally.
- Captions, alt text, structure, contrast and keyboard access are the basics.
Try it
Answer the quiz on the Do tab. Then pick one of your own materials and run your tool's accessibility checker on it.