LearnWorlds Accessibility Checklist 2026 | WCAG 2.1 AA & EAA Compliance

Course videos uploaded to LearnWorlds or embedded from a host frequently play with no captions. Deaf and hard-of-hearing learners, and anyone watching with sound off, cannot follow spoken instruction. Auto-generated captions from a video host, if present at all, are often inaccurate for technical or domain-specific vocabulary, which still fails the spirit of 1.2.2 because the captions are not equivalent to the audio. Education content is heavily scrutinized for exactly this gap, and a course built entirely on uncaptioned video is one of the most common and most serious complaints.

Captions cover spoken words, but learners who are blind also need the meaningful visual information conveyed in a lesson, and many learners simply prefer a text transcript to skim or search. LearnWorlds lessons often present a video alone with no accompanying transcript or description of on-screen demonstrations, slides, or diagrams. When the video shows something the narration does not describe out loud (a screen recording of clicks, a chart, code on screen), that information is lost to non-sighted users, failing the requirement for an alternative for time-based media.

Images inside lessons, in Site Builder sections, and course/category thumbnails are often inserted without alternative text. Screen reader users hear only a filename or nothing at all, so diagrams, screenshots and infographics that carry instructional meaning become inaccessible. Decorative images that are not marked as decorative add noise instead. On a course catalog page, thumbnails without alt text leave the listing ambiguous for non-sighted learners deciding what to enroll in.

In the lesson text editor, creators often style headings by making text big and bold rather than using real heading levels, or they skip levels (H2 straight to H4). Screen reader users navigate by headings, so a flat or scrambled structure makes long lessons hard to scan and breaks the programmatic outline. This also affects Site Builder pages where multiple H1s or no H1 can appear. The information and relationships in your content are then not conveyed in code, failing 1.3.1.

LearnWorlds theming lets you pick brand colors, and a common failure is light gray text on white, pale buttons, or low-contrast link colors that fall below the 4.5:1 ratio required for normal text (3:1 for large text and UI components). On course cards, enroll buttons, and player overlays this makes key actions hard to read for users with low vision or in bright conditions. Because the theme applies site-wide, a single bad color choice cascades across every page.

Quizzes and assessments built in LearnWorlds can present open-answer fields, fill-in-the-blanks, or surveys where the input has no programmatically associated label, only nearby visible text or placeholder hints. Screen reader users then reach an unlabeled field and cannot tell what to enter. Placeholder text alone is not a label and disappears on typing. Without clear instructions and labels, learners may answer the wrong question or be unable to complete a graded assessment at all.

When a learner submits a quiz or form with a missing or invalid answer, the error is sometimes shown only with a color change (a red border) or a generic message, with no text saying which question failed or why. Color-blind learners and screen reader users may not perceive that anything is wrong, or cannot find the offending field. On a timed or graded assessment this is especially frustrating and can unfairly cost a learner their result.

LearnWorlds interactive video lets you add clickable hotspots, questions and buttons over a playing video. If these overlays respond only to mouse clicks and cannot be reached or activated with the Tab and Enter keys, keyboard-only and many switch or screen reader users are locked out of the interaction, and possibly out of progressing through the lesson if a hotspot is required. This is a hard blocker that fails 2.1.1 because functionality is not available from a keyboard.

Pop-ups such as interactive video questions, lightboxes, or checkout modals can trap keyboard focus: once a learner tabs into the overlay they cannot tab back out or close it without a mouse. This strands keyboard and screen reader users, who may be unable to reach the rest of the lesson or even leave the page. It is the classic no keyboard trap failure (2.1.2) and is particularly damaging in a course flow where the modal gates further progress.

Workbooks, slide decks and certificates offered as PDF downloads in LearnWorlds are often untagged, scanned as flat images, or lacking a reading order and headings. Screen reader users then get garbled output or nothing readable, and the document fails the same structure requirements as a web page. Because course handouts are core learning material, an inaccessible PDF can make a whole module unusable for some learners even when the on-platform content is fine.

Lessons or Site Builder sections set to autoplay video or background audio can start sound automatically when a page loads. This disorients screen reader users (the audio competes with their screen reader voice), distracts learners with cognitive disabilities, and is simply intrusive. If sound plays for more than three seconds with no easy way to pause or stop it, it fails 1.4.2. Autoplaying course intros are a frequent culprit.

The registration, login and checkout forms are where money and access are decided, yet fields sometimes rely on placeholder text instead of real labels, custom buttons lack an accessible name, and the keyboard focus indicator is faint or removed by the theme. Screen reader users may not know what a field is for, and keyboard users cannot see where they are while filling out payment details. A learner who cannot complete checkout cannot buy the course, so this is both an accessibility and a revenue problem.