Tool reference · Articulate Rise 360

Articulate Rise 360 captions: glossary-biased WebVTT for responsive microlearning

Articulate Rise 360 is the modern responsive-microlearning surface in the Articulate 360 suite — block-based, mobile-first, browser-authored, the L&D operator's tool for shipping a 10-block "what-changed-in-the-policy" module by lunchtime. Where Storyline 360 handles the higher-production-value slide-based interactives, Rise handles the long tail of microlearning that drives the actual completion-rate numbers. Rise's video block accepts WebVTT captions directly, and the published SCORM/xAPI/Web package carries the captions into the target LMS with no separate caption-upload step. The captioning question on Rise is the same as on every authoring tool: not whether captions are technically supported (they are) but whether the imported VTT preserves the vocabulary the module was built to teach.

TL;DR

Rise 360 supports WebVTT captions on the Video block via the block's caption-import action, with the imported VTT served alongside the video asset in the published SCORM/xAPI/Web package. SRT is not natively accepted at the block level — convert SRT to VTT upstream — though the underlying media-library workflow accepts SRT as a fallback. The technical caption-import is straightforward; the difficulty is upstream: ASR-generated captions on Rise's typical content (policy updates, customer-academy modules, compliance refreshers, sales-enablement explainers) carry the highest proper-noun density of any training surface and mangle predictably. Glossary-biased captioning with the customer's controlled vocabulary preserves these surface forms upstream of the Rise block-import, so the published microlearning module lands clean in the LMS.

What Rise 360 is, and why captioning sits in the block import path

Rise 360 is the browser-authored, responsive, block-based authoring tool in the Articulate 360 suite. Distinguishing characteristics:

Block-based composition. Modules are assembled from a fixed library of pre-styled blocks — text, image, video, accordion, button-stack, knowledge check, scenario, sorting activity, labelled graphic, and so on. The block taxonomy is the design system; authors don't lay out pages, they pick blocks.
Responsive by construction. Every block is designed to render on desktop, tablet, and phone without per-breakpoint authoring. Microlearning consumed on the L&D learner's phone in three minutes between meetings is the design centre.
Cloud-authored. Rise lives in the browser, content lives on Articulate's cloud, multiple authors can co-edit. No installed software, no .story source files passed around.
Publishes to SCORM 1.2 / SCORM 2004 / xAPI / AICC / Web / PDF / Articulate Review. The same publish artefact targets are available as Storyline; the package carries embedded video and captions into the LMS.

The Video block is the captioning surface. A Rise module typically has between zero and a handful of video blocks; captioning lands per-block, not per-slide as in Storyline. This is operationally simpler — less per-module captioning work — but the per-video work has the same vocabulary surface to handle.

The Rise Video block caption-import mechanic

The Video block in Rise 360 accepts a video file (uploaded from disk, or a URL pointing to YouTube / Vimeo / Wistia / Brightcove / Kaltura) plus, optionally, a closed-caption file. The caption-import affordance:

WebVTT (preferred). The Video block's settings pane exposes a "Closed captions" file picker that accepts .vtt directly. The imported VTT is served alongside the video asset in the published package, with the player rendering the CC toggle in the block's own controls.
SRT (via media library fallback). The Articulate 360 media library accepts SRT for video assets, with conversion to WebVTT happening server-side. For SRT-first workflows the block-level VTT requirement is satisfied via this path.
YouTube / Vimeo / Wistia hosted video. When the Video block points at a hosted video URL, the captions are served by the host platform's player, not by Rise. The captioning workflow therefore lands at the host, not in Rise. See our Vimeo captions reference and Wistia captions reference for those host-side mechanics.

The publish setting "Closed captions" toggles whether the player exposes the CC button by default; the published package always carries the imported VTT regardless of the toggle state. For ADA / Section 508 compliance the toggle should be on by default, and the imported VTT should be present.

The vocabulary surface on Rise-authored content

Rise's typical content profile concentrates several vocabulary surfaces because of the format's strengths and the operator's typical use:

Policy-update microlearning. "What changed in the new privacy-policy revision," "the updated PHI handling rule under § 164.530(b)," "the 2026 update to our SOC 2 control register." Citations, framework names, regulatory acronyms.
Customer-academy modules. Product names, feature names, integration names, configuration UI element names. Every customer-facing SaaS product ships these in Rise. The L&D function for customer success teams typically authors these. See sales enablement captions for the related sales-side surface.
Sales enablement explainers. Product names, competitor names, persona names, framework names ("MEDDIC", "Challenger Sale", "Command of the Message"). High proper-noun density.
Compliance-training refreshers. The annual HIPAA / SOX / GDPR / PCI-DSS / ISO 27001 / SOC 2 refresh cycle drives Rise content; framework citations and acronym density per minute is high. See compliance training captions.
Onboarding microlearning. Engineering onboarding (SDK names, command-line tools, internal services), clinical onboarding (drug names, EHR-specific terminology), retail onboarding (product names, vendor codes). See engineering onboarding captions and medical training captions.
Safety-training short modules. Chemical names, OSHA and MSHA citation surfaces, equipment and PPE proper nouns. See safety training captions.

