GlossCap

Platform reference · Degreed · Learning Experience Platform · ADA Title I · WCAG 2.1 AA · Corporate learning · Skills intelligence

Degreed captions: LXP custom content, learning pathways, and ADA compliance for corporate learning teams

Degreed is a learning experience platform (LXP) used by hundreds of enterprise and mid-market organizations to aggregate external learning content, build employee skill development pathways, measure skill progress, and surface learning opportunities. Unlike traditional learning management systems that act as a single video repository, Degreed primarily works as a content aggregator — pulling in courses from LinkedIn Learning, Pluralsight, Coursera, Udemy for Business, and dozens of other external providers — while also supporting employer-uploaded custom content including proprietary training video. The captioning challenge on Degreed is structurally distinct from a traditional LMS: for external content aggregated from provider platforms, captioning is the content provider's responsibility and is typically already present; for employer-uploaded custom video, Degreed has no built-in speech-to-text captioning capability and the employer is responsible for providing a captioned video or VTT sidecar file. This means Degreed customers who upload proprietary training video — company onboarding, product-specific training, internal methodology walkthroughs — must caption that content before or at upload, or provide a VTT alongside the upload. For hearing-impaired employees, uncaptioned custom video in Degreed's custom content library is a barrier to accessing required or recommended training, triggering employer accommodation obligations under ADA Title I and equivalent state and international disability employment laws.

TL;DR

Degreed supports VTT caption file upload for custom employer-uploaded video content. The caption file is attached to the video content item in Degreed's admin interface at content creation or editing time. Degreed does not generate captions automatically for employer-uploaded video — the caption file must be produced externally and uploaded. External content aggregated from LinkedIn Learning, Pluralsight, or Coursera typically carries its own provider-generated captions and does not require employer action. The employer's captioning obligation is specifically for custom-content video that the employer has uploaded to Degreed from its own production. Compliance: ADA Title I (employer accommodation for hearing-impaired employees) and EAA (for EU-deployed Degreed instances) both require that required or mandated training content available through Degreed be accessible to employees with hearing disabilities via accurate captions. The vocabulary failure mode is in the company-specific training content: Degreed's own platform vocabulary is modest, but the employer's product vocabulary, business-process vocabulary, and internal acronym register are the captioning challenge.

Degreed as a learning experience platform — content model and captioning structure

Understanding Degreed's captioning structure requires understanding what Degreed is and is not as a platform. Degreed is an LXP — a Learning Experience Platform — rather than an LMS. The distinction matters for captioning:

LXP vs LMS: the structural captioning difference

A traditional learning management system (LMS) — Cornerstone OnDemand, Docebo, TalentLMS, Absorb LMS, Workday Learning — is primarily a content repository. Employers upload SCORM packages, MP4 videos, and course files directly into the LMS, and the LMS delivers that content to learners. Captioning obligations for employer-uploaded LMS content fall entirely on the employer.

An LXP like Degreed operates differently. Degreed is first a content aggregation and curation layer: the learning experience is primarily assembled from third-party provider content (LinkedIn Learning, Pluralsight, Coursera, O'Reilly, Udemy for Business, Skillsoft, Harvard ManageMentor, and many others). Those third-party providers own the captioning quality of their content — a LinkedIn Learning course already has captions because LinkedIn Learning produces captions on its own platform (see LinkedIn Learning captions for the employer's residual obligations even with captioned external content). Degreed's custom content layer is where employer-produced video enters: when a company uploads its own training video to Degreed as custom content, that video is subject to the employer's captioning obligation.

Custom content in Degreed

Degreed's custom content library allows employers to add their own learning items that are not sourced from external providers. Custom content items in Degreed include videos, articles, and other media. For video custom content, an employer can upload an MP4 directly or link to a video hosted on an external platform (a YouTube URL, a Vimeo URL, a Loom link, or a SharePoint/OneDrive video). The captioning approach depends on how the video is added:

Pathways and the aggregation model

Degreed's core UX is the Pathway — a curated sequence of learning items (videos, articles, courses, events) assembled by an L&D team or by Degreed's AI. Pathways for compliance training, onboarding, technical skill building, or leadership development typically combine external provider content with employer-uploaded custom content. Captioning is needed at the item level: each video item in a Pathway needs captions regardless of whether it is external provider content or employer custom content. For a Pathway that mixes LinkedIn Learning courses (already captioned) with employer-uploaded onboarding videos (not yet captioned), the employer's action is needed only for the custom-uploaded items.

Opportunities, Initiatives, and Required Learning

