Skip to main content

🎓 Lesson 14: Accessibility, First-Class

Accessibility is not a checkbox you tick at the end — it's a design decision you make from the first slide, and it makes your course better for everyone. In this lesson we turn "accessibility" from a vague worry into a concrete, repeatable pass you run on every project: alt text, keyboard order, contrast, captions, accessible quizzes, and a real testing routine. By the end you'll have a checklist you can trust.

📚 What You'll Learn

By the end of this lesson, you will be able to:

  • Explain WCAG and Section 508 in plain language, and why accessibility is a legal, ethical, and quality issue
  • Write alt text that actually helps — and know when an image should be marked decorative instead
  • Set a sensible keyboard tab / focus order so a course works with no mouse at all
  • Check color contrast and captions, and build accessible quizzes
  • Run an end-to-end accessibility pass using a checklist you can reuse forever All-New

⏱️ Estimated Time: 40 minutes

🎯 Project: Run a full accessibility pass on the course you've been building — add alt text, fix tab order, check contrast, confirm captions, and log what you changed in your Journal.

In This Lesson

Why Accessibility Is First-Class

Imagine two people opening your finished course. One uses a mouse and hears the narration fine. The other can't see the screen and navigates entirely by keyboard and a screen reader — software that speaks what's on the page aloud. If you designed only for the first person, the second one hits a wall on slide one: an image that says nothing, a button they can't reach with the Tab key, a video with no captions. Accessibility is simply the practice of making sure the second person — and the many people in between — can take your course too.

"The many people in between" is the part folks underestimate. Accessibility isn't only about blindness. It covers low vision, color blindness, deafness and hard-of-hearing, motor differences that make a mouse hard to use, cognitive and learning differences, and situational limits we all hit — a noisy train where you can't hear audio, bright sun washing out a low-contrast screen, a broken trackpad forcing you to the keyboard. Design for the edges and the middle gets better too. Captions help non-native speakers. Good contrast helps everyone outdoors. A clean tab order helps power users fly through your course.

🧠 Mindset

Accessibility can sound like a specialist's job with its own acronyms and rules — but you already have the instincts. If you've ever written a clear label on a button or picked a readable font size, you've done accessibility work. The rest is just a checklist and a little practice. You don't need to memorize every WCAG clause today; you need to know the handful of things that matter most and where to check the rest. You can absolutely do this — and each pass makes the next one faster.

There are three reasons this belongs at the front of your mind, not the end of your timeline:

  • It's the right thing to do. A learner shouldn't be locked out of training they need for their job, their school, or their safety because of how the course was built.
  • It's often the law. Public-sector, education, and many corporate courses are legally required to be accessible (more on the specific standards next).
  • It's cheaper and better done early. Adding alt text and fixing tab order as you build takes minutes. Retrofitting a finished 40-slide course the week before launch is miserable — and it shows.

That last point is the whole reason this is a Part 3 lesson and not an afterthought. In this course you've learned to add media (Lesson 9), style with themes (Lesson 6), and build assessments (Lessons 12–13). Now you learn to do all of that accessibly the first time, so it becomes a habit rather than a rescue mission.

WCAG & Section 508 in Plain Language

Two names come up constantly, and they're less scary than they sound.

WCAG — the Web Content Accessibility Guidelines — is the international rulebook for making digital content accessible. It's maintained by the same standards body behind the web itself, and because a published Captivate course is web content (HTML5), WCAG applies directly to what you build. WCAG is organized around four principles, easy to remember with the initialism POUR:

