For whoever has to defend this choice
At some point IT, legal, or procurement will ask what this thing actually is. This page is the answer: which standards OELTKit packages target, what the accessibility commitment means concretely, and exactly where learner data goes (spoiler: to your LMS, and nowhere else).
LMS interoperability
Every OELTKit course can be packaged for four targets from the same source. You pick the target; the content doesn't change.
- SCORM 1.2
- The lowest common denominator — and still the safest bet for older corporate LMSes. If you don't know what your LMS supports, it supports this.
- SCORM 2004
- Richer status reporting than 1.2 (separate completion and success). Status: export available; completion reporting not yet verified — 1.2 and cmi5 are the verified targets. The runtime writes the right values and the LMS accepts them, but completion/success don't yet reliably roll up to the registration on a real LMS (OQ-004). Prefer SCORM 1.2 or cmi5 when tracking must be guaranteed.
- cmi5 / xAPI
- The modern standard: granular statements to an LRS, courses that can live outside the LMS. Choose it if your platform is recent or you run an LRS.
- Standalone web
- No LMS at all — the same course runs on any static host. Tracking calls no-op safely or log locally. Good for previews, portfolios, and public courses.
Verified on
This list only ever contains platforms where the full conformance test suite has actually been run — that's a launch rule, not a disclaimer.
- No entries yet. SCORM Cloud is the first verification target; real LMSes follow as they're tested. Until a platform appears here, we make no claim about it.
Accessibility
OELTKit components are built to WCAG 2.2 AA — keyboard operability, visible focus, screen-reader tested behavior, and reduced-motion support are construction requirements, not an audit afterthought. The validator checks the content layer (the part your AI writes) so generated courses don't undo that work.
Per-component conformance
Every launch component (see the full set in the component gallery) ships with Playwright + axe-core tests that run in CI, and is keyboard-operable by construction (see each component's keyboard map in the component reference). Components are in beta; a manual screen-reader pass (NVDA + VoiceOver) is the gate to stable.
Pending: the auto-generated per-component conformance table (automated results plus manual-AT status, straight from oeltkit/oeltkit) lands here with the v0.1 release — it is not hand-maintained, by design.
Regulatory mapping
WCAG 2.2 AA conformance is the basis for Section 508 (US) and EN 301 549 (EU) compliance claims. A conformance statement template you can adapt for procurement paperwork ships alongside the conformance table.
TODO: conformance statement template download pending the first published test run.
Data
- What's tracked: what you declare in the course manifest — progress, scores, completion, and (on cmi5/xAPI) the statements your components emit. Nothing else.
- Where it goes: to your LMS or LRS, over the standard API for the target you packaged. That's the whole list.
- No phone-home: OELTKit courses make no requests to OELTKit, BCL Training, or any third party. No analytics, no beacons, no CDN dependencies at runtime.