Degreed's platform allows L&D administrators to designate content as Required Learning (mandatory training with due dates and completion tracking), to create Initiatives (skill-building campaigns tied to organizational goals), and to surface learning Opportunities (recommended content aligned to career paths or skill gaps). Required Learning in Degreed has a heightened captioning obligation: if an employer designates a video as required training with a compliance deadline, a hearing-impaired employee who cannot access the content due to missing or inaccurate captions is directly disadvantaged relative to hearing colleagues in fulfilling a mandatory employment requirement. Required Learning with uncaptioned video is a cleaner ADA Title I employer accommodation violation claim than a general observation that "some training video lacks captions."

ADA and EAA compliance for Degreed custom content

The captioning obligation for Degreed custom content flows from multiple independent legal sources, each with different reach and enforcement mechanisms.

ADA Title I: employer accommodation (42 U.S.C. § 12112)

ADA Title I prohibits employment discrimination by employers with 15 or more employees against qualified individuals with disabilities. Accessible training materials — including training video that hearing-impaired employees can follow with accurate captions — are a core component of the reasonable accommodation obligation. The standard analysis:

For Required Learning with hard due dates, the accommodation response must be timely — the employer cannot require a hearing-impaired employee to defer completion of mandatory compliance training until captions are produced. Pre-captioning all required and frequently assigned training content is operationally more efficient than reactive per-employee captioning.

California FEHA and state disability employment laws

California's Fair Employment and Housing Act (Gov. Code § 12940) applies to employers with five or more employees — covering a large fraction of Degreed-using organizations. FEHA's reasonable accommodation requirement for hearing-impaired employees mirrors ADA Title I but at a lower employer-count threshold. New York's Human Rights Law (4+ employees) and New Jersey's Law Against Discrimination (no employee minimum) extend the accommodation obligation to essentially all employers who have employees in those states. For large and mid-market organizations using Degreed, state-level accommodation obligations compound the federal Title I obligation across all employment states where hearing-impaired employees may be located.

European Accessibility Act for EU-deployed Degreed

Degreed has EU-based customers, and the European Accessibility Act (EAA, Directive 2019/882), enforceable from June 2025, requires that digital learning services provided in the EU comply with WCAG 2.1 AA, as referenced through EN 301 549 V3.2.1. For a Degreed deployment at a company with EU-based employees, the custom content deployed through Degreed constitutes a digital service provided to EU workers, and WCAG 2.1 AA SC 1.2.2 (synchronized captions on prerecorded video) applies. Unlike ADA Title I, the EAA frames this as a service-provider obligation rather than specifically an accommodation obligation — the entire digital service must be accessible, not just specific accommodations for identified individuals. See EAA captioning requirements and EN 301 549 captions for the detailed EAA technical standard.

WCAG 2.1 AA SC 1.2.2 as the technical standard

WCAG 2.1 AA Success Criterion 1.2.2 requires synchronized captions on all prerecorded video. For employer-uploaded custom content in Degreed, the compliance question is whether the VTT attached to the content item provides captions that accurately represent the audio — including company-specific vocabulary, product names, internal acronyms, and business-process terminology. Auto-generated captions produced by a consumer STT system and attached as-is to Degreed content do not satisfy SC 1.2.2 for specialized training content. See WCAG captions for prerecorded media for the SC 1.2.2 interpretation in training contexts.

The vocabulary failure mode in Degreed custom content

