SAP Enable Now captions: screen-record training, guided procedures, and WCAG 2.1 AA compliance for SAP implementation training

SAP Enable Now — what it is and what it produces

SAP Enable Now is an enterprise digital adoption platform in the same market category as WalkMe, Whatfix, and Oracle User Productivity Kit (UPK). Within the SAP ecosystem it is the purpose-built authoring and delivery tool for SAP-specific training content. Understanding what SAP Enable Now produces, and where video fits in that output, is the foundation of the captioning analysis.

SAP Enable Now content types

• Simulation mode recordings. The Producer authoring tool records a narrator's interactions with the live SAP system — clicking through SAP Fiori tiles, entering values into SAP GUI transaction screens, navigating menu paths in S/4HANA — and generates a step-by-step guided simulation from the recording. The simulation plays in four modes: Demo mode (watch the correct steps played back), Practice mode (guided simulation — the learner follows on-screen instructions to complete the steps), Test mode (unguided — the learner completes the transaction without on-screen help), and Concurrent mode (the learner works in the real SAP system while Enable Now overlays guidance). Simulation objects contain narration audio recorded by the trainer or a voice-over narrator.
• Book Pages. Static help documentation pages published in the Manager repository, often embedding simulation objects. Book Pages serve as permanent reference material for SAP end users looking up how to complete a specific transaction or Fiori app workflow.
• Presentations. Narrated presentations built in Producer, typically used for process overviews, policy training, and organisational context training (e.g. explaining the SAP Organisational Structure — Company Code, Plant, Sales Organisation, Distribution Channel — before drilling into transaction-level simulations).
• Guided Procedures. Context-sensitive in-application help that is triggered when the user opens a specific SAP Fiori application. The SAP Companion widget detects the user's current application context (which Fiori tile they launched, which T-code they are in) and presents the relevant guided procedure as an overlay. Guided procedures can include narration audio.
• Videos (exported MP4). Producer exports simulation recordings and presentations as MP4 video files — full-motion narrated screen-record video of the SAP interaction. These MP4 exports are the primary captioning surface; they contain the narration audio as a synchronised audio track and have no embedded caption data until a caption file is added externally.
• SAP Enable Now Manager. The backend content management portal where producers publish content, manage content groups, control learner access, and distribute training to learners. Manager can host video and simulation content for direct learner access, or it can serve as the source for LMS import.
• SAP Enable Now Companion. The browser extension or desktop client that delivers context-sensitive help to SAP users as they work in SAP Fiori applications or SAP GUI. The Companion surfaces guided procedures and simulation-based walkthroughs as in-application overlays; any narration audio in Companion-delivered content requires captions for WCAG compliance.

Why captioning SAP Enable Now output is mandatory, not optional

SAP customers who are US employers have ADA Title I obligations — employees with hearing disabilities must be able to access mandatory training content. SAP training is not supplementary; it is the mechanism by which employees learn to perform their job function in the organisation's ERP system. A hearing-impaired SAP end user who cannot access captioned S/4HANA transaction training is disadvantaged in job performance in a way that directly implicates the ADA Title I reasonable-accommodation standard.

Beyond individual accommodation, the systematic captioning gap in SAP training libraries — where an entire 400-video go-live training set has no caption files — creates organisational risk. Section 508 applies to US federal agencies and many contractors who purchase SAP products; EAA applies to EU-based SAP customers producing training content within the EU accessibility framework. The scale of SAP training libraries at large enterprises means the remediation cost of retroactively captioning an uncaptioned library is substantial; the prophylactic cost of captioning at authoring time is a fraction of that.

The SAP vocabulary failure mode — why generic STT produces wrong captions on SAP training

SAP training video has the highest proprietary-software vocabulary density of any enterprise application training content. This is not a minor inconvenience — it is a fundamental failure of generic STT on SAP content. The SAP vocabulary failure mode operates across five distinct layers, each of which individually would challenge generic ASR and which in combination create near-total caption unreliability on SAP training narration.

Layer 1 — SAP application and product family names

The SAP product portfolio spans dozens of application families, each with a name that appears in training narration in both full and abbreviated form. Generic STT fails on these because the abbreviated forms are short, phonetically ambiguous, and absent from general speech-to-text training corpora in their SAP-specific meaning:

