Platform reference · Skilljar · Customer education · Customer academy · ADA Title III · WCAG 2.1 AA · SaaS training

Skilljar captions: customer academy video, ADA Title III, and WCAG compliance for SaaS companies training customers

Skilljar is a customer education learning management system used by SaaS companies to build and operate customer academies — the structured training programs that teach paying customers to use a product effectively, realize value faster, and reduce support burden. Customer academy video content is a legally distinct captioning domain from internal employee training: the audience is external customers, not employees, and the legal frame shifts from ADA Title I (employer accommodation) to ADA Title III (public accommodation). Customer academies that are publicly accessible — where any visitor can access training content, including free certification courses, product overview videos, and "getting started" content — are places of public accommodation under ADA Title III, and WCAG 2.1 AA accurate captions are required on all prerecorded video. Even customer academies that are gated behind authentication face ADA Title III exposure for customers with hearing disabilities who access the academy as part of their contractual relationship with the SaaS vendor. The vocabulary challenge in customer education video is a compound failure mode unlike any other training context: the content is dense with the SaaS vendor's own product names, API method names, feature names, and workflow terminology — which generic speech-to-text systems have not been trained on, because the vendor's product is precisely what distinguishes this company's training from anything in the general language model's corpus.

TL;DR

Skilljar supports SRT and VTT caption file upload for course video, uploaded through the course content editor in Skilljar's admin interface. Skilljar does not auto-generate captions for uploaded video — the caption file must be produced externally. For publicly accessible customer academy content (free courses, onboarding sequences, certification tracks accessible to any visitor), ADA Title III applies and WCAG 2.1 AA-accurate captions are required. For gated customer academy content (requiring login or a license key), Title III still applies as a public accommodation obligation for authenticated customers, and the SaaS vendor has ADA and state-law obligations to customers with hearing disabilities. The central captioning challenge for Skilljar content is vocabulary: the vendor's own product names and feature names are the training content, and generic STT fails on those terms by definition. A company glossary containing all product names, feature names, and API vocabulary is essential for accurate customer academy captioning.

Customer academy video and ADA Title III: the public accommodation analysis

ADA Title III's "place of public accommodation" analysis applies differently to customer education than to internal employee training or general marketing content.

Publicly accessible customer academy content

Many SaaS companies operate Skilljar customer academies where a portion of the content is publicly accessible — free product certification courses, onboarding preview videos, feature overview courses — available to anyone who visits the academy site without logging in. This content is publicly accessible in the same way a Freshdesk Help Center, a YouTube channel, or a HubSpot Academy is publicly accessible: any visitor with a browser can reach and watch the content. ADA Title III (42 U.S.C. § 12181 et seq.) applies to this content as a public accommodation. Visitors with hearing disabilities who cannot access uncaptioned customer academy video are denied equal access to the information the video conveys — the product education that enables them to evaluate the product, onboard effectively, or prepare for certification.

The Title III public accommodation analysis focuses on whether the digital property is accessible to the general public without restriction. A Skilljar academy subdomain (e.g., learn.yourproduct.com) that serves publicly accessible courses qualifies. The commercial nature of the content (the academy exists to serve the vendor's commercial interest in customer adoption and retention) does not create an exception to Title III — commercial websites are paradigmatic examples of Title III-covered public accommodations in US case law.

Gated customer academy: the authenticated-user analysis

Skilljar customer academies that require a login or license key to access are gated — not publicly accessible in the browsable-without-authentication sense. The Title III analysis for gated content is more nuanced. Two theories of liability remain applicable:

The customer relationship theory. Customers with hearing disabilities who have a contractual relationship with the SaaS vendor (they are paying customers or trial users) and who access the gated academy as part of that relationship are in a direct commercial relationship with the vendor. The vendor's ADA Title III obligation under this theory covers the commercial transaction and everything the vendor provides as part of it — including customer training. A customer who cannot access gated customer education due to missing captions is receiving a lesser version of the product they contracted for.
The website nexus theory. Courts in many jurisdictions have applied Title III to gated websites where there is a sufficient nexus to the vendor's physical operations or commercial activities. For SaaS vendors with any physical presence — a US office, a physical sales meeting, a conference exhibit booth — the nexus theory is well-established in the Ninth and other circuits.

The practical result: both public and gated Skilljar customer academy content should be captioned to WCAG 2.1 AA accuracy. The risk profile is highest for publicly accessible content (broadest visitor population, clearest Title III public-accommodation analysis), but gated content is not risk-free.

California Unruh Act exposure for SaaS customer academies

California's Unruh Civil Rights Act (Cal. Civ. Code § 51) provides $4,000 per incident in statutory minimum damages for ADA Title III violations. For a SaaS company with a Skilljar customer academy, the Unruh exposure is substantial:

California has the highest concentration of SaaS customers in the US — most SaaS companies have a large fraction of customers in California.
Each uncaptioned video that a California-resident customer or visitor encounters is a potential separate incident, at $4,000 per encounter.
A Skilljar academy with 50 courses, each containing five video modules, has 250 potential Unruh incidents per California-resident visitor who encounters the uncaptioned content.
California plaintiffs' attorneys have brought serial Unruh Act web-accessibility cases against SaaS companies; customer academy video libraries are identifiable as accessible-content targets.

Section 1557 for healthcare SaaS vendors with Skilljar academies

SaaS vendors in healthcare — clinical software, EHR integrations, patient engagement platforms, healthcare analytics — that operate Skilljar customer academies and receive federal financial assistance (Medicare/Medicaid revenue flow-through, NIH grants, federal hospital contracts) may also face Section 1557 (ACA healthcare nondiscrimination, 89 Fed. Reg. 37,522) obligations. Section 1557's effective-communication and WCAG 2.1 AA web-content requirements apply to covered entities' customer-facing digital properties. A healthcare SaaS vendor whose hospital customers access training on Skilljar as part of their software subscription may have Section 1557 exposure for uncaptioned customer academy video if the vendor is a "covered entity" or "covered entity vendor" under the 2024 HHS rule. See Section 1557 captions for the detailed scope analysis.

The compound vocabulary failure mode in customer education video

Customer education video has the most severe vocabulary failure mode of any training content type — more severe than internal employee training on external software, and more severe than compliance training with regulatory vocabulary. The reason is structural: customer education video is specifically about the vendor's own product, which means every word that matters in the training content is a word the vendor invented. Generic speech-to-text systems have not been trained on the vendor's product names, feature names, API method names, or internal workflow terminology. The failure is not random — it is systematic, affecting every significant noun in the training content.

Product and feature name failures

Consider a SaaS company whose product has features named "SmartSync," "FlowBuilder," "DataBridge," and "InsightPanel." These names are compound proper nouns invented by the product team — they appear in the product UI, the product documentation, and every customer training video. Generic STT transcribes them as "smart sync," "flow builder," "data bridge," and "insight panel" — phonetically correct but missing the capitalisation and compounding that distinguish them as product names. A customer following a training video caption that says "configure the smart sync settings" instead of "configure the SmartSync settings" cannot navigate the product UI to find "SmartSync" if the UI labels the feature with the capitalised compound form. The practical usability impact of generic captions on customer training is direct and measurable: customers who rely on captions to learn the product have a worse product learning experience than customers who can hear the audio.

API and developer documentation vocabulary

For SaaS products with developer components — APIs, SDKs, CLI tools, webhooks — customer education includes technical training for developer customers. Technical customer education video is among the most vocabulary-dense content type: API endpoint names (POST /api/v2/workflows), SDK method names (client.initialize()), CLI command names, configuration parameter names, and error message text all appear in screen-capture training content. Generic STT transcribes code-style vocabulary poorly: backtick-enclosed code, camelCase method names, and slash-delimited endpoint paths all produce incorrect transcriptions. A developer customer relying on training video captions to understand an API endpoint workflow cannot copy-paste a correctly transcribed endpoint path from a caption that renders it incorrectly.

Integration and workflow vocabulary

Customer education video for integration-heavy SaaS products (products that connect to Salesforce, HubSpot, Zendesk, Slack, Jira, or similar platforms) requires accurate transcription of both the vendor's own product vocabulary and the integrated platform's vocabulary. A training video about setting up the Salesforce integration for a CRM data enrichment tool will reference the vendor's own API objects, the Salesforce objects (Lead, Opportunity, Account, Contact), the Salesforce field API names (in snake_case), and the integration configuration terminology. Two vocabulary layers from two distinct product namespaces compound in a single training video. The generic STT failure rate on a bi-platform integration training video is higher than on a single-platform video.

Certification vocabulary

Many Skilljar customer academies include certification programs — the vendor's own product certification (for example, "Certified [Vendor] Administrator," "Certified [Vendor] Developer") that customers or partners earn by completing a curriculum and passing an assessment. Certification-track video training is the most high-stakes customer education content: customers who are preparing for certification need to understand the vocabulary precisely, because the certification assessment uses exact product terminology. Captions that mis-transcribe product-specific certification terms directly impair the exam preparation of hearing-impaired certification candidates.

Skilljar caption upload workflow

Skilljar supports SRT and VTT caption file upload for video content in courses. The caption file is attached at the lesson level in Skilljar's course editor.

Uploading captions to a Skilljar lesson

For video content in Skilljar courses:

Produce a corrected SRT or VTT caption file for the video using glossary-biased transcription. The company glossary should include all product names, feature names, API vocabulary, and integration vocabulary used in the training video.
In Skilljar's admin interface, navigate to the Training Portal → Courses → [Course] → [Lesson] and open the lesson editor.
For video uploaded directly to Skilljar, use the caption/subtitle upload option in the video lesson editor to attach the SRT or VTT file. SRT is the most widely supported format for Skilljar video caption upload; confirm the current format support in Skilljar's admin documentation.
For video embedded from Wistia, Vimeo, or YouTube, captions are managed at the originating platform (Wistia video settings, Vimeo video settings, YouTube Studio) and the corrected caption track propagates automatically to the Skilljar-embedded player.
Save the lesson. The attached caption track will be available to learners in the Skilljar player across all devices.

Wistia-hosted customer academy video

Many SaaS companies who build Skilljar academies use Wistia as the underlying video hosting platform — embedding Wistia videos in Skilljar lesson pages. The Wistia Skilljar integration allows Wistia-hosted video to be embedded in Skilljar courses with the Wistia player, which supports Wistia's native caption tracks. For Wistia-hosted Skilljar video, caption management is through the Wistia video settings interface (Settings → Captions → Upload a caption file). A corrected SRT uploaded to the Wistia video propagates to all Wistia player embeds including the Skilljar-embedded player.

Vimeo-hosted customer academy video

Some Skilljar customers use Vimeo for professional-quality customer training video. Caption management for Vimeo-hosted Skilljar content is through Vimeo's video settings → Distribution → Subtitles. See Vimeo captions for training videos for the Vimeo SRT upload workflow and the Vimeo API approach for bulk caption uploads across a large customer academy library.

YouTube-hosted customer academy video

Some customer academies embed YouTube video (unlisted or channel-organized) in Skilljar courses. Caption management for YouTube-embedded content is through YouTube Studio → Subtitles. YouTube auto-generated captions on customer education video fail systematically on product vocabulary, as described above. Uploading a corrected SRT to YouTube Studio replaces the auto-generated track and propagates to all Skilljar embeds of that video. See Loom captions for screen-capture product walkthrough captions if the team uses Loom for quick demo recordings embedded in Skilljar.

See GlossCap pricing

Customer education captioning: business case beyond compliance

Accessible customer education is not only a legal compliance obligation — it is a product-quality and customer-success investment. The business case for accurate customer academy captions extends beyond avoiding ADA Title III exposure:

Customer success outcomes for hearing-impaired customers

Customers with hearing disabilities who use your SaaS product deserve the same onboarding and training experience as customers without disabilities. A customer who onboards through a Skilljar academy with inaccurate captions on every product terminology video has a longer time-to-value, a higher support ticket rate, and a higher churn risk than a customer who onboards through accurately captioned content. Customer education investment that excludes hearing-impaired customers from accurate training is investment that does not fully pay off for that customer segment.

Global accessibility and international expansion

Skilljar customer academies deployed for global customers serve non-native English speakers who rely heavily on captions to follow product training in English. While this is not a disability accommodation in the ADA sense, accurate captions on product vocabulary words are just as valuable for non-native English speakers as for hearing-impaired native speakers — and the global reach of a SaaS customer academy means that the accessible-captioning investment benefits a much larger population than the hearing-impaired fraction alone. A customer in Germany or Japan following an English-language Skilljar training video with accurate product vocabulary in the captions has a materially better training experience than with auto-generated captions that mangle the product names.

Certification program integrity

If your Skilljar academy includes a certification program with practical or exam components, the integrity of the certification is at stake for hearing-impaired candidates. A certification that cannot be fairly completed by hearing-impaired candidates is both an accessibility violation and a brand problem — customers who complete a vendor certification expect it to mean something, and a certification that excludes a class of candidates by virtue of inaccessible training undermines that meaning.

FAQ — Skilljar captions

Does Skilljar provide built-in caption generation for video content?

Skilljar does not have a built-in speech-to-text captioning engine that auto-generates captions for customer-uploaded video. When you upload an MP4 to a Skilljar lesson or embed a video from an external platform, the video is served to learners without captions unless you separately attach a caption file (SRT or VTT) or the originating video platform provides its own captions. For video uploaded directly to Skilljar, you produce the SRT/VTT externally and upload it through the lesson editor. For video embedded from Wistia, Vimeo, or YouTube, captions are managed at the originating platform. The practical implication for a SaaS company with a Skilljar academy: every video lesson in your academy needs an externally produced and attached caption file to meet WCAG 2.1 AA standards. For a mature academy with 200+ video lessons, a batch captioning project for the existing library — using a glossary-biased captioning pipeline that captures your product vocabulary — is the right starting point before investing in per-video manual review workflows.

Our Skilljar academy is gated — customers need a license key to access it. Does ADA Title III still apply?

Yes, with some nuance. The primary theory of Title III liability for gated customer academy content rests on the commercial relationship between the SaaS vendor and its customers. A customer who pays for a SaaS product and receives access to the vendor's Skilljar academy as part of the subscription is in a direct commercial transaction with the vendor. Courts have applied Title III to gated commercial relationships where there is sufficient nexus to a place of physical accommodation or to a commercial activity covered by Title III. For SaaS vendors with US physical offices (which is most SaaS companies), the nexus theory for gated online content is well-established in the Ninth Circuit and recognized in other circuits. Additionally, if your Skilljar academy includes any publicly accessible content — free courses, onboarding previews, certification overviews visible without login — that public portion triggers Title III directly for those pages. A best-practice approach is to treat the entire customer academy as within Title III scope, regardless of gating, because the commercial relationship with customers creates a duty to provide accessible service, and the lines between gated and public content on a Skilljar subdomain can be administratively unclear to enforce separately.

Our SaaS product is technical — customers are developers using our API. Does our Skilljar developer education content need captions?

Yes. Developer education video — API tutorials, SDK walkthroughs, code-along training, integration setup guides — is subject to the same ADA Title III captioning obligation as any other customer-facing training video. Developer communities include professionals with hearing disabilities, and developer education without accessible captions excludes those customers from the vendor's developer ecosystem. The vocabulary challenge for developer education video is particularly acute: code-style vocabulary (endpoint paths, method names, parameter names, error codes) is the content of the training, and generic STT handles code-style vocabulary very poorly. A developer following a captioned API tutorial where POST /api/v2/leads is rendered as "post api v2 leads" without the slash notation or capitalisation cannot reliably implement the integration from the caption alone. Accurate captions for developer education require a glossary that includes all API endpoints, all SDK class and method names, all CLI command names, and all configuration parameter names in the developer documentation. The glossary-biased Whisper approach handles code-style vocabulary significantly better than generic STT because the glossary explicitly tells the model to expect specific strings — though for inline code, the combination of a glossary and post-processing for code formatting produces the most accurate results.

How does the caption quality obligation differ between free public courses and paid certification tracks in Skilljar?

The caption quality obligation — WCAG 2.1 AA SC 1.2.2 accuracy — is the same for both free public courses and paid certification tracks. However, the stakes of caption quality differ. For free public courses, the primary risk is Title III exposure for public-accommodation visitors who encounter inaccurate captions. For paid certification tracks — where a customer or partner has paid specifically to earn a certification and relies on the training to pass — inaccurate captions directly impair the customer's ability to complete the paid product they have purchased. This creates both a Title III exposure (the certification track is a commercial service offered to the public) and a contractual exposure (a hearing-impaired customer who cannot effectively complete a paid certification they purchased because of inaccessible video may have a breach-of-contract or unjust-enrichment claim independent of ADA). Certification tracks should be prioritized in captioning workflows precisely because the stakes of caption quality are highest there: a certification candidate who fails an exam because their caption-based preparation misled them about product terminology has a concrete, measurable harm.

We use both Skilljar and Gainsight CS — should our customer education captioning strategy cover both platforms?

Yes. If your organization uses Gainsight Customer Success alongside Skilljar for customer education, and if Gainsight CS surfaces training video (via Gainsight's in-app engagement features, Digital Journey video steps, or Knowledge Center Bot video content), that video is also subject to ADA Title III captioning obligations if it is accessible to customers with hearing disabilities. The captioning strategy should cover all platforms through which you deliver video content to customers — not just the primary customer academy LMS. Gainsight's in-app engagement tools (PX, Journey Orchestrator) that include video components are ADA-covered for customer-facing video. The caption workflow for in-app video components embedded in Gainsight typically goes through the video hosting platform (Wistia, Vimeo, or YouTube) from which the video is embedded — the same upstream-source captioning approach described in this reference for Skilljar-embedded video. A holistic customer education captioning strategy covers the Skilljar academy (structured courses), the in-app engagement layer (Gainsight, Appcues, or similar), the customer-facing help center (Zendesk Guide, Freshdesk Help Center, or similar), and any other digital touchpoint where customers access video as part of their relationship with the vendor.