Unlike platform-specific training tools (where the main vocabulary challenge is the platform's own product names), the primary vocabulary challenge in Degreed custom content is the employer's own vocabulary — the company-specific product names, internal project codenames, business-process terminology, and acronym register that are unique to that organization. Degreed's own platform vocabulary is relatively modest, but the content uploaded to Degreed as custom training is where the employer's proprietary terminology creates the most severe captioning failures.

Company product and service vocabulary

For a 50-500-employee SaaS company using Degreed for employee learning, the custom content library typically includes training on the company's own product: "here is how our platform works," "here is the new feature we launched this quarter," "here is how to demo the integration to enterprise prospects." Every product name, feature name, API method name, and internal product-team codename in that training content is a potential STT failure. Generic Whisper-large transcription of a SaaS company's product training video routinely produces incorrect transcriptions for SDK method names, product-tier names, and internal feature codenames — exactly because these are not in any general language model's training data.

Internal acronym registers

Companies develop dense internal acronym registers over time: department names (GTM team, CS org, MLE team, BDR team), project names (Project Aurora, Phoenix Initiative, Tiger Team), and business-process abbreviations (QBR, SKO, OKR tracking terminology, RACI matrix terms). These acronyms, said aloud in an internal training video, are transcribed by generic STT as phonetically similar common words: "GTM" → "G-T-M" or "got them," "BDR" → "B-D-R" or "bidder," "QBR" → "Q-B-R" or "cue BR." In onboarding training — exactly where internal acronyms appear most densely — these errors systematically confuse new employees who are hearing these terms for the first time and relying on captions for context.

Technical and engineering vocabulary in skill-building content

Engineering organizations using Degreed for technical skill development often upload custom content covering the company's own infrastructure, internal developer tooling, proprietary data pipelines, and codebase conventions. Technical vocabulary in this content — cloud service names, internal SDK names, database table conventions, CLI tool names — fails severely in generic STT. The combination of a custom Degreed deployment for a technical organization with employer-uploaded engineering training video is one of the highest-priority captioning scenarios precisely because the vocabulary failure surface is most severe and the hearing-impaired viewer's ability to follow along is most critically dependent on accurate technical terminology in the captions.

Degreed platform vocabulary

Degreed's own platform vocabulary, while less dense than the employer's custom content vocabulary, still creates failure points in training that teaches employees how to use Degreed itself:

Practical caption workflow for Degreed custom content

The captioning workflow for Degreed custom content depends on how the content is hosted and surfaced in Degreed's interface.

Direct MP4 upload: VTT sidecar attachment

For custom content videos uploaded as MP4 directly to Degreed's content library, the caption workflow is:

  1. Produce a corrected VTT caption file for the video using glossary-biased transcription. The VTT format is required for Degreed caption attachment (SRT is not supported for direct Degreed attachment in most versions of the platform interface — confirm the current format requirements in the Degreed admin documentation at the time of upload, as the platform may update format support).
  2. In Degreed's admin interface, navigate to the content item (Content Library → [Content item] → Edit) and upload the VTT file in the Captions/Subtitles section of the content settings.
  3. Save the content item. The attached VTT will be displayed as a caption track when the video plays in Degreed's video player for learners on any device.
  4. If the content item is part of a Pathway, the VTT captions are served when the video plays inline within the Pathway context — no additional Pathway-level configuration required.

YouTube-linked external content

For custom content items where the video is linked from YouTube (an internal-unlisted YouTube video, for example), caption management is through YouTube Studio: upload a corrected SRT to the YouTube video, and the corrected captions propagate to the Degreed-embedded player. For companies that host internal training video on YouTube (unlisted, or in a private YouTube channel with restricted access), the YouTube Studio caption workflow is the operative path. The YouTube SRT upload process is standard: YouTube Studio → the video → Subtitles → Add language or Edit → Upload file.

Vimeo, Loom, and Wistia-linked external content

Many organizations using Degreed link custom content from Vimeo (for professionally produced training video), Loom (for quick screen-capture walkthroughs), or Wistia (for polished L&D libraries). In each case, caption management is at the originating platform:

Microsoft Stream-linked content (M365 integration)

Degreed has an M365 integration that surfaces SharePoint and Teams content in Degreed pathways. Training video hosted in Microsoft Stream (SharePoint-integrated Stream) and surfaced in Degreed through the M365 connector is captioned at the Stream layer. The VTT upload workflow for Microsoft Stream video is documented at Microsoft Stream captions. For companies that use Degreed as the learning layer on top of a Microsoft 365 video infrastructure, the Stream captioning workflow is the upstream action point for all M365-hosted content that flows into Degreed.

See GlossCap pricing

Degreed vs LMS platforms: captioning responsibility comparison

Organizations that have both a Degreed LXP and an LMS — a common enterprise configuration where Degreed sits on top of a formal LMS like Cornerstone OnDemand, Workday Learning, or Docebo — need to understand where captioning responsibility lies for each type of content.

Content originated in the LMS, surfaced in Degreed

When Degreed integrates with an LMS via xAPI or SCORM API, LMS content can be surfaced in Degreed's learning experience layer while the content actually lives in the LMS. Captions on this content are managed at the LMS level — changes to caption files at the LMS propagate to the Degreed-surfaced experience. The LMS's captioning workflow (for example, Workday Learning's VTT sidecar workflow or Cornerstone's caption management interface) is the operative captioning path for this content.

Content uploaded directly to Degreed, bypassing the LMS

Some organizations upload content directly to Degreed that is not managed through the formal LMS — informal knowledge sharing, subject-matter-expert screen recordings, quick team updates. This content bypasses the LMS governance workflow, which means it also bypasses any LMS-enforced captioning quality gates. Content teams that use Degreed as a low-friction "post a video" channel for informal learning need to include captioning in that informal workflow — not just for content in the formal LMS channel — to avoid creating an uncaptioned shadow library that accumulates unchecked.

FAQ — Degreed captions

Does Degreed automatically generate captions for custom-uploaded video?

No. Degreed does not have a built-in speech-to-text captioning engine for employer-uploaded custom content. When you upload an MP4 to Degreed's custom content library, the video is served to learners without captions unless you separately produce and upload a VTT caption file. This is different from some LMS platforms that have added auto-captioning features (often using Azure Cognitive Services or similar) — Degreed's platform-level captioning support is limited to accepting a VTT file that you produce externally. The external content Degreed aggregates from LinkedIn Learning, Pluralsight, Coursera, and other providers typically already has captions produced by those providers, but that does not carry over to your own custom content. The practical implication: every piece of custom video content your organization uploads to Degreed needs a separately produced and attached VTT caption file to be accessible to hearing-impaired employees.

Our organization uses Degreed alongside Cornerstone OnDemand. Where should captions be managed?

The general principle is to manage captions where the content source of truth lives. Content that lives in Cornerstone OnDemand and is surfaced in Degreed via an LMS integration should have captions managed in Cornerstone — the Cornerstone caption workflow is the upstream action point. Content that lives in Degreed's own custom content library (uploaded directly to Degreed, not sourced from Cornerstone) should have captions managed in Degreed via the VTT attachment workflow. The risk in a dual-system architecture is that "Degreed-native" content (content posted directly to Degreed, outside the Cornerstone governance workflow) accumulates without the captioning quality gates that formal LMS governance imposes. L&D teams operating in a Degreed + Cornerstone environment benefit from a policy that treats Degreed-native content uploads as subject to the same captioning requirements as Cornerstone uploads — the informal, lower-friction Degreed channel should not become an uncaptioned exception to an otherwise captioning-compliant training library. See Cornerstone OnDemand captions for the Cornerstone-specific workflow.

Does Required Learning in Degreed have a different compliance obligation than optional content?

Yes — Required Learning in Degreed carries a heightened obligation relative to optional or recommended content. When an organization designates a Degreed content item as Required Learning with a completion deadline, hearing-impaired employees who cannot access the content due to missing or inaccurate captions are being denied access to mandatory employment requirements on equal terms with hearing colleagues. An ADA Title I reasonable accommodation analysis applied to Required Learning with uncaptioned video is straightforward: the employee has a disability-related barrier to completing a job requirement, and the employer has failed to provide an accessible version. The employer cannot require the employee to defer completion or to seek an ad hoc accommodation after the fact when the barrier is the employer's own failure to caption mandatory training. Proactively captioning all Required Learning content before it is assigned to employees eliminates this exposure. For optional and recommended content, the obligation is the same in principle but the immediacy of the exposure is lower — the accommodation request typically arises when a specific employee indicates interest and encounters the barrier.

How do I handle external content in Degreed (LinkedIn Learning, Pluralsight) for hearing-impaired employees — is the content provider responsible?

For external content aggregated from a provider like LinkedIn Learning, Pluralsight, or Coursera, the provider is responsible for captioning quality on their platform's content — and those providers generally do caption their courses, meeting their own accessibility obligations. However, the employer has a residual obligation: if an external provider's captions are inaccurate for the specific content that the employer has assigned as Required Learning, the employer cannot simply point to the provider's captions as "good enough." If the provider's captions are genuinely inadequate for a specific course that the employer has mandated, the employer should request accessibility improvements from the provider or find an alternative resource that provides accurate captions. For external content that is optional or recommended (not required), the employer's obligation is softer — you are relying on the provider's captions for non-mandatory content, which is generally defensible as long as you are not turning a blind eye to a known, systematic accessibility failure in a key learning resource. See LinkedIn Learning captions for the specific employer obligation split on LinkedIn Learning custom content versus LinkedIn-produced library content.

We are a US company with EU-based employees using Degreed — does the EAA apply to our Degreed deployment?

The European Accessibility Act (EAA) applies to digital services provided in the EU market. If your organization deploys Degreed for EU-based employees and custom training content in Degreed is part of that service, the EAA's WCAG 2.1 AA requirements apply to the accessible delivery of that content. The EAA frames this as a service-level obligation — the entire digital learning service should be accessible — not merely as a per-employee accommodation. In practice, for a US company with EU employees using Degreed, this means custom training video deployed to EU employees should have WCAG 2.1 AA-accurate captions. The EAA enforcement timeline and penalty structure varies by EU member state (each member state transposed the directive into national law), but the compliance obligation has been in effect since June 2025. Germany (BFSG), France (RGAA), Netherlands (WCAG-based legislation), and other member states have each transposed the EAA — the applicable national law depends on which member states your EU employees are in. See EAA captioning requirements for the EAA scope and technical standard.

Further reading