Rise modules are short, but the proper-noun density per minute is typically higher than long-form Storyline content because the format pushes for tight, didactic explanation rather than narrative ramp.

The glossary-biased workflow for Rise modules

Pull the customer's controlled vocabulary. Same step as for Storyline: drug formulary, product-feature catalogue, SDK reference, framework register, locally meaningful organisational vocabulary. Most organisations have a glossary already; loading it once is one-time setup.
Caption the source video upstream. The video file the Rise author plans to insert into the Video block is the capturing surface; caption it with the workspace glossary biasing the decoder, producing a clean WebVTT.
Reviewer pass. Amber-highlight UI shows every glossary-applied term with source-line provenance. The reviewer scrubs each video in minutes; corrections feed the workspace glossary.
Import into the Rise Video block. Block settings pane → Closed captions → upload the WebVTT. Rise serves it alongside the video.
Publish to the target LMS. SCORM / xAPI / Web; the published package carries the captions. No LMS-side caption configuration step.
Document the captioning provenance. Each published module gets a row in the asset register: caption source (vendor + glossary version), reviewer, date, glossary term count. Same audit-evidence shape as for Storyline.

See pricing

Where Rise's "Auto-generate captions" feature falls short

Rise 360 ships an auto-generate-captions feature on the Video block that runs ASR over the imported video and produces a draft caption track. It is convenient for narrator-recorded video where the vocabulary is generic (welcome modules, intro videos, organisational-update messages from the CEO). It fails predictably on the content profiles above.

The failure mode is the same shape as Storyline's auto-caption feature: no access to the customer's controlled vocabulary, so the proper-noun surface mangles. The hand-correction cost lands on the L&D operator after publish — the half-FTE captured nowhere on the L&D budget that our long-form post walks. Glossary-biased captioning upstream of the Rise import is the path that doesn't generate the back-end correction cost.

The Rise back-catalogue retrofit pattern

Rise back-catalogue retrofit is operationally easier than Storyline because the source lives in Articulate's cloud — re-authoring is a browser action, not a re-open-the-source-file-and-republish action. The retrofit pattern:

Inventory the back-catalogue. Articulate 360's content library lists every Rise course; export the list, count the Video blocks per course, identify which use Articulate-hosted video (retrofit-able through this workflow) versus YouTube/Vimeo/Wistia hosted video (retrofit lives at the host).
Bulk-export source video. For Articulate-hosted video, the media library permits download of source assets. Export to a folder structure that mirrors course / block hierarchy.
Glossary-biased re-captioning. Run the exported video through the captioning workflow with the customer glossary. Output: one VTT per video block.
Bulk-update the Video blocks. Per-block, replace the existing caption file with the new VTT. This is manual at the time of writing — no programmatic API for caption swap on Rise blocks — but it's a few-clicks-per-video operation that scales to hundreds of modules in a project.
Re-publish. Rise publishes incrementally; updated modules re-publish to the same SCORM/xAPI/Web target. Most LMSes preserve learner progress on re-upload.

How Rise-published captions land in the major LMS targets

Same portability as Storyline. The published Rise package — SCORM 1.2 / SCORM 2004 / xAPI / Web — carries the embedded captions into:

TalentLMS — the SMB/mid-market default. Embedded captions render via TalentLMS's player without further configuration.
Docebo — mid-market and enterprise. Docebo's player respects embedded VTT.
Absorb LMS — Engage player supports embedded captions in Rise-published packages.
Cornerstone OnDemand — enterprise. The Rise SCORM package lands as a standard learning object; embedded captions render through the Cornerstone player. See our Cornerstone OnDemand captions reference.
Healthstream — for hospital-authored Rise content (less common than Storyline in this vertical, but used).

How Rise captions intersect WCAG 2.1 AA, ADA Title II, and Section 508

Rise modules in scope of ADA Title II (state and local government, public universities, county hospitals) must meet WCAG 2.1 AA from 2026-04-24. Rise modules in scope of Section 508 (federal government and federal contractors) must meet the EN 301 549 / WCAG 2.0 AA technical bar referenced by 36 CFR § 1194.

WCAG SC 1.2.2 (Captions, Prerecorded) is the operative success criterion. Rise modules with no Video block are out of scope for SC 1.2.2; modules with a Video block must carry captions. Rise modules with audio narration on text blocks (uncommon but possible) trigger SC 1.2.1 (Audio-only and Video-only Prerecorded), with a transcript or text-equivalent satisfying that SC. The most common shape — block-text content plus video blocks with captions — passes the audit cleanly when the video captions are present and accurate.

For private-sector L&D operating under indirect ADA Title III, the EAA, AODA, or any of the regional accessibility regimes, the technical caption bar is consistent. See our WCAG 2.1 AA captions reference and our AODA captions reference.