💧 POUR — the four ideas behind every accessibility rule

  • Perceivable — people can perceive the content with the sense they have. (Alt text for images, captions for audio, enough color contrast.)
  • Operable — people can operate it with the input they use. (Everything works by keyboard, nothing is on a time limit they can't extend, no seizure-inducing flashing.)
  • Understandable — content and controls make sense. (Clear language, predictable navigation, helpful error messages.)
  • Robust — it works with assistive technology like screen readers, now and later.

WCAG sorts its success criteria into three conformance levels: A (the essentials), AA (the practical target almost everyone aims for), and AAA (the strictest, rarely required across a whole course). When someone says "we need to be WCAG compliant," they almost always mean WCAG 2.1 AA (or 2.2 AA — the versions increment over time, so confirm which one your organization requires). That is your north star: aim for AA.

Section 508 is a United States law. It requires that electronic content produced or used by federal agencies — and, by extension, a great many contractors, universities, and vendors who sell to them — be accessible. The practical news is friendly: Section 508 was updated to point at WCAG. So in most cases, if you meet WCAG 2.x AA, you meet Section 508 too. You mostly get to think about one standard, not two. Other countries have their own laws (for example, the EU's EN 301 549 and various national acts), and they, too, lean on WCAG — which is exactly why WCAG is the skill worth learning.

⚠️ Tools help, but they don't "certify" you

Automated checkers (including any built into Captivate or your browser) catch maybe a third to a half of real issues — missing alt text, low contrast, empty labels. They cannot judge whether your alt text is meaningful, whether the tab order makes sense, or whether a screen reader user could actually complete your quiz. Treat automated results as a first sweep, then test with the keyboard and a screen reader yourself. "The checker passed" is a start, not a finish line.

One more reassurance: Adobe Captivate is built with this in mind. The all-new Adobe Captivate All-New is designed to produce accessible HTML5 output, and both it and Captivate Classic give you places to add alt text, control reading/tab order, and add captions. Adobe adjusts exactly where these settings live between releases, so we'll describe them by what they do and point you to helpx.adobe.com/support/captivate.html for the current menu path. The concepts below don't move even when the buttons do.

The Big Six: What to Actually Do

Here's the good part. Almost all the accessibility wins in a Captivate course come from six practical habits. Master these and you're most of the way to AA. This diagram is the map; the sections below are the detail.

graph TD A["♿ Accessible Captivate course"] --> B["1. Alt text
for images & components"] A --> C["2. Keyboard & tab order
everything reachable"] A --> D["3. Color contrast
text stays readable"] A --> E["4. Captions & transcripts
for audio & video"] A --> F["5. Clear structure
headings, labels, language"] A --> G["6. Accessible quizzes
feedback anyone can read"] style A fill:#bbf7d0,color:#1e293b style B fill:#bfdbfe,color:#1e293b style C fill:#bfdbfe,color:#1e293b style D fill:#bfdbfe,color:#1e293b style E fill:#c7d2fe,color:#1e293b style F fill:#c7d2fe,color:#1e293b style G fill:#fde68a,color:#1e293b

Figure 1 — The Big Six: six habits that carry most of the accessibility load in a Captivate course.

1. Alt text — describe what matters

Alt text (alternative text) is a short written description of an image that a screen reader reads aloud. In Captivate you set it in the properties for an image or component — usually a field labeled Accessibility, Alt text, or Accessibility name/description. The skill isn't finding the field; it's writing text that helps.

Good alt text answers: what does this image communicate in this context? — not "what pixels are in it." Describe the meaning, keep it concise, skip "image of…" (the screen reader already announces it's an image), and don't stuff keywords.

The image ❌ Weak alt text ✅ Strong alt text
A worker wearing safety goggles at a workbench "image1.png" "A worker wearing safety goggles while using a bench grinder"
A chart showing sales rising each quarter "chart" "Bar chart: quarterly sales rose steadily from Q1 to Q4"
A purely decorative swoosh in the corner "blue swoosh graphic decoration element" (mark as decorative — no alt text)
💡 Decorative vs meaningful. If an image adds nothing a learner would miss — a background texture, a divider line, a purely aesthetic flourish — mark it decorative so the screen reader skips it. Nothing is more tiring than a screen reader announcing "blue swoosh graphic" on every slide. Reserve alt text for images that carry meaning; silence the rest.

And if an image contains a lot of information — a detailed diagram, an infographic, a data table rendered as a picture — a one-line alt can't carry it. Put the full content in nearby on-screen text or a transcript, and use the alt text to point to it ("Detailed process diagram; full steps in the text below").

Figure 2 — All-new Captivate (a simplified mock-up, not a real screenshot): setting alt text and the decorative flag on a selected image component.

2. Keyboard & tab order — no mouse required

Many learners never touch a mouse: they navigate with Tab to move forward, Shift+Tab to move back, Enter or Space to activate, and arrow keys inside a control. Two rules make a course keyboard-friendly:

  • Everything interactive must be reachable and operable by keyboard. Every button, link, quiz option, and interactive component should take focus and respond to Enter/Space. If you can't reach it with Tab, a keyboard-only learner can't use it.
  • The order must make sense. Focus should move the way a person reads — generally top to bottom, left to right — not jump randomly around the slide. Captivate lets you set the reading/tab order of objects on a slide (look for a Tab order or Reading order control). Fix any object that jumps out of sequence, and remove decorative objects from the tab order entirely so nobody tabs onto a background shape.

There's also a visible focus indicator — the outline that shows where the keyboard is right now. Don't suppress it. A learner navigating by keyboard needs to see where they are, the same way a mouse user needs to see the cursor.

3. Color contrast — readable for real eyes

Low-contrast text (pale gray on white, thin color on a busy photo) is hard for anyone and impossible for some. WCAG AA sets clear targets: normal body text needs a contrast ratio of at least 4.5:1 against its background, and large text (roughly 18pt+, or 14pt bold) needs at least 3:1. You don't compute this by eye — you use a contrast checker (many free web tools, and some built into design software) that takes two colors and gives you the ratio.

This ties straight back to Lesson 6: set accessible colors in your theme once, and every slide inherits them. A brand palette that passes contrast at the theme level means you're not fighting this slide by slide. Two more rules: don't rely on color alone to carry meaning (pair "red = wrong" with an ✗ icon or the word "Incorrect," since color-blind learners may not see the difference), and keep enough contrast on buttons and focus outlines too, not just paragraph text.

4. Captions & transcripts — for audio and video

Back in Lesson 9 you added narration and video. Accessibility is where you make sure a deaf or hard-of-hearing learner — or anyone with the sound off — gets the same content:

  • Closed captions put the spoken words on screen, timed to the audio. Add them to videos and to narrated slides. If you wrote a narration script (you should), you're halfway there — captions are largely that script, timed.
  • Transcripts are the full text of the audio/video in one readable block. They help screen-reader users, people who prefer to read, and search. For an audio-only element, a transcript is often the key accessibility fix.
  • Don't bury information in audio alone. If narration says something the learner must know, make sure it's also available as text somewhere.

5. Clear structure — headings, labels, language

Screen readers let people jump by heading, so use real heading styles (from your theme) for titles and section heads rather than just making text big and bold — the style is what conveys "this is a heading" to assistive tech. Give every interactive element a clear, meaningful label ("Submit quiz," not "Button 3"). Set the project's language so the screen reader uses the right voice and pronunciation. And write plainly: short sentences, defined jargon, predictable navigation. Understandable is one of the four POUR principles for a reason.

6. Accessible quizzes

We'll dig into this next — it's where accessibility most often quietly breaks.

Accessible Quizzes & Testing

Assessments (Lessons 12–13) carry extra accessibility weight because a locked-out learner doesn't just miss content — they can fail a course they actually know. A few habits keep quizzes fair:

  • Every question must be keyboard-operable. A learner should be able to Tab to each option, select with Space/Enter, and reach Submit — with no mouse. Drag-and-drop and hotspot questions are the usual trouble spots; either provide a keyboard-accessible way to answer or offer an equivalent question type. When in doubt, a plain multiple-choice question is the most accessible.
  • Feedback must be perceivable without color. "Correct/Incorrect" should be words a screen reader announces, not just a green or red flash. Make sure the feedback text itself takes focus or is read out when it appears.
  • Watch time limits. If a question or the quiz is timed, learners who need more time (for motor or cognitive reasons) must be able to get it. Avoid tight timers unless the assessment genuinely requires them, and provide an alternative if it does.
  • Label everything. Each option, the question stem, and the Submit and results controls need clear labels so they make sense read aloud out of visual context.

✅ The reusable accessibility checklist

Run this on every project before you publish. Save it — you'll use it for the rest of your career.

  • ☐ Every meaningful image has clear alt text; decorative images are marked decorative
  • ☐ You can complete the whole course with the keyboard only — no mouse
  • ☐ Tab / reading order follows the visual reading order on every slide
  • ☐ The focus indicator is visible as you tab through
  • ☐ Text meets contrast (4.5:1 normal, 3:1 large); meaning never relies on color alone
  • ☐ Audio and video have captions; audio-heavy content has a transcript
  • ☐ Real heading styles are used; interactive elements have meaningful labels; project language is set
  • ☐ Quizzes are keyboard-operable and give text feedback; no unfair time limits
  • ☐ You tested with a screen reader, not just an automated checker

How to test. Do these three passes and you'll catch the vast majority of issues:

  1. Automated sweep. Run Captivate's accessibility check (if present in your version) and/or a browser accessibility tool on the published HTML5 output. Fix the flagged basics: missing alt, empty labels, low contrast.
  2. Keyboard-only run. Put the mouse down. Tab through the entire course from start to finish, including every quiz. If you get stuck or can't reach something, a keyboard user can't either.
  3. Screen-reader run. Turn on a screen reader — NVDA (free, Windows), VoiceOver (built into macOS, ⌘+F5) Win + Mac — and listen to a few slides and a quiz. Does the alt text make sense? Is feedback announced? This is the single most revealing test, and it costs nothing.
💡 Test on the published output, not just the editor. Learners experience the published HTML5 course in a browser, so that's where accessibility ultimately counts. Publish a quick preview (you'll master publishing in Lesson 15) and run your keyboard and screen-reader passes there.

🎯 Try It: Run an Accessibility Pass

🏋️ Activity: Make your course usable by everyone (~25 minutes)

Objective: Take the course you've been building and run a real, first-class accessibility pass on it using the checklist — the exact routine you'll repeat on every future project.

Steps

  1. Open your project. For every meaningful image and component, add clear alt text; mark any purely decorative graphics as decorative. (⏱️ 6 min)
  2. Check the tab / reading order on two or three of your busiest slides. Fix anything that jumps out of sequence, and remove decorative objects from the tab order. (⏱️ 5 min)
  3. Run your main text and button colors through a contrast checker. Aim for 4.5:1 on body text. If something fails, adjust it in your theme so it fixes everywhere at once. (⏱️ 4 min)
  4. Confirm any audio or video has captions (and a transcript for audio-heavy content). (⏱️ 3 min)
  5. Do a keyboard-only run: put the mouse down and Tab through the whole thing, including a quiz. Note anything you can't reach or operate. (⏱️ 5 min)
  6. If you have a few extra minutes, turn on NVDA or VoiceOver and listen to two slides and one question. (⏱️ 2 min)
💡 Hint

Feeling like there's too much? Do it in the order of the Big Six and stop when your timer's up — even alt text plus one keyboard run is a real improvement over most courses in the wild. If you can't find a specific setting (Adobe moves them between releases), search helpx.adobe.com/support/captivate.html for "accessibility" — the concept is what matters, and you now know exactly what you're looking for.

✅ Activity Complete When…

  • Every meaningful image has alt text and decorative graphics are marked decorative
  • You've checked and fixed tab order on your busiest slides
  • Your key text passes contrast, and any media has captions
  • You've completed at least one full keyboard-only pass and logged what you found

🎯 Quick Quiz

Question 1: A learner's organization says the course must be "WCAG 2.x AA and Section 508 compliant." What's the most accurate takeaway?

Question 2: You've added a purely decorative swoosh graphic in the corner of every slide. What should you do for accessibility?

📓 Learning Journal

Keep your Learning Journal going — it's where "I read that" becomes "I can do that." After each lesson, jot down:

  • Key concepts you learned
  • Things that clicked for you
  • Questions or confusion points to revisit
  • Ideas you want to try
  • Your progress and how you feel about learning this

✍️ This lesson's prompt: Run your keyboard-only pass and write down the single biggest barrier you found in your own course — the moment you got stuck without a mouse. How did you fix it, and how will you avoid building that barrier next time? Note one thing about accessibility that surprised you.

📝 Lesson Summary

🎓 Key Takeaways

  • Accessibility is a first-class design decision — it's the right thing, often the law, and far cheaper done early. It makes courses better for everyone.
  • WCAG (aim for AA) is the international rulebook, organized by POUR — Perceivable, Operable, Understandable, Robust. Meeting WCAG 2.x AA generally satisfies U.S. Section 508 too.
  • The Big Six carry most of the load: alt text, keyboard/tab order, color contrast, captions/transcripts, clear structure, and accessible quizzes.
  • Automated checkers are a first sweep, not a certificate. Verify with a keyboard-only run and a screen reader (NVDA on Windows, VoiceOver on Mac) on the published output. Win + Mac

🎉 What You've Accomplished

You turned "we should make it accessible" into a routine you can actually run. You can explain WCAG and Section 508 without flinching, write alt text that helps, set a sane tab order, check contrast, handle captions, build fair quizzes, and test the way real assistive-tech users experience your work. That's a professional-grade skill — and it's part of what separates a course that ships from a course that gets sent back.

❓ Common Questions at This Stage

Do I really have to make everything accessible?

Aim for it, yes — but progress beats paralysis. If your organization requires WCAG AA, that's the target and it's very achievable with the Big Six. If you're building for yourself, do as much as you can and grow each project. Even alt text plus keyboard support puts you ahead of most courses out there.

Where exactly are the accessibility settings in Captivate?

They live in an object's or component's properties (often an "Accessibility" area) and in a per-slide reading/tab-order control, plus project-level language and closed-caption features. Adobe moves the exact menu paths between releases, so search helpx.adobe.com/support/captivate.html for "accessibility" in your version. You now know what to set — that's the durable part.

Is a screen reader hard to test with?

Less than you'd fear. Turn on VoiceOver with ⌘+F5 on a Mac, or install the free NVDA on Windows, and just listen. You don't need to be an expert user — even a beginner immediately hears when alt text is missing or feedback isn't announced. Ten minutes of listening reveals more than any automated report.

🔭 Looking Ahead

Your course is now built, assessed, and accessible. In Lesson 15, you'll publish it — to HTML5 for the web and to SCORM/xAPI for a Learning Management System — and see how tracking and completion reporting work. It's the moment your course becomes something real learners can take.

✅ Before the Next Lesson

  • Finish your accessibility pass and save your reusable checklist somewhere handy
  • Write this lesson's journal prompt — the biggest barrier you found and fixed
  • If you're curious, try a free contrast checker on your brand colors so you're ready to publish

📚 Additional Resources

🌟 Encouragement for the Journey

Every learner you'll never meet — the one on the train with the sound off, the one navigating by keyboard, the one who just needs bigger contrast — gets to take your course because of the work you did today. That's not a compliance checkbox. That's the whole point of building courses in the first place. Beautifully done.