What works, and what has not been audited.

Several training academies have an internal accessibility requirement, and a supplier who answers it with a logo rather than a description is not answering it. This page is written the same way as the trust centre: what is in place, and what is not.

Last updated 31 Aug 2026 · questions: support@ohmix.eu

The target

The intent is WCAG 2.1 level AA. It is the level most European academies reference, and it is the level the interface is built and checked against — but "built against" is not "certified", and the difference matters when you are filling in a supplier form.

What is in place

• Colour contrast. Interface text is checked against AA (4.5:1 for body text, 3:1 for large text) in both the light and dark themes. A previous pass found and fixed five light-theme roles that failed, the worst being white on the accent colour used by every primary button. The deck player's own chrome was corrected in the same way: it sits on a deliberately dark frame, so its controls carry pinned light-on-dark colours rather than inheriting the application theme.
• Keyboard. The interface is operable without a pointer, every page begins with a skip link, and focus is visible — :focus-visible outlines rather than the removed outline that makes a keyboard user guess where they are.
• Reduced motion. prefers-reduced-motion is respected: slide transitions, the animated system diagram and the guided walkthrough all stop animating. The diagram's guided playback is opt-in in the first place, and a reduced-motion viewer keeps the static chart.
• Status messages. Progress and results are announced through live regions rather than only by a visual change, so a job finishing is not a silent event.
• Text alternatives. Manual figures carry a description naming the page they come from; decorative marks are hidden from assistive technology.
• A transcript for every voiced lesson. The narration is written text first and spoken second, so the transcript is the source rather than a derivative. It is readable in the player, and it travels in the exported handout and inside the SCORM package, which means a technician who cannot use the audio still receives every word.
• Themes. Light and dark are both first-class, and the choice follows the system setting unless it is overridden.

What is not in place

• No independent audit and no VPAT. Nobody outside the project has assessed this.
• No screen-reader test matrix. The interface is built to be operable with one, but it has not been systematically exercised against JAWS, NVDA and VoiceOver, and we will not imply that it has.
• The 3D vehicle view is visual. A component is reachable and named in text elsewhere in the lesson, but the spatial view itself has no non-visual equivalent.
• Exported packages inherit their player. A SCORM package is keyboard operable and carries its transcript, but once it is inside your LMS, the surrounding frame is your LMS's, and its behaviour is not ours to state.
• Uploaded documentation is as accessible as you supply it. A scanned manual page reproduced in a lesson is an image of a page. The lesson's own text carries the claim, which is why the citation is text and not only a picture.

If something blocks you

Write to support@ohmix.eu or use the contact form, and describe what you were doing and what happened. An accessibility fault is treated as a fault, not as a feature request. If it stops a technician working, it is urgent.