• SAP S/4HANA — the core ERP. Spoken as "S-4-HANA," "S/4," "S4HANA," or "S-4." Generic STT produces "S4 Hana," "S for Hana," "S-for-Hana," "SFORNA," or drops the product name entirely. The slash in S/4HANA is invisible to ASR; the spacing and capitalisation vary by narrator.
• SAP HANA — the in-memory database platform. Spoken as "HANA" or "S-A-P HANA." Substitution to "Hannah" is the canonical generic STT failure on this term.
• SAP Fiori — the UX design system and application launchpad for S/4HANA. Spoken as "Fio-ree" (correct) or colloquially with variations. Generic STT produces "feary," "fiery," "Fiore," "Fiorey," or "FI-oh-ree" depending on the narrator's accent. Every SAP Fiori training module references this term dozens of times.
• SAP GUI — the legacy Windows client used for hundreds of SAP transactions that have not yet been Fiori-enabled. Spoken as "S-A-P gooey" or "S-A-P G-U-I." Generic STT handles "GUI" inconsistently — "gooey," "G.U.I.," "Goodie," or "GUI" without the SAP prefix. For organisations still training on ECC or hybrid S/4HANA environments, SAP GUI is a constant in training narration.
• SAP ECC — ERP Central Component, the legacy pre-S/4HANA system. Spoken as "E-C-C" or "SAP ECC 6.0." Many organisations are mid-migration from ECC to S/4HANA and run training on both systems simultaneously.
• SAP BTP — Business Technology Platform (formerly SAP Cloud Platform). Spoken as "B-T-P" or "SAP BTP." Generic STT produces "BTP" correctly when the training corpus context is present, but in SAP training narration the acronym often appears without prior context ("log in to BTP and open the integration suite"), producing false matches to "BDP," "BTB," or generic three-letter sequences.
• SAP SuccessFactors — the HCM suite. Module names within SuccessFactors are individually challenging: Employee Central (correctly transcribed, but the SAP-specific meaning is not captured), Performance & Goals (ampersand rendering varies), Recruiting, Onboarding, Learning, Compensation, Succession & Development — each individually correct in isolation but contextually misread when spoken at pace in SuccessFactors training narration.
• SAP Analytics Cloud (SAC) — spoken as "S-A-C" as an acronym. "SAC" → "sack" is the canonical failure mode — generic STT phonetic substitution produces the English common noun rather than the product acronym. Training narrators who say "open SAC and navigate to the planning model" will produce "open sack and navigate to the planning model" in uncorrected auto-captions.
• SAP Ariba — procurement and sourcing. Spoken as "Ariba." Generic STR handles "Ariba" relatively well, but "Ariba Network," "Ariba Sourcing," and "Ariba Buying and Invoicing" compound into phrases that generic STT often splits or elides. "Ariba" → "a RIBA" or "a riba" (treating it as a non-capitalised English phrase) is a recurring failure mode.
• SAP Concur — travel and expense management. "Concur" is an English verb ("I concur"), so generic STT produces uncapitalised "concur" consistently, erasing the product-name signal. Training narration about "Concur Expense reports" or "Concur Travel booking" produces "concur expense reports" — grammatically coherent but factually wrong.
• SAP Datasphere — data warehousing (formerly SAP Data Warehouse Cloud). A newer product name; generic STT has minimal exposure to "Datasphere" as a single compound word and splits it: "data sphere," "data-sphere," or substitutes "data sphere" for the product name throughout a training module.
• SAP Signavio — process intelligence and business process management. "Signavio" is an Italian-origin word with no English common-noun equivalent. Generic STT failures: "Sig-navio," "Signavi-oh," "signavio," "sign AVIO." Every Signavio training module title and narration reference is corrupted in auto-captions.
• SAP Build — low-code/no-code platform. Build Apps, Build Process Automation, Build Work Zone. "Build" is a common English verb; "SAP Build" as a product family name is invisible to generic STT without a capitalisation-aware prefix. "Use SAP Build to create your process" → "use SAP build to create your process" — the product boundary is erased.

Layer 2 — SAP module abbreviations

SAP's modular architecture is described using two-letter and multi-letter abbreviations that are spoken as letter-sequences in training narration. Generic STT has no grounding for these as SAP-specific vocabulary items:

• FI — Financial Accounting. Spoken as "F-I" or "the FI module." Generic STT: "fee," "phi," "fie" — consistently wrong. "FI configuration" → "fee configuration" or "phi configuration."
• CO — Controlling. Spoken as "C-O" or "the CO module." Generic STT: "co" (a prefix rather than an acronym), "C.O.," "co-" — the module identifier disappears into prefix morphology.
• SD — Sales and Distribution. Spoken as "S-D." Generic STT: "S.D.," "SD" (sometimes correct), or phonetically "es-dee." For training narrators who speak quickly, "the SD module" becomes "the SD module" in transcription only when contextual SAP vocabulary is present.
• MM — Materials Management. Spoken as "M-M" or "the MM module." "MM" appears correctly in generic STT only when the model resolves the repeated letter; "em em" is a common failure.
• PP — Production Planning. Spoken as "P-P" or "the PP module." "P-P" resolves to "pp" (a musical dynamic marking), "P.P.," or is dropped. "Run the PP planning run" → "run the P.P. planning run" at best.
• HCM — Human Capital Management. Three-letter acronym; generic STT handles it better than two-letter module codes, but "HCM" in the context of "the on-premise HCM system" vs "SAP SuccessFactors" (the cloud HCM) creates a disambiguation problem that only a SAP-aware glossary resolves.
• PM/EAM — Plant Maintenance / Enterprise Asset Management. "PM" as an abbreviation in an enterprise context competes with "project management," "product manager," and "private message" in generic STT disambiguation. Without an SAP glossary, "open the PM module" resolves to its generic-abbreviation meaning.
• CO-PA — Profitability Analysis within the CO module. Spoken as "CO-PA" or "Copa." "Copa" is a Spanish/Portuguese common noun (cup, competition); generic STT produces "copa" or "co-PA" or "Copa" — none of which conveys the correct SAP controlling sub-module identity.

Layer 3 — SAP transaction codes (T-codes)

SAP transaction codes are the direct-access shortcuts used in SAP GUI and referenced in training narration for S/4HANA and ECC environments. T-codes are pronounced as letter-number sequences and are entirely absent from generic STT training data as SAP-specific vocabulary:

