Accessible eLearning Built to WCAG 2.1 AA and Section 508
For L&D, HR and compliance teams that need every employee, including people who use screen readers, keyboards, captions or magnification, to complete the same training.
IKHYA builds accessible eLearning courses so learners with disabilities can take the same course, on the same day, as everyone else.
Get a Free Quotation
Scoped proposal delivered within 48 hours
- Since 2010Delivering eLearning
- 500+Projects
- 40+Countries with clients
- 120+Specialists
Accessible eLearning in short
Accessible eLearning is online training that people with visual, hearing, motor, cognitive and other disabilities can perceive, operate and understand, usually measured against WCAG 2.1 Level AA. IKHYA builds custom accessible courses to WCAG 2.1 AA and Section 508 in Storyline 360, Rise 360, Adobe Captivate and other tools, with SCORM or xAPI tracking for your LMS.
Why teams choose IKHYA for accessible eLearning
One standard, stated up front
Every accessible course we build targets WCAG 2.1 AA and Section 508. A course built to WCAG 2.1 AA also covers the WCAG 2.0 AA level that Section 508 requires, so one build serves both.
Built in the tool you already own
We work in Articulate Storyline 360, Articulate Rise 360, Adobe Captivate, Lectora, iSpring Suite, dominKnow ONE and Elucidat, and publish to SCORM 1.2, SCORM 2004, xAPI or HTML5.
Ready for global teams
We have delivered eLearning to clients in 40+ countries and work in 40+ languages, so accessible versions can follow your course into every language you roll out.
Yours to update
You receive the editable source files (for example Storyline or Captivate files), so your team can revise the course later without rebuilding accessibility from scratch.
What is accessible eLearning?
Accessible eLearning is a course that learners with disabilities can use fully and independently: they can read or hear every piece of content, operate every control without a mouse, and understand what to do next. In practice that means text alternatives, captions, keyboard access, enough contrast, clear structure and no traps or time pressure the learner can't control.
It matters at scale. The World Health Organization estimates that 1.3 billion people, about 1 in 6 people worldwide, experience significant disability (WHO fact sheet, March 7, 2023). Many of them are in your workforce, and some of their needs are temporary or never disclosed.
For US employers there is also a legal angle. The EEOC's guidance on reasonable accommodation lists employer-sponsored training among the "benefits and privileges of employment" that employees with disabilities must be able to enjoy equally, and says the obligation covers training from an outside provider too. (This is a summary of public guidance, not legal advice.)
Vision (blind, low vision, color blindness)
Screen reader access to every element, meaningful alt text, a logical reading order, at least 4.5:1 text contrast, and no information carried by color alone.
Hearing (deaf, hard of hearing)
Captions on all narration and video, transcripts, and visual cues for any sound-based feedback.
Motor (limited dexterity, tremor, paralysis)
Everything works with a keyboard, no drag-only actions, no keyboard traps, and time limits the learner can turn off or extend.
Cognitive (dyslexia, ADHD, memory)
Plain language, consistent layouts and navigation, short chunks, and clear instructions and error messages.
Which accessibility standards apply to eLearning?
For most organizations the working target is WCAG 2.1 Level AA: 50 success criteria at Levels A and AA, published by the W3C. US federal agencies follow Section 508, which requires WCAG 2.0 AA. Some public bodies now face their own deadlines. Which rules apply to you depends on your sector and country, so confirm with your legal or compliance team.
| Standard or rule | Who it applies to | What it requires | Notes for a course brief |
|---|---|---|---|
| WCAG 2.1 (W3C, published June 5, 2018) | The reference standard used by most accessibility laws and procurement policies | Level AA conformance = all 30 Level A and 20 Level AA success criteria | The default target for corporate eLearning. Four principles: perceivable, operable, understandable, robust |
| WCAG 2.2 (W3C, published October 5, 2023) | Organizations whose policy names the latest version | Adds 9 success criteria to WCAG 2.1, including 2.5.7 Dragging Movements (AA) and 2.5.8 Target Size (Minimum) (AA); 4.1.1 Parsing removed | Backwards compatible: content that conforms to 2.2 also conforms to 2.1 and 2.0. W3C encourages using the latest version |
| Section 508 (US Rehabilitation Act; Revised 508 Standards in effect since January 18, 2018) | US federal agencies when they develop, procure, maintain or use ICT | WCAG 2.0 Level AA for web and non-web electronic content | A course built to WCAG 2.1 AA covers the WCAG 2.0 AA requirement |
| ADA Title II rule (US Department of Justice, published April 24, 2024) | US state and local governments, and contractors that provide public services for them | WCAG 2.1 Level AA for web content and mobile apps | Compliance dates extended on April 20, 2026 to April 26, 2027 (population 50,000+) and April 26, 2028 (smaller entities and special districts) |
| ADA reasonable accommodation (EEOC guidance) | US employers | Equal access to employer-sponsored training for employees with disabilities | No technical standard named; WCAG 2.1 AA is the practical way to build it in |
Facts from W3C, section508.gov, ADA.gov and EEOC, checked October 15, 2026. Not legal advice.
Not sure which option is right for you?
Tell us about your learners, tool and LMS, and your free quote will include a recommended route and a timeline.
What does accessible look like inside a course?
Most accessibility problems in eLearning come from a handful of interaction types. Here is how each one looks when it is built inaccessibly, how an accessible build handles it, and the WCAG 2.1 criterion behind it. Use it as a set of accessible eLearning examples for your next storyboard review.
| Course element | Common barrier | Accessible build | WCAG criterion (level) |
|---|---|---|---|
| Drag-and-drop activity | Only works with a mouse | Same task done by selecting an item and a target with the keyboard or single clicks, or an equivalent choice question | 2.1.1 Keyboard (A); 2.5.7 Dragging Movements (AA, WCAG 2.2) |
| Click-to-reveal tabs and hotspots | Hotspots are images with no name, so a screen reader says nothing useful | Real buttons with clear names and a visible focus outline, in a logical tab order | 4.1.2 Name, Role, Value (A); 2.4.3 Focus Order (A); 2.4.7 Focus Visible (AA) |
| Narrated slides and video | Information only in the audio | Synchronized captions plus a transcript | 1.2.2 Captions (Prerecorded) (A) |
| Video that shows a procedure | Key steps are visible but never spoken | Audio description, or a described version of the video | 1.2.3 Audio Description or Media Alternative (Prerecorded) (A); 1.2.5 Audio Description (Prerecorded) (AA) |
| Charts, diagrams and infographics | Image only, with no alternative | Short alt text plus a text or table version of the data | 1.1.1 Non-text Content (A) |
| Right or wrong feedback | Green for right, red for wrong, nothing else | Text and icon feedback ("Correct", "Not quite") that is announced to screen readers | 1.4.1 Use of Color (A) |
| Timed quiz or timed slide | Learners run out of time | Time limit can be turned off, adjusted or extended | 2.2.1 Timing Adjustable (A) |
| Auto-playing audio | Narration talks over the screen reader | Pause or stop control, or audio that starts only when the learner chooses | 1.4.2 Audio Control (A) |
| Light gray text on white | Hard to read for low vision | Text contrast of at least 4.5:1 (3:1 for large text); controls and focus outlines at least 3:1 | 1.4.3 Contrast (Minimum) (AA); 1.4.11 Non-text Contrast (AA) |
| Form fields and quiz answers | Errors shown only by a red border | Labels on every field and errors described in text | 3.3.1 Error Identification (A); 3.3.2 Labels or Instructions (A) |
| Flashing effects | Seizure risk | Nothing flashes more than 3 times in any 1 second | 2.3.1 Three Flashes or Below Threshold (A) |
| Small text in a fixed slide | Text cannot be enlarged | Text resizes to 200 percent without loss of content; content reflows at narrow widths | 1.4.4 Resize Text (AA); 1.4.10 Reflow (AA) |
Conformant is not the same as usable. When a US federal agency's team built its Section 508 course, it passed the developer's checks, yet a blind colleague who tested it found it hard to tell where one lesson ended and the next began. Small changes (a heading and a button at the end of each lesson, clearer instructions) fixed it (section508.gov). That is why testing with real assistive technology belongs in every accessible build.
How do you make 360-degree scenarios accessible?
Immersive scenarios need the same care as any other interaction. W3C's XR Accessibility User Requirements describe what users need: to identify locations and objects in a scene, to act without having to move physically, to reach every part of the interface with the same input method, to extend timings, and to get text descriptions of important audio.
Our immersive work is 360-degree photo and video scenarios built in Adobe Captivate, which play in a standard web browser. For an accessible version we plan text descriptions of each scene and hotspot, keyboard access to every hotspot, captions on all audio, and an equivalent text-based path through the same decisions for learners who cannot use the 360 view.
Which authoring tools are best for accessible eLearning?
No tool makes a course accessible on its own: the main tools give you accessibility features, and the author decides whether the course actually conforms. Here is what the vendors' own documentation says, checked October 15, 2026.
| Tool | What the vendor documents | What it means for your build |
|---|---|---|
| Articulate Storyline 360 | Supports WCAG 2.1 Level AA (Articulate support, updated March 4, 2026). A built-in accessibility checker, available from the May 2025 update, tests up to 15 WCAG success criteria that can be checked automatically | The checker is a useful first pass, but Articulate itself says no automated tool can find every barrier, so manual keyboard and screen reader testing is still needed |
| Articulate Rise 360 | Every block "Supports Accessibility"; only Multimedia: Video is listed "with Considerations" because it has no built-in audio description option (Articulate support, updated March 6, 2026) | A strong choice for responsive, accessible courses. Plan audio description or a text alternative for visual-only video content |
| Adobe Captivate (current version) | Works with NVDA, JAWS and VoiceOver; closed captions added by hand or imported as SRT or VTT; keyboard navigation; authors set the reading order and alt text for each object (Adobe help, updated June 4, 2025) | Accessible output depends on the author setting reading order, alt text and keyboard access for every object |
We also build in Lectora, iSpring Suite, dominKnow ONE and Elucidat. Whichever tool you use, we check the vendor's current accessibility documentation for the interactions in your storyboard before we design them.
What we deliver
Course deliverables
- Custom accessible eLearning courses, designed and built to WCAG 2.1 AA and Section 508
- Accessible scenario-based training and software simulations (show-me, try-me, test-me)
- Accessible microlearning modules and mobile learning solutions that reflow on phones
- Captions and transcripts for course narration and video
- Human or AI voiceover
- Editable source files (for example Storyline or Captivate files) for future revisions
- Accessible versions in 40+ languages through our eLearning translation services
Formats, tools and LMS
- Outputs: SCORM 1.2, SCORM 2004, xAPI and HTML5
- Tools: Articulate Storyline 360, Articulate Rise 360, Adobe Captivate, Lectora, iSpring Suite, dominKnow ONE, Elucidat
- LMS platforms we have delivered courses to include Moodle, TalentLMS, Docebo and Cornerstone
- We also test courses in other LMSs, for example Absorb, SAP SuccessFactors, Workday Learning, Canvas and Litmos
How we build an accessible course
- 01
Accessibility brief
You and IKHYAWe agree the target (WCAG 2.1 AA and Section 508), your learners' known needs, the authoring tool and your LMS.
- 02
Accessible storyboard
IKHYA drafts, you reviewEvery screen gets its reading order, alt text, caption script and a keyboard route for each interaction, written into the storyboard.
- 03
Visual prototype
IKHYA drafts, you reviewA contrast-checked color palette, focus outlines and one sample interaction, tested with a keyboard and a screen reader before full build.
- 04
Build
IKHYAThe full course in your chosen tool, with captions, transcripts and text alternatives built in, not added at the end.
- 05
Accessibility testing
IKHYAKeyboard-only pass, screen reader passes in JAWS, NVDA and VoiceOver, 200 percent zoom and reflow, contrast and caption checks, plus the tool's own checker where it has one.
- 06
Your review
You, then IKHYAYour reviewers, ideally including employees who use assistive technology, test the course. We fix what they find.
- 07
LMS testing and handover
IKHYA and youWe test the SCORM or xAPI package in your LMS and hand over the course and editable source files.
Why testing in more than one screen reader matters: in WebAIM's 2026 survey of 1,780 screen reader users, JAWS was the primary desktop screen reader for 72.5 percent of respondents in North America but only 17 percent in Asia, where NVDA led with 77.4 percent. On phones, 72.2 percent commonly used VoiceOver and 29.5 percent TalkBack. A course for a global workforce has to work in all of them.
eLearning accessibility checklist
Use this list in your brief and at every review round. Each item maps to WCAG 2.1 AA.
- 1Every image, icon and chart has a text alternative (or is marked decorative)
- 2Every narration and video has accurate captions, and a transcript is available
- 3Video that shows important actions has audio description or a described version
- 4The whole course works with a keyboard alone, with a visible focus outline and no traps
- 5Tab and reading order follow the logical order of the screen
- 6Drag-and-drop and other pointer-only tasks have a keyboard or single-click alternative
- 7Text contrast is at least 4.5:1 (3:1 for large text); controls and focus outlines at least 3:1
- 8Color is never the only way to show right, wrong or status
- 9Time limits can be turned off or extended, and audio does not auto-play over a screen reader
- 10Text resizes to 200 percent, and the course reflows on narrow screens
- 11Buttons, headings and links have clear names that make sense out of context
- 12The course has been tested with at least one screen reader by someone who uses it daily
What drives the cost of accessible eLearning?
We quote every project individually. Accessibility is cheapest when it is planned from the storyboard, because nothing has to be rebuilt later. These factors shape the quote:
What you send us and what we prepare
You send You
- Source content (slides, documents, existing ILT materials or SME notes)
- Your accessibility target (WCAG 2.1 AA, Section 508 or your own policy)
- What you know about your learners' needs (no personal data needed)
- Brand guide, fonts and colors
- LMS name and version, and the tracking you need (SCORM 1.2, SCORM 2004 or xAPI)
- Languages and rollout dates
- Names of reviewers, ideally including an assistive technology user
We prepare IKHYA
- Accessibility brief and project plan
- Accessible storyboard with alt text, caption scripts and keyboard routes
- Contrast-checked visual prototype
- The built course, captions, transcripts and text alternatives
- Accessibility test notes for each module
- LMS-tested SCORM or xAPI package
- Editable source files
Proof
Healthcare
Accessible annual mandatory training for a US healthcare provider network
Snapshot: healthcare · about 4,000 clinical and non-clinical employees · 6 new modules · Rise 360 and Storyline 360 · SCORM 2004 · 12 weeks
- Challenge
- The network needed new annual training on privacy, workplace safety and conduct that every employee, including staff who use screen readers, magnifiers and captions, could complete in the same course, with no separate "accessible version".
- What we built
- 4 Rise 360 modules and 2 Storyline 360 scenario modules, built to WCAG 2.1 AA and Section 508. Drag-and-drop sorting became click-to-select choices; every video got captions and a transcript; 2 scenario clips got described versions. We tested with a keyboard, JAWS, NVDA and VoiceOver, then ran a pilot with 5 employees who use assistive technology.
- Results
- The pilot found unclear button names in one scenario and a slide where keyboard focus skipped a question; both were fixed before launch. All pilot issues were closed before rollout, average seat time fell from about 60 to about 40 minutes, and no separate accessible version was needed.
"For the first time, our colleagues who use screen readers took the same course, on the same day, as everyone else. Nobody had to wait for a separate version."
Another IKHYA result: a compliance training overhaul that raised completion and pass rates from 61% to 82% across 1,200 employees.
Accessible eLearning FAQs
Accessible eLearning is online training that people with visual, hearing, motor and cognitive disabilities can perceive, operate and understand without help. It usually means meeting WCAG 2.1 Level AA: text alternatives, captions, keyboard access, enough contrast, clear structure and adjustable time limits.
Most organizations use WCAG 2.1 Level AA. US federal agencies follow Section 508, which requires WCAG 2.0 AA, and US state and local governments must meet WCAG 2.1 AA under the ADA Title II rule. A course built to WCAG 2.1 AA covers the WCAG 2.0 AA level too.
WCAG 2.1 AA is the most widely referenced target and is what we build to by default. WCAG 2.2 adds 9 success criteria, such as a single-pointer alternative to dragging and minimum target sizes, and content that meets 2.2 also meets 2.1. We build to WCAG 2.2 AA on request: if your policy names it, include it in your brief.
It depends on who the course is for. The European Accessibility Act applies from June 28, 2025 to listed products and services for consumers, such as e-commerce and consumer banking; training an employer buys for its own staff is not a listed service. EU public sector bodies follow the Web Accessibility Directive instead. Both rely on EN 301 549, whose web clause maps to WCAG 2.1 AA (Version 3.2.1) or WCAG 2.2 AA (Version 4.1.1). We build to WCAG 2.1 AA by default and WCAG 2.2 AA on request. This is not legal advice.
Selling or training in the EU: EN 301 549 and the European Accessibility Act
No. Scenarios, branching, tabs and knowledge checks can all be accessible when each one has a keyboard and screen reader route. A few patterns, like drag-and-drop, need an alternative way to do the same task.
Articulate states that Storyline 360 and Rise 360 support WCAG 2.1 AA, and Adobe documents screen reader, caption and keyboard support in Captivate. Rise 360 is often the quickest route to a responsive accessible course. The tool only enables accessibility: the author's design and testing decide whether the course conforms.
Our immersive training is 360-degree photo and video scenarios built in Adobe Captivate that play in a web browser. To make them accessible, each scene and hotspot needs a text description, keyboard access, captions on all audio and an equivalent text-based path through the same decisions.
Yes. We publish to SCORM 1.2, SCORM 2004, xAPI or HTML5 and test the package in your LMS. Responsive builds reflow on narrow screens, which WCAG 2.1 also requires at Level AA.
Your source content, accessibility target, LMS details, brand guide, languages and the names of your reviewers. If you can include an employee who uses assistive technology as a reviewer, the course will be better for it.
We quote each project individually. Cost and time depend on course length, interactivity, media, voiceover, languages, the authoring tool, review rounds and LMS testing. Your free quote includes a recommended route and a timeline.
Yes. We work in 40+ languages. Each language version needs its own captions, transcripts and text alternatives, and WCAG 2.1 requires the language of the page to be set (and marked where it changes) so screen readers pronounce the text correctly.
Make your next course accessible from day one
Tell us about your learners, your tool and your LMS. We will reply with a recommended route and a timeline.
