eLearning Accessibility Guide 2026: WCAG 2.1, Section 508 & Online Course Compliance

Who Must Make eLearning Accessible

eLearning accessibility isn't a single regulation — it's a patchwork of overlapping legal requirements that apply differently depending on who's creating the content, who's using it, and how it's funded.

Federal Agencies and Government Contractors: Section 508

The Rehabilitation Act's Section 508 requires federal agencies to make all electronic and information technology — including online training — accessible to employees and members of the public with disabilities. The 2018 Section 508 refresh explicitly adopted WCAG 2.0 Level AA as the standard for web content, and the general direction of enforcement has moved toward WCAG 2.1 AA.

Government contractors who develop eLearning content for federal agencies must meet 508 requirements as a contract condition. Failure to deliver accessible content is a contract compliance issue, not just a legal technicality.

Universities and K–12: ADA Title II and Section 504

Educational institutions that receive federal funding — which includes virtually all public universities and K–12 districts — must ensure that all online course content is accessible to students with disabilities under Section 504 and ADA Title II. The DOJ's April 2024 Title II rulemaking formally adopted WCAG 2.1 AA as the compliance standard, with phased deadlines based on institution size.

The OCR (Office for Civil Rights) actively investigates and resolves complaints about inaccessible LMS content, video-only materials, and inaccessible course documents. Settlement agreements with universities like MIT, Harvard, and dozens of smaller institutions have established detailed remediation requirements.

Corporate Training: ADA Title I

Employers with 15 or more employees must provide reasonable accommodations to employees with disabilities under ADA Title I. If mandatory corporate training is inaccessible to an employee with a visual impairment or hearing loss, the employer may be required to provide an accessible alternative as a reasonable accommodation — or face an EEOC complaint.

Corporate training companies selling to employers have a strong commercial incentive beyond compliance: enterprise procurement teams increasingly require a VPAT (Voluntary Product Accessibility Template) before purchasing any training platform or content library.

WCAG 2.1 Requirements That Most Affect eLearning

1.2 — Time-Based Media (Captions and Transcripts)

This is where most eLearning content fails. WCAG's 1.2 criteria cover all time-based media — video, audio, and synchronized presentations:

