If you build or buy training for a federal or state agency, accessibility isn’t optional. Section 508 of the Rehabilitation Act, and increasingly WCAG 2.1 Level AA by reference, is a compliance requirement, not a nice-to-have. Contracting officers ask for a VPAT before award, and a course that fails testing after delivery can get bounced back, delay payment, or become a real liability.
We’ve built 508-compliant Storyline, Captivate, and Lectora courses for federal and state agencies for years, including work for the U.S. Army. Here’s what actually matters in practice, not the whole WCAG spec, but the parts that consistently trip up eLearning teams.
What “508 compliant” actually means for a course
Section 508 requires federal electronic content to be accessible to people with disabilities. Most agencies now point to WCAG 2.1 Level AA as the technical standard they’ll actually test against. For an eLearning course, that breaks down into four practical buckets, usually called POUR: Perceivable, Operable, Understandable, and Robust.
The checklist we run on every course
Perceivable
- Every image, icon, and decorative graphic has correct alt text (or is marked decorative)
- Every video has accurate closed captions, reviewed and corrected, not just auto-generated
- Every audio narration has a text transcript alongside it
- Color is never the only way information is conveyed, like a red/green correct-incorrect indicator that also gets an icon or label
- Text contrast meets a 4.5:1 minimum against its background
Operable
- Every interaction (click, drag, hotspot, slider) has a keyboard-only equivalent
- Tab order follows the logical reading order, not the order objects were dropped on the stage
- No content flashes more than 3 times per second
- Learners get enough time to read and interact; no auto-advancing timers that can’t be paused or extended
Understandable
- Instructions are written in plain language and don’t rely on sensory cues alone, like “click the button on the right”
- Form fields and quiz inputs have programmatically associated labels, not just visual proximity
- Error messages tell the learner what’s wrong and how to fix it, not just “incorrect”
Robust
- The published SCORM or xAPI package works correctly with a screen reader, like NVDA or JAWS, in the actual LMS it will run in, not just the browser preview
- Custom Storyline and Captivate interactions have proper focus order and ARIA labeling, which usually needs manual tagging, not just the built-in “accessible course” checkbox
The step most vendors skip: real assistive-tech testing
Authoring tools like Storyline and Captivate include an “accessible” toggle, but flipping it on doesn’t guarantee real accessibility. It sets up the scaffolding; it doesn’t verify the result. We test the published output in the actual LMS with a screen reader and keyboard-only navigation before delivery, not just eyeball it in the tool’s preview mode. That’s usually where the real gaps show up: a hotspot that’s unreachable by keyboard, a quiz option a screen reader skips, a modal that traps focus.
Where a VPAT comes in
A VPAT, or Voluntary Product Accessibility Template, is the document most contracting officers ask for before or at delivery. It states, criterion by criterion, which WCAG success criteria the course meets, partially meets, or doesn’t meet, and why. We provide one with every 508-scoped course so procurement and security review isn’t a bottleneck at the finish line.
What this costs to get right
Building for 508 compliance from the start doesn’t have to double your budget. Most of the added cost is caption and transcript review plus screen-reader QA time, typically 15 to 25 percent on top of a standard build. See our PowerPoint-to-eLearning pricing guide for base rates, then add that range if the course needs to be 508-scoped. What isn’t affordable is finding out after delivery that a course fails testing and has to be rebuilt.
Bottom line
If you’re scoping a course for a federal or state agency, ask your vendor for their WCAG testing process, not just a checkbox that says “accessible.” DGS Designs has been building and testing 508-compliant Storyline, Captivate, and Lectora courses for federal and state clients for years. Contact us to get your next course built and verified for 508 compliance from day one.
