Why this standard exists

The EU AI Act already expects your staff to be AI literate.

Article 4 has applied since February 2025. Everything further down this page is how we build to that duty, and what a module can honestly evidence on your behalf.

Article 4 asks organisations that provide or deploy AI systems to ensure a sufficient level of AI literacy among their staff and anyone operating those systems on their behalf, judged against people's roles and the context they work in. It also reaches organisations outside the EU where the output of the system is used inside it, so a UK team can be in scope.

We write modules to serve that duty and record what each learner completed. Training is one part of meeting the obligation rather than the whole of it, so we will tell you plainly what a module evidences and what you still need to record yourself.

What a module gives you

A dated completion record for every learner, with scores
Content pitched at a role and a context, rather than one generic course
A route through the material that works for everyone on your staff list
Revisions when the tools or the rules move

What stays with you

Deciding which roles need which depth of literacy
Your own AI policy, and instruction on your own systems
Keeping the record where your auditors will look for it
The wider duties Article 4 sits alongside

Request a trial Discuss your requirements

Standard one

Accessible by construction

WCAG 2.2 AA is the floor every module is built to, not a badge added at the end. The checks run on every build, so a module cannot quietly drift below the standard between one version and the next.

Captions on every narrated slide, and a transcript for the whole module
Audio description written by a person rather than generated
A full keyboard route through every screen, activity and control
Colour, contrast, focus states and reading order measured on each build
Plain English scored on each build and graded at both quality gates, so a long sentence or an unexplained term is flagged and fixed before a learner sees it

The European Accessibility Act

The Act has applied since 28 June 2025. It sets accessibility requirements for a defined list of products and services sold to consumers in the EU, and for the digital parts of that the standard everyone works to is EN 301 549, which currently points at WCAG 2.1 AA.

We build to WCAG 2.2 AA, the later version. It carries every 2.1 AA requirement apart from one the W3C has since retired as obsolete, and adds six more on top, so a module built to our floor already sits above the level the Act is measured against today.

What we will not do is tell you the Act reaches your organisation. That depends on what you sell and to whom, and a training module is not itself one of the listed services. If it does reach you, the accessibility work is the same work either way, and you will have the record to hand on.

Standard two

Self-contained zips, no tracking calls

Each module is a single SCORM 1.2 package. Everything it needs is inside the file: video, audio, captions, fonts and code. Nothing is fetched from somewhere else while a learner is working.

SCORM 1.2, accepted by nearly every corporate LMS
No third-party telemetry and no calls out to an external service
Completion and scores reported through SCORM, into your own audit trail
The same file runs on your LMS or on ours, unchanged

Why it matters. A package that phones home is a package your security review has to argue about, and one that breaks the day a supplier changes a URL. What your learners see does not depend on our servers being up.

Standard three

Modules are maintained, not shipped and forgotten

Content moves when the tools and the rules move. A module is a version rather than a one-off delivery, and you can see which version your people took.

Every module carries a lifecycle stage, from early production through to established
A recently updated flag when the content changes, so you can see what has moved since your last rollout
Learner progress is held separately from the content, so an update does not wipe a record
Revisions as the regulatory picture and the tools change

What we will tell you. Not every change is worth putting in front of your people again. When we update a module we say whether it is a correction, a refresh or a genuine change of substance, so you can decide whether a re-take is warranted.