• 1.2.1 (Level A) — Pre-recorded audio-only and video-only content must have a text alternative or audio description. Podcast modules and narrated-but-no-video content need a written transcript.
• 1.2.2 (Level AA) — Pre-recorded video with audio must have synchronized captions. This is the caption requirement. Auto-generated captions from YouTube or your video platform count only if reviewed and corrected — raw auto-captions with errors don't meet this standard.
• 1.2.3 (Level A) — Pre-recorded video must have audio descriptions (a narration of visual content that isn't apparent from the audio alone) or a full media alternative.
• 1.2.5 (Level AA) — Pre-recorded video must have audio descriptions. This is stricter than 1.2.3 — a transcript doesn't satisfy this criterion at AA level.

In practice: every lecture video, demo walkthrough, and software simulation with narration needs (1) synchronized captions and (2) audio descriptions for any visual content the narration doesn't explicitly describe.

2.1 — Keyboard Accessibility

Every interaction in an eLearning course must be operable by keyboard without requiring a mouse. This is not a theoretical requirement — people with motor disabilities routinely use courses via keyboard, switch access, or other alternative input methods.

Common keyboard accessibility failures in eLearning:

• Drag-and-drop with no keyboard path — categorization, sequencing, and matching interactions built purely as mouse-drag operations with no keyboard equivalent
• Custom media players with inaccessible controls — play/pause, scrub, volume, and caption toggle buttons that only work with mouse clicks
• Modal dialogs and overlays that trap focus — pop-up instructions, tooltips, or feedback panels that keyboard users can't dismiss or navigate out of
• Carousel/slide navigation without keyboard support — next/previous controls that don't respond to arrow keys or Tab

2.2 — Enough Time

Timed activities — countdown quizzes, timed knowledge checks, and session timeouts — must give users the ability to turn off, adjust, or extend time limits (WCAG 2.2.1, Level A). The exception is when the time limit is essential to the content (like a typing speed test), but most corporate and academic eLearning timers are assessment design choices, not inherent requirements.

LMS session timeouts are a common failure: learners using screen readers take longer to navigate content, and automatic logouts can cause data loss if the timeout is too short or the warning isn't accessible.

1.1 — Text Alternatives for Non-Text Content

All informational images must have alt text (WCAG 1.1.1, Level A). In eLearning, this extends to:

• Screenshots of software interfaces — when showing "click this button" instructions using a screenshot, the alt text should describe the relevant part of the interface, not just say "screenshot"
• Charts and graphs in slide decks — the data the chart represents must be communicated in text, either as alt text or in a visible caption/table
• Infographics — complex infographics need either detailed alt text or a full text alternative describing all the information conveyed
• Text rendered in images — slide headings or callouts that were created as PNG images rather than real HTML text (a common artifact of some authoring tools)

Accessible Quiz and Assessment Design

Knowledge checks and assessments are where eLearning accessibility most often breaks down. Here are the key principles:

Multiple Choice Questions

Multiple choice is the most accessible question type when built correctly. Requirements:

• Each answer option must be a labeled radio button or equivalent ARIA role — not a custom-styled clickable div
• The question stem must be programmatically associated with the radio group (using fieldset and legend, or ARIA role="group" with aria-labelledby)
• Correct/incorrect feedback must not rely on color alone — use an icon, text label, or sound in addition to green/red coloring
• If immediate feedback appears after each question, focus must be managed so screen reader users hear the feedback automatically

Drag-and-Drop Interactions

Drag-and-drop activities (sort, match, categorize, sequence) are the most problematic interaction type for accessibility. WCAG 2.5.1 (Level A) requires that any drag functionality have an equivalent single-pointer (or keyboard) path. Solutions:

• Select-then-place: Allow users to click an item to select it, then click the target zone to place it — no continuous drag required
• Numbered dropdown alternative: Alongside the drag interface, provide a dropdown or text field where users can specify the order or category for each item
• Arrow key movement: Selected items can be moved between zones using arrow keys after being "picked up" with Enter or Space

Fill-in-the-Blank and Short Answer

Text input fields must have visible, associated labels (not just placeholder text). If context makes the label redundant, usearia-label or aria-labelledby to provide a programmatic label. Error messages for incorrect answers must be specific and describe what the correct format should be (if the answer is being checked against a specific pattern).

Authoring Tool Accessibility Comparison

The accessibility of your final course is heavily influenced by your authoring tool. No tool produces fully accessible output without intentional effort, but some are significantly better starting points.

Lectora (by ELB Learning) has the longest track record of accessibility-focused development and is the default choice for Section 508 government projects. Articulate Rise — the newer, responsive format — produces cleaner HTML than Storyline and is generally more accessible out of the box. Storyline requires more manual accessibility work but offers more design flexibility.

LMS Platform Accessibility

Even if your course content is fully accessible, learners interact with your content through an LMS — and an inaccessible LMS shell creates barriers regardless of course quality.

• Canvas by Instructure — the accessibility leader among major LMS platforms. Has a published VPAT, dedicated accessibility team, and strong screen reader compatibility across its navigation, discussion boards, and grade book. Canvas Accessibility Checker built into the rich content editor helps instructors catch issues in course pages.
• Moodle — core Moodle is highly accessible; accessibility of a deployed Moodle installation depends heavily on the theme and plugins chosen. The Boost theme is more accessible than many alternatives.
• D2L Brightspace — good keyboard support and screen reader compatibility; active VPAT maintenance. A strong choice for higher education.
• Blackboard/Anthology — has improved substantially since 2020 but legacy modules remain less accessible. New Ultra Experience is more accessible than original view.
• Cornerstone OnDemand — commonly used in corporate settings; has a VPAT but has received mixed screen reader feedback. Testing before procurement is important.

Accessible eLearning Design Checklist