• FB01 — Post Document (FI). Spoken as "F-B-zero-one" or "FB01." "F-B-zero-one" → "FB zero one" (correct structure), but many narrators say "F-B-oh-one" (treating 0 as "oh"), producing "FB-oh-one," "FBO1," or "f B O 1" depending on spacing heuristics.
• FB60 — Enter Vendor Invoice. Spoken as "F-B-sixty" or "FB-sixty." "FBsixty" or "F B 6 0" — the concatenation of letters and numbers challenges generic STT spacing rules.
• VA01, VA02, VA03 — Create/Change/Display Sales Order. "VA01" spoken as "V-A-zero-one," "V-A-oh-one." The distinction between VA01 (create), VA02 (change), VA03 (display) is operationally critical in SD training — a hearing-impaired learner who cannot distinguish these T-codes from each other or from their generic ASR substitutes cannot follow the transaction training.
• ME21N, ME22N — Create/Change Purchase Order (new MM transactions). "ME-twenty-one-N" or "ME-twenty-two-N." The trailing "N" (for "new," distinguishing from legacy ME21/ME22 without N) is critical vocabulary; generic STT often drops it or renders it as "en" separated from the numeric string.
• MIGO — Goods Movement. Spoken as "M-I-G-O" or "Migo." "Migo" as a spoken word maps to a proper noun (a name) or an Italian exclamation in generic ASR; the transaction code identity is lost.
• MIRO — Invoice Verification. Spoken as "M-I-R-O" or "Miro." "Miro" resolves to the visual collaboration tool (Miro) or a proper name; the MM transaction identity is lost.
• FBL3N — GL Account Line Item Display. "F-B-L-3-N" or "FBL3N" — a six-character alphanumeric sequence that generic STT renders as fragments: "FBL 3N," "FBL3 N," "F.B.L. 3 N," or other non-concatenated forms.
• MD04 — Display Stock/Requirements List (MRP). Spoken as "M-D-zero-four" or "MD04." "MD04" → "MD 04" (spaced), "M.D. 04" (period-separated), or "MDO4" (letter-substitution for zero).
• BP — Business Partner (S/4HANA replacement for Customer Master and Vendor Master). Spoken as "B-P" or "the BP transaction." "BP" as a generic abbreviation competes with "blood pressure," "British Petroleum," and dozens of other BP expansions in generic ASR disambiguation. An SAP glossary anchors "BP" to its SAP Business Partner meaning in SAP training context.

Layer 4 — SAP Organisational Units and Master Data objects

SAP's hierarchical Organisational Structure defines how a company's legal entities, plants, sales channels, and controlling areas are represented in the SAP system. Training narrators reference these structures constantly — explaining which Organisational Unit to enter in a transaction, how to filter data by Company Code, how cost flows from Plant to Profit Center. These are multi-word proper nouns that generic STT treats as common-noun phrases, losing the SAP-specific capitalisation and identity signal:

• Company Code — the primary legal entity unit in SAP FI. Spoken as "Company Code." Generic STT: "company code" (lower-case) — the term is recognisable, but its status as an SAP Organisational Unit proper noun is erased.
• Plant — the operational unit in SAP MM and PP. Spoken as "Plant" in an SAP context where it means manufacturing/warehouse/operational site, not a botanical entity. Generic STT renders "plant" correctly but without SAP-specific capitalisation or disambiguation from common-noun usage.
• Sales Organisation, Distribution Channel, Division — the SD Organisational Structure hierarchy. "Sales Organisation" is recognisable; "Distribution Channel" is recognisable; "Division" in an SD context has a very specific meaning distinct from common-noun "division." Training narrators who say "enter your Sales Org, Distribution Channel, and Division" produce correct generic STT transcription of the words, but the status of these as SAP Organisational Unit proper nouns is invisible without a glossary.
• Controlling Area — the CO Organisational Unit that spans Company Codes for management accounting. "Controlling Area" → "controlling area" — phonetically transparent but contextually invisible to generic STT without SAP context.
• Profit Center, Cost Center, Business Area — FI/CO master data objects. These are recognisable compound nouns, but their SAP-specific meanings — and the criticality of capitalisation in training content that refers to them as named objects — require glossary anchoring.
• Material Master, Customer Master, Vendor Master, GL Account, Cost Element — SAP master data object types. In S/4HANA, Customer Master and Vendor Master have been replaced by the unified Business Partner (BP) model; training narration that explains this migration uses all these terms in close proximity, and generic STT handles the transition terminology poorly.
• Credit Control Area — the SAP unit for managing customer credit exposure across Company Codes. "Credit Control Area" as an SAP proper noun vs "credit control area" as a generic operational concept — the distinction exists in capitalisation and context, not phonetics.

Layer 5 — SAP Enable Now-specific authoring vocabulary

SAP Enable Now training videos often narrate the Enable Now authoring and delivery process itself — training teams that produce "training on how to use training tools" reference Enable Now's own product vocabulary:

• Producer — the SAP Enable Now authoring tool. Spoken as "Producer" or "SAP Enable Now Producer." Generic STT renders "producer" as the common English noun — the tool-name identity is lost.
• Manager — the SAP Enable Now content repository. Spoken as "Manager" or "Enable Now Manager." Same capitalisation-erosion failure as "Producer."
• Companion — the in-app help overlay. Spoken as "Companion" or "SAP Companion." "SAP Companion" → "SAP companion" — lower-cased, product identity lost.
• Instant Producer — the browser-extension-based recording tool for Companion content. Spoken as "Instant Producer." "Instant Producer" is a two-word product name that generic STT renders as common English without capitalisation.
• Learning Map — the visual learning path with progress tracking in Manager. "Learning Map" → "learning map" — recognisable but not capitalised as the product feature name.
• Demo mode, Practice mode, Test mode, Concurrent mode — the four simulation delivery modes. These are Enable Now-specific terms for specific simulation interaction paradigms; generic STT correctly transcribes the words but without the product-context capitalisation that Enable Now documentation uses.
• Bubble text — in-simulation instructional overlay callouts. Spoken as "bubble text." "Bubble text" is correctly transcribed by generic STT as common English; however, in Enable Now training videos that walk through the Producer interface, "bubble text" is a UI element name that should be consistently capitalised per Enable Now documentation conventions.
• Offline Player — the desktop application for offline SAP Enable Now content delivery. "Offline Player" → "offline player" — product name lost to lower-casing.
• SAP Companion for Desktop — the Companion client for SAP GUI transactions (as opposed to Fiori). "SAP Companion for Desktop" as a multi-word product name is fragile in generic STT; "SAP Companion" might be transcribed correctly but "for Desktop" as a product qualifier is often rendered in lower case or elided.

