🎓 Lesson 19: Accessibility, First-Class

♿ Why Accessibility Matters

Somewhere between one in four and one in five adults lives with a disability — visual, motor, hearing, cognitive, or a mix. If your course can't be used with a screen reader, or by keyboard alone, or without hearing the audio, you haven't just made a design choice. You've locked real people out of training they may need to do their jobs.

There are three reasons to care, and any one of them is enough:

• It's human. Everyone deserves access to learning. Full stop.
• It's the law. In the US, Section 508 covers federal and federally funded content, the ADA reaches many organizations, and both point at the WCAG standard. Many other countries have equivalents. Non-compliant courses are a real legal and reputational risk.
• It's just good design. Captions help people in noisy offices and non-native speakers. Clear focus order helps power users. High contrast helps everyone on a sunny day. Accessible design is better design for all learners — the "curb-cut effect."

🧭 WCAG & POUR in Plain Terms

The global standard is the Web Content Accessibility Guidelines (WCAG), and it can look intimidating — pages of numbered success criteria at levels A, AA, and AAA (most organizations aim for AA). But every one of those criteria hangs off four plain-English ideas, remembered by the acronym POUR.

Figure 1 — The four POUR principles behind WCAG: Perceivable, Operable, Understandable, Robust.

• Perceivable — a learner must be able to sense the content. If they can't see an image, it needs alt text; if they can't hear audio, it needs captions.
• Operable — they must be able to use it, including with a keyboard alone and without being rushed by a timer they can't control.
• Understandable — the content and the navigation must make sense: plain language, predictable buttons, clear instructions.
• Robust — it must work with assistive technology like screen readers, now and as tech evolves. This is why publishing modern HTML5 (Lesson 20) matters.

🖼️ Alt Text: Meaningful vs Decorative

Alt text (alternative text) is the words a screen reader speaks in place of an image. Both Rise and Storyline let you add alt text to any image — but the skill is knowing what to write, and when to write nothing at all.

• Meaningful images carry information. Describe what matters: "A Class C extinguisher with a red label and a lightning-bolt icon." Don't start with "Image of…" — the screen reader already says it's an image.
• Decorative images are pure eye-candy — a background swoosh, a divider. Mark them as decorative (in Storyline, uncheck "visible to accessibility tools" or mark it decorative; in Rise, leave alt text empty for decorative images) so screen readers skip them instead of announcing clutter.
• Text in images is a trap. If a graphic contains words that matter, put those words in the alt text (or, better, as real text) — otherwise they're invisible to a screen reader.

💡 The alt-text test: Read your alt text aloud with your eyes closed. Does it give you what a sighted learner gets from the image? If it over-describes ("a 1200-pixel photograph of…") or under-describes ("chart"), rewrite it. Aim for the point of the image, not its pixels.

⌨️ Focus Order & Accessible Labels

A keyboard or screen-reader user moves through a slide by pressing Tab, landing on one object after another. The sequence they land in is the focus order — and if it's wrong, your beautifully arranged slide becomes a confusing jumble read out in the order objects happened to be created.

Storyline gives you a dedicated Focus Order editor (per slide). You can reorder objects so a screen reader reads them top-to-bottom, left-to-right the way a sighted learner scans, and remove objects that shouldn't be announced. You also set accessible labels (also called alternate text on objects) so a bare button reads as "Start the course," not "Button 3."

Figure 2 — Storyline's Focus Order editor (a simplified mock-up, not a real screenshot): the exact sequence a screen reader announces objects.

Rise handles most focus order automatically because its blocks stack in a logical, responsive order — one more reason Rise is "accessible by default." You still write good alt text and labels, but you rarely wrestle with tab order the way you might on a busy Storyline slide.

🔊 Closed Captions & Media

Any audio or video with meaningful sound needs closed captions so deaf and hard-of-hearing learners — and anyone in a quiet or noisy room — can follow along. Storyline lets you import a caption file (common formats like SRT or VTT) or type and time captions in its built-in caption editor, and it shows a CC toggle in the player. Rise supports captions on its video/multimedia blocks as well.

Storyline also offers an auto-caption feature that generates a first draft of captions from your narration — a real time-saver, but treat it as a draft. Auto-captions mishear names, jargon, and accents, so always proofread and fix the timing (and note that availability and behavior of AI-assisted features can vary by plan Add-on — check your account).

🎨 Contrast, Color & Keyboard

A cluster of smaller habits rounds out an accessible course:

• Color contrast. Text must stand out from its background (WCAG AA asks for roughly 4.5:1 for normal text). Pale gray text on white looks elegant and fails hard — use a contrast checker.
• Never rely on color alone. "Click the green button, not the red one" is invisible to a colorblind learner. Add a label, an icon, or a shape so meaning survives without color.
• Readable text. Reasonable font sizes, don't cram, and let text reflow (Rise does this natively; in Storyline, mind responsive playback and zoom).
• Keyboard operability. Everything clickable should be reachable and activatable with Tab and Enter/Space. Test your course with the mouse unplugged.
• No auto-play surprises & enough time. Don't blast audio on load, and avoid timers a learner can't pause or extend. Flashing content can trigger seizures — avoid it.

✅ The Accessibility Checklist

Print this, pin it, and run it before you publish. It maps each practical task to a POUR principle and to where you'll find it in each tool.

🎯 Try It: Make a Slide Accessible

📓 Learning Journal

📝 Lesson Summary

🎉 What You've Accomplished

You now think about accessibility the way professionals do — not as a scary audit, but as a set of habits and a checklist you can run in minutes. That single skill separates courses that quietly exclude people from courses that genuinely reach everyone. It'll show up in your portfolio and your job interviews.

❓ Common Questions at This Stage

🔭 Looking Ahead

Your course is built and accessible — now it needs to reach learners. In Lesson 20, we demystify publishing and the LMS: SCORM, xAPI, AICC, cmi5, Web, and how completion and tracking actually work (including that Result-slide variable from Lesson 18).

✅ Before the Next Lesson

• Run the accessibility checklist on at least one slide or lesson
• Write this lesson's journal entry — a course that failed, and two habits you'll adopt
• Keep the checklist table handy; you'll use it again in the capstone preflight (Lesson 24)

📚 Additional Resources

• Course Glossary — WCAG, 508, alt text, focus order, captions
• Quick-Reference Cheat Sheet — the accessibility quick checklist
• E-Learning Heroes — accessibility discussions and examples
• Articulate Support — accessibility how-to articles