The SAP SuccessFactors Learning vocabulary layer

Most large SAP customers distribute SAP Enable Now training videos through SAP SuccessFactors Learning — the SAP LMS that is part of the SAP SuccessFactors HCM suite. When an SAP training team narrates a tutorial about how to use SAP SuccessFactors Learning itself — assigning curricula, managing completion status, uploading SCORM content — a second vocabulary layer appears on top of the SAP application vocabulary: the SuccessFactors Learning administrative vocabulary. This is common in SAP implementation projects where the training team is simultaneously deploying SuccessFactors Learning as the distribution platform and creating Enable Now content to train administrators on how to use it.

• Items — the learning content objects in SuccessFactors Learning. The SuccessFactors-specific usage of "Item" as a formal object type (not a generic list item) is vocabulary that generic STT cannot distinguish from the common noun without a glossary.
• Curricula — structured learning paths in SuccessFactors Learning (note: SAP uses "Curricula," not "Curriculum" as the plural form, distinguishing the SAP-specific technical term from standard English). Generic STT produces "curricula" correctly but without the SuccessFactors-specific context that "Curriculum" in SuccessFactors Learning has a defined object type with specific behaviours distinct from a generic curriculum.
• Programs — SuccessFactors Learning's blended-learning planning container, distinct from common-noun "programs." The SuccessFactors meaning of "Program" as a structured blended-learning enrollment plan is an SAP-specific vocabulary item.
• Assignments — system-generated or admin-assigned learning obligations. "Assignment" in SuccessFactors Learning is a formal record object with a due date, completion status, and escalation path. Generic STT transcribes "assignment" as the common English noun — the SAP-specific operational meaning is invisible.
• Completion Status values — Completed, Not Started, In Progress, Waived, Exempt. Training narrators who say "the learner's status is Waived" need "Waived" as a proper-noun status code in the caption, not the common adjective "waived." The capitalisation distinction is the product-vocabulary signal.
• Super Admin, HR Admin, Content Admin, Report Admin — SuccessFactors Learning role names. These role names appear in SuccessFactors Learning administration training and are SAP-defined role identifiers, not generic job title descriptions.
• SCORM 1.2, SCORM 2004, xAPI — content packaging formats that SAP SuccessFactors Learning supports. "SCORM" as a spoken acronym ("S-C-O-R-M") is handled inconsistently by generic STT — "scorm," "S.C.O.R.M.," "sco-rm" — with version numbers ("1.2," "2004") further complicating the transcription. "xAPI" spoken as "ex-A-P-I" or "x API" produces "extra P.I.," "X API," or "XAPI" depending on the generic STT model's spacing heuristics.

Caption workflow for SAP Enable Now video exports

SAP Enable Now does not include auto-captioning. The path from Enable Now MP4 to compliant captioned video requires external captioning tools. The complete workflow:

Step 1 — Export video from SAP Enable Now Producer

In SAP Enable Now Producer, select the simulation or presentation object and use Export → Video → select resolution (typically 1920×1080 or 1280×720) → MP4 output. The exported MP4 includes the narration audio track as a synchronised audio channel. The exported file has no embedded caption data — no SRT, no VTT, no burned-in text. This MP4 with narration is the captioning input.

For organisations with large Enable Now content libraries, batch export via the Enable Now Producer command-line export option (where available) or scripted export jobs reduces the manual overhead for bulk processing. A go-live training library of 300 simulation videos can typically be batch-exported in a single overnight run.

Step 2 — Assemble the SAP glossary

The SAP glossary for the captioning workspace has two layers:

• SAP base vocabulary layer. All SAP product family names (S/4HANA, Fiori, SuccessFactors, Ariba, Concur, BTP, Analytics Cloud, Datasphere, Signavio, Fieldglass, etc.), all SAP module abbreviations (FI, CO, SD, MM, PP, HCM, PM, EAM, QM, PS, BW), all common T-codes for the modules in scope (FB01, FB60, VA01, VA02, VA03, ME21N, ME22N, MIGO, MIRO, FBL3N, KSB1, CO01, MD04, BP, VF01, VF02, VK11, MM01, MM02), all SAP Organisational Unit names (Company Code, Plant, Sales Organisation, Distribution Channel, Division, Purchasing Organisation, Profit Center, Cost Center, Business Area, Controlling Area, Credit Control Area), all SAP Enable Now product vocabulary (Producer, Manager, Companion, Learning Map, Demo mode, Practice mode, Test mode, Concurrent mode). This base layer is shared across all SAP customer implementations — the vocabulary is standardised across the SAP product portfolio.
• Customer-specific overlay. The customer's SAP Organisational Unit names and codes (e.g. "Company Code 1000 — US OPCO," "Plant 1200 — Chicago Distribution Centre"), the customer's SAP custom configuration names, the implementation partner's naming conventions for project deliverables, the customer's SAP system landscape names (DEV, QAS, PRD system identifiers), and any customer-specific SAP custom developments (Z-transactions, Y-transactions, customer-specific Fiori app names). This layer comes from the implementation project's configuration documentation and the enable-now production team's script library.

Step 3 — Caption with SAP glossary-biased decoding

Upload the exported MP4 to GlossCap. The SAP glossary biases the Whisper-large decoder — at each decoding step, token probabilities for SAP vocabulary items are elevated, ensuring that "F-B-zero-one" resolves to "FB01," "Fio-ree" resolves to "SAP Fiori," "S-A-C" resolves to "SAP Analytics Cloud (SAC)," and "ME-twenty-one-N" resolves to "ME21N" rather than their generic phonetic near-matches. The output is a draft VTT and SRT for each exported video.

Step 4 — Reviewer pass

Every glossary-applied term is highlighted in the GlossCap reviewer UI with source-line provenance — which layer of the SAP glossary applied the correction, and what the raw ASR output would have been without the glossary. For SAP training content, the reviewer is typically an SAP functional consultant or a trained Enable Now content author who knows the SAP vocabulary. The reviewer pass typically takes 5–15 minutes per 5-minute training video, compared with 45–90 minutes for the same video captioned from generic ASR output without glossary bias.

Step 5 — Distribute caption files

The reviewed VTT and SRT files are ready for distribution. The path depends on how the SAP training is delivered:

• SAP SuccessFactors Learning. Upload the captioned MP4 as an Item in SuccessFactors Learning, then attach the SRT/VTT as a subtitle track to the video resource. SuccessFactors Learning's video player renders the CC toggle with the attached caption file. For SCORM-packaged Enable Now content uploaded to SuccessFactors Learning, the caption track must be embedded in the SCORM package at authoring time (see Step 6 below).
• SAP Enable Now Manager (direct). For Enable Now content delivered directly through the Manager portal (rather than through SuccessFactors Learning), publish the captioned video to the Manager content group. Manager's video player will render the caption file if attached correctly to the video object.
• Kaltura. For organisations using Kaltura as the enterprise video platform for SAP training distribution (common at large enterprises that have standardised on Kaltura for all video), upload the MP4 and attach the VTT via Kaltura's caption asset API.
• TalentLMS. For SAP partner organisations or mid-market SAP customers using TalentLMS as the distribution LMS, upload MP4 plus SRT as a TalentLMS course content item.
• Docebo. For enterprise SAP customers using Docebo as their primary LMS alongside or instead of SuccessFactors Learning, upload MP4 plus VTT sidecar to the Docebo course.

Step 6 — SCORM packaging with embedded captions

Many SAP implementation training libraries are packaged as SCORM for LMS distribution — particularly for compliance training, onboarding training, and modules that need quiz-based completion tracking. If Enable Now content is packaged as SCORM (either directly from Enable Now Producer's SCORM export or assembled in Articulate Storyline using Enable Now MP4 as an embedded video), the caption track must be embedded in the SCORM package at authoring time. The VTT produced in Step 4 is imported into the Storyline slide or the SCORM package wrapper before final publication. The published SCORM package carries the captions embedded; the LMS (SuccessFactors Learning, Docebo, TalentLMS, Cornerstone, or any SCORM-compliant target) plays the captioned content without additional configuration.

See GlossCap pricing

No built-in STT in SAP Enable Now — the systematic captioning gap

SAP Enable Now Producer does not include speech-to-text auto-captioning for its video exports. This is not an oversight that is likely to be corrected soon — the product's architecture focuses on guided simulation authoring and context-sensitive help delivery, not on multimedia accessibility tooling. The absence of built-in STT in Enable Now creates a systematic gap in SAP training accessibility at scale.

Bubble text is not a caption substitute

A common misconception among SAP training teams is that the bubble text in Enable Now simulations — the instructional overlay callouts that guide learners through each simulation step — serves as an accessibility substitute for audio captions. It does not. The bubble text and the narration audio are distinct content layers with different functions and different timing:

• Bubble text is display text in the simulation overlay, not a timed caption track. In Demo mode playback, bubble text appears at step boundaries (not synchronised to milliseconds of narration audio). In Practice and Test modes, bubble text is triggered by user interaction, not by audio playback.
• In MP4 video exports of Enable Now simulations, bubble text appears as burned-in overlay text on the video frame at the authoring-time step transitions — not as a synchronised caption track that maps to the narration audio timeline. The WCAG SC 1.2.2 requirement is for a synchronised caption track, not for on-screen display text.
• Bubble text does not cover all narration — narrators frequently speak between step boundaries, providing context that is not captured in the bubble text at any step.
• Enable Now's exported MP4 does not carry a WebVTT or SRT caption data structure derived from bubble text. There is no mechanism in Producer that converts bubble text to a synchronised caption file on export.

The practical upshot: every Enable Now MP4 export that contains narration audio and has not had an external VTT/SRT file generated and attached is an uncaptioned video for WCAG SC 1.2.2 purposes, regardless of how much instructional text appears on the video frame as bubble text.

The scale of the uncaptioned SAP training library problem

A typical SAP S/4HANA implementation at a 3,000-employee enterprise produces the following training volume from the Enable Now authoring team:

• FI go-live training: 40–60 simulation videos covering GL posting, AP invoice entry, AR collections, bank reconciliation, asset capitalisation, period-end close procedures
• CO training: 20–30 videos covering cost center reporting, internal order management, profit center analysis, CO-PA reporting
• SD training: 30–50 videos covering the Order-to-Cash process — sales order creation (VA01), delivery processing, billing (VF01, VF02), pricing condition management (VK11)
• MM training: 30–50 videos covering the Procure-to-Pay process — purchase order creation (ME21N), goods receipt (MIGO), invoice verification (MIRO), inventory management
• PP training: 20–40 videos covering production order creation (CO01), MRP execution, goods issue, production confirmation
• HCM/HR training: 20–40 videos covering personnel actions, infotype maintenance, time management, payroll processing
• Fiori Launchpad and navigation training: 10–20 videos covering Fiori launchpad personalisation, tile navigation, search, settings
• SAP Enable Now Companion administration training: 5–15 videos covering Companion installation, configuration, context activation

Total: 175–325 video modules for a single S/4HANA go-live. None of them ship with caption files from Enable Now Producer. All of them have narration audio with SAP vocabulary that generic STT cannot handle reliably. This is the captioning gap that SAP implementation training teams inherit by default.

Compliance framework for SAP training video

SAP training video produced for US and EU organisations exists within a multi-layered compliance framework. The relevant obligations for SAP customers vary by sector and jurisdiction, but the practical captioning obligation is uniform: WCAG 2.1 AA SC 1.2.2 (Captions, Prerecorded) requires synchronised captions on all prerecorded video with synchronised audio. The SAP training library is exactly this content type — there are no exemptions that typically apply to SAP training video at a US employer or EU business.

ADA Title I — US employer obligations

ADA Title I (29 CFR Part 1630, implementing 42 U.S.C. § 12112) prohibits disability discrimination in employment, including in the provision of training. SAP customers are US employers. Their SAP training video — the mechanism by which employees learn to perform their job functions — is subject to the ADA Title I reasonable-accommodation framework. An employee with a hearing disability who requires captions to access SAP training has a protected accommodation request under ADA Title I. The employer's obligation is to provide the accommodation — captions on the training video — not to provide a separately scheduled in-person training alternative.

The ADA Title I captioning obligation does not specify a technical standard (it is a functional access standard), but the DOJ's WCAG 2.1 AA technical reference for the ADA Title II context (28 CFR Part 35, effective 2026-04-24) is increasingly the de facto technical benchmark that ADA Title I accessibility counsel recommends. Captioning SAP training video to WCAG 2.1 AA SC 1.2.2 satisfies both the Title I functional standard and the de facto technical benchmark simultaneously.

Section 508 — US federal agencies and contractors

Section 508 (29 U.S.C. § 794d) requires that electronic and information technology developed, procured, or used by US federal agencies meets the Section 508 technical standards. The current Section 508 standards (36 CFR Part 1194, updated 2018 to incorporate the WCAG 2.0 AA and EN 301 549 technical bar) apply to training content produced for or by federal agencies. US federal agencies that have implemented SAP S/4HANA, SAP SuccessFactors, or other SAP products and that produce SAP training video are covered entities — their training video must meet Section 508. The technical standard: WCAG 2.0 AA SC 1.2.2 (equivalent to WCAG 2.1 AA SC 1.2.2 for this purpose).

SAP partners and system integrators (Big Four implementation firms, Accenture Federal Services, Deloitte Federal, SAIC, Leidos) that produce SAP training video under federal contracts may have Section 508 compliance requirements flowed down from their government contracts. Project SOWs often include explicit Section 508 compliance requirements for training materials deliverables — Enable Now videos included.

European Accessibility Act (EAA) — EU obligations

The EAA (EU Directive 2019/882) requires that products and services placed on the EU market meet harmonised accessibility requirements by June 28, 2025, with enforcement through national legislation (transposition). SAP is a German company with a massive EU customer base, and SAP itself must meet EAA requirements in its product development — but the EAA also applies to EU-based SAP customers who produce and distribute training content to their EU employees or learners. Training video as a digital service provided to employees in the EU context falls within the EAA's scope for digital services. EU SAP customers producing Enable Now training content for EU employee distribution should treat WCAG 2.1 AA SC 1.2.2 as the operative caption standard.

EN 301 549 — EU public procurement

EN 301 549 is the EU harmonised technical standard for ICT product and service accessibility, referenced by the EAA and by EU public procurement requirements. EU public-sector SAP customers — national government agencies, regional governments, universities, public hospitals — that procure SAP products under EU procurement frameworks may face EN 301 549 compliance requirements for training content produced for the procured system. EN 301 549 clause 9 incorporates WCAG 2.1 AA (including SC 1.2.2) as the web content accessibility requirement. SAP Enable Now training video distributed via web-based delivery systems is in scope.

WCAG 2.1 AA — the universal technical baseline

WCAG 2.1 AA SC 1.2.2 (Captions, Prerecorded) requires that "captions are provided for all prerecorded audio content in synchronised media." SAP Enable Now MP4 exports are prerecorded synchronised media. The compliance path is: provide a synchronised caption file (SRT or VTT, depending on the delivery platform) that accurately conveys the audio. The "accurately conveys the audio" standard is the one that generic STT fails on SAP training video — the word "accurately" in WCAG 1.2.2 SC is not satisfied by a caption track that renders "SAP Fiori" as "feary," "FB01" as "FBO1," or "SAP Analytics Cloud" as "sack."

SAP's own VPAT/ACR for SAP Enable Now

SAP publishes Voluntary Product Accessibility Templates (VPATs) / Accessibility Conformance Reports (ACRs) for its products under the ITIC / ITI Accessibility Framework. SAP Enable Now's ACR documents SAP's conformance with Section 508 / WCAG 2.1 AA for the Enable Now product itself — the authoring interface, the Manager portal, the Companion overlay. SAP's product-level ACR does not address the accessibility of customer-produced training content: that responsibility falls entirely on the customer. The training videos that the customer's team authors in Enable Now Producer and distributes via SuccessFactors Learning or Manager are customer-owned content, and the WCAG compliance of that content is the customer's obligation, not SAP's.

SAP Enable Now versus other SAP training authoring and distribution tools

SAP training teams rarely use SAP Enable Now exclusively. The broader SAP training production environment typically combines Enable Now with general-purpose authoring tools and video platforms. Understanding how the captioning workflows interact helps training teams build a coherent approach across the full production environment.

SAP Enable Now versus Articulate Storyline

Articulate Storyline is the dominant general-purpose authoring tool in corporate L&D; SAP Enable Now is SAP-specific application simulation authoring. Many SAP implementation training projects use both: Enable Now for the simulation-mode walkthroughs of SAP transactions (where Enable Now's built-in SAP application recording is superior to Storyline's software-simulation mode for SAP GUI and Fiori), and Storyline for the conceptual, process, and compliance modules that surround the transaction simulations (where Storyline's branching, quizzing, and media-rich authoring environment is superior). The Storyline modules carry Enable Now MP4 video embedded in slide-level video objects. Captions for the Enable Now MP4 are imported into Storyline's slide-level video caption editor as VTT; the published SCORM package carries both sets of captions embedded. The SAP vocabulary failure mode applies equally to captions on Enable Now video embedded in Storyline — the Storyline auto-caption generator, like all generic ASR, does not know SAP vocabulary.

SAP Enable Now versus Camtasia

Many SAP trainers use TechSmith Camtasia for full-walkthrough screen-record editing — capturing long SAP workflow walkthroughs (a complete Procure-to-Pay cycle, a period-end close walkthrough) that span multiple transactions and benefit from Camtasia's timeline editing, callouts, and zoom-pan animations. Enable Now is better for step-by-step simulation authoring; Camtasia is better for polished narrative walkthroughs. The SAP vocabulary failure mode is identical in Camtasia recordings — "MIGO," "MIRO," "ME21N," "Company Code," "Controlling Area" all appear in narration and are all mis-transcribed by Camtasia's Speech-to-Text feature. The GlossCap SAP glossary applies upstream of both tools.

SAP Enable Now versus Lectora

Lectora is the authoring tool most associated with Section 508-focused eLearning production — federal government L&D teams and federal contractors often use Lectora for its compliance-first authoring approach. Federal agencies that have implemented SAP and need Section 508-compliant SAP training may use Lectora to package Enable Now video exports in a Section 508-compliant shell — Lectora's accessibility-first approach handles the Section 508 structural requirements (keyboard navigation, screen reader support, caption track configuration) that the training content must meet. The SAP vocabulary in the narration audio of the embedded Enable Now MP4 still requires glossary-biased captioning; Lectora's caption import accepts the resulting VTT.

SAP Enable Now versus Microsoft Teams / Stream for informal SAP training

Informal SAP training — ad hoc transaction walkthroughs recorded by super-users, post-go-live support recordings, SAP upgrade preview walkthroughs — is frequently captured in Microsoft Teams meetings and auto-hosted on Microsoft Stream on SharePoint. Stream provides AI-generated auto-captions, but Stream's auto-caption engine has no SAP vocabulary. The informal SAP training corpus that accumulates in Stream after a go-live is as large as the formal Enable Now training library, and it carries the same SAP vocabulary failure mode with the same compliance implications. The GlossCap SAP glossary and workflow applies to Stream-hosted SAP training video exactly as it applies to Enable Now exports — upload the Stream-hosted video to GlossCap, apply the SAP glossary, produce VTT, upload back to Stream as the override caption track.

The GlossCap SAP glossary approach — two layers

Because SAP vocabulary is standardised across all SAP customer implementations — every SAP customer uses the same T-codes for the same transactions, the same module abbreviations for the same functional areas, the same Fiori tile naming conventions — a shared SAP base vocabulary layer handles the majority of SAP-specific vocabulary failure modes across all customers. The customer-specific layer handles the implementation-specific vocabulary that varies by organisation.

SAP base vocabulary layer

The GlossCap SAP base glossary includes:

• All SAP product family names with their abbreviation-to-full-name mappings (S/4HANA, HANA, Fiori, ECC, BTP, SAC → SAP Analytics Cloud, SuccessFactors and its sub-modules, Ariba, Concur, Fieldglass, IBP, Datasphere, Signavio, MDG, EWM, TM, Build and its sub-products, SAP CX suite products)
• All SAP module two-letter codes and their expansions (FI, CO, SD, MM, PP, HCM, PM, EAM, QM, PS, BW/4HANA) with compound sub-module codes (CO-PA, FI-AA, FI-GL, FI-AP, FI-AR, SD-BIL, MM-IV, PP-MRP, HCM-PY, HCM-TM, PM-EQM)
• The most common T-codes across FI, CO, SD, MM, PP, HCM, and cross-application use (FB01, FB60, VA01–VA03, VF01–VF02, VK11, ME21N, ME22N, MIGO, MIRO, FBL3N, KSB1, CO01, MM60, MD04, BP, MM01, MM02, and approximately 200 additional T-codes covering common transactions across all modules)
• All SAP Organisational Unit names (Company Code, Plant, Sales Organisation, Distribution Channel, Division, Purchasing Organisation, Profit Center, Cost Center, Business Area, Controlling Area, Credit Control Area, Storage Location, Shipping Point, Loading Point, Personnel Area, Personnel Subarea, Employee Group, Employee Subgroup, Payroll Area)
• All SAP Master Data object type names (Material Master, Business Partner, GL Account, Cost Element, Cost Center, Profit Center, Asset Master, Vendor Master, Customer Master, Work Center, Functional Location, Equipment)
• SAP Enable Now product vocabulary (Producer, Manager, Companion, Instant Producer, Learning Map, Demo mode, Practice mode, Test mode, Concurrent mode, Bubble text, Offline Player, SAP Companion for Desktop)
• SAP SuccessFactors Learning vocabulary (Item, Curricula, Program, Assignment, Completion Status values, LMS Admin role names, and SuccessFactors-specific navigation terminology)
• Common SAP process names (Order-to-Cash, Procure-to-Pay, Record-to-Report, Hire-to-Retire, Plan-to-Produce, Request-to-Service) that appear in process-overview training narration

Customer-specific overlay

The customer-specific layer is built from the implementation project's configuration documentation and is typically populated at project start:

• Organisational Structure codes and names. If the customer's Company Code is "US01 — United States Operating Company," narrators will say "Company Code US01" throughout FI training — the "US01" code must be in the overlay.
• Customer's custom T-codes (Z-transactions and Y-transactions). Customer-specific SAP developments often add custom T-codes with Z/Y prefixes (e.g. ZMME1 for a custom purchase order report, ZFIB1 for a custom FI report). These are entirely unknown to any generic STT model and require explicit glossary entries.
• SAP system landscape names. Development system (DEV), Quality Assurance system (QAS), Production system (PRD), Training / Sandbox system (TRN, SBX) — the customer's system landscape names appear in training narration ("log in to the QAS system and confirm the configuration") and should be consistently transcribed.
• SAP project and programme names. SAP implementation projects are named — "Project Phoenix," "Transform," "Horizon" — and these names appear in training narration and in training video titles.
• Customer's SAP SuccessFactors configuration vocabulary. Custom learning item names, custom curricula names, custom role names, custom approval workflow names — all the customer-specific SuccessFactors Learning configuration terms that appear in admin training.
• Implementation partner vocabulary. SAP system integrators (Deloitte, Accenture, PwC, IBM, Capgemini, Infosys, Wipro, NTT DATA) each have proprietary delivery methodology vocabulary that appears in training content produced during the implementation phase. "Fit-to-Standard workshops," "blueprint documentation," "go-live readiness assessment" — these implementation methodology terms should be in the overlay.

SAP SuccessFactors Learning: the caption distribution architecture

SAP SuccessFactors Learning is the dominant LMS for distributing SAP training at large SAP customers. Understanding how captions are attached and delivered through SuccessFactors Learning is essential for SAP training teams building a captioning workflow.

Video Items in SuccessFactors Learning

SAP SuccessFactors Learning can host video directly as a Learning Item — uploading an MP4 to the SuccessFactors Learning content repository and attaching a caption file (VTT or SRT, depending on the SuccessFactors Learning version and configuration) to the video Item. The SuccessFactors Learning video player renders the CC toggle when a caption file is present. For Enable Now MP4 exports distributed via SuccessFactors Learning's native video hosting, the VTT produced in the GlossCap captioning workflow is uploaded to the Item's media resource in SuccessFactors Learning administration.

SCORM-packaged content in SuccessFactors Learning

Many SAP training libraries distribute content through SuccessFactors Learning as SCORM packages (SCORM 1.2 or SCORM 2004) or xAPI packages. The SCORM package model embeds the caption file inside the package zip at authoring time, so the SuccessFactors Learning LMS does not need to manage the caption file separately — the package carries its own caption track and the player embedded in the SCORM package renders it. For Enable Now content packaged via Articulate Storyline or directly via Enable Now's own SCORM export, the caption VTT must be embedded in the SCORM package before publication to SuccessFactors Learning.

SuccessFactors Learning's Completion Status and caption evidence

SuccessFactors Learning tracks completion at the Item level. For required SAP training assigned via a Curriculum or Program in SuccessFactors Learning, completion records show whether a learner has completed the training (status: Completed) or not (Not Started, In Progress). For hearing-impaired learners who complete SAP training, the completion record in SuccessFactors Learning is the legal evidence of training completion — and it implicitly evidences that the learner had access to accessible training. If the captioned video in SuccessFactors Learning contains inaccurate captions (e.g. generic STT output that mangles SAP T-codes and module names throughout), the completion record does not accurately represent whether the learner received "appropriate" training, because the captions did not accurately convey the instructional content. Accurate captions — not merely present captions — are what the ADA Title I and WCAG SC 1.2.2 "accurately conveys the audio" standards require.

FAQ — SAP Enable Now captions

Further reading

• Articulate Storyline captions: the authoring tool most commonly combined with SAP Enable Now in implementation training libraries
• Camtasia captions: screen-record walkthroughs of SAP transactions and Fiori apps
• Lectora captions: Section 508-focused SAP training packaging for federal implementations
• Microsoft Stream captions: informal SAP training walkthroughs recorded in Teams
• Section 508 captions: the technical standard for US federal SAP training
• EAA captions requirements: EU obligations for SAP customer training content
• EN 301 549 captions: EU public procurement and SAP training accessibility
• WCAG 2.1 AA captions: what SC 1.2.2 "accurately convey the audio" requires
• Workday Learning captions: the SAP SuccessFactors competitor LMS
• Cornerstone OnDemand captions: enterprise LMS alternative for SAP training distribution
• Proper noun failure modes in captioning training video: why enterprise software vocabulary breaks generic STT