Accessibility Statement

Our commitment

Bykov-Brett Enterprises Ltd, trading as the AI Literacy Lab, is committed to making this site and every module on it usable by everyone, including people who use a screen reader, navigate by keyboard, need captions, or need the text bigger.

We treat this as part of building the thing rather than a pass someone does afterwards. A module that fails the accessibility checks does not ship.

Conformance status

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and we hold that as a hard floor for both the website and the learning modules. Every module ships with a conformance statement covering its accessibility and its SCORM behaviour, which you can ask for before you buy.

We describe ourselves as broadly conformant rather than perfectly conformant, because the honest position includes the limitations listed further down.

Inside a module

• Narration on every slide, with captions written from the same source as the audio, so the words on screen and the words spoken cannot drift apart.
• Audio description for visual content, spoken in a deliberately different voice from the narration, so you always know whether you are being described to or taught. Turning it on replaces the narration rather than talking over it, and its captions appear too.
• Full keyboard operation. Every activity, quiz and simulation can be completed without a mouse, with a visible focus indicator on whatever you have landed on.
• Screen reader support. Controls carry accessible names, headings run in order, and interactive elements announce their state.
• Target size. Interactive elements meet the 24 by 24 pixel minimum in WCAG 2.2.
• Contrast meets AA for text and interactive elements, and the layout keeps the caption zone clear of the navigation controls.
• Plain language. We write for a general reader and measure every learner-facing sentence for reading age, sentence length and unexplained jargon.
• Nothing loads from outside. A package is self-contained, so it works behind a corporate firewall and makes no tracking calls.

On the website

• A skip link to the main content on every page
• Semantic headings, landmark regions and descriptive link text
• Alternative text on images that carry meaning, and empty alt on the decorative ones
• Visible focus outlines for keyboard users
• Menus operable with the keyboard, including arrow keys, Enter and Escape
• Layouts that work on a phone, a tablet and a desktop, and at 200 per cent zoom
• Transcripts for podcast episodes

The accessibility toolbar

Every page carries an accessibility toolbar. It offers:

• Visual adjustments: dark mode, high and low contrast, greyscale
• Reading aids: text size, line height, OpenDyslexic font, bionic reading, a reading guide, RSVP reading
• Audio: text to speech, read the page aloud, voice navigation
• Navigation aids: page structure outline, stop animations, hide images, big cursor, highlight links
• Profiles pre-configured for ADHD, low vision, dyslexia and screen reader users
• Translation into other languages

Your choices are stored on your device so the site remembers them next time. They are not sent to us.

How this is checked

Every module build runs five automated test suites, and a failure blocks the build. They cover colour contrast at 200 per cent zoom, keyboard operation, captions on every narrated slide, and the packaging rules that keep a module self-contained.

A second set of checks runs as a pre-flight rather than a gate: pointer target sizes, accessible names, heading order and alternative text. We run it before a module is handed over and record the result, but we are honest that today it is a manual step rather than an automatic block. Reading level is measured on every learner-facing sentence and reported as a warning, because legal and regulatory wording sometimes has to carry length that the formula marks down.

Beyond the machines, every module gets a manual keyboard pass and a manual screen reader pass before handover, recorded rather than assumed. The build prints what a machine cannot check, so nobody can quietly skip it.

Known limitations

These are the things we know are not right yet.

• Voice navigation in the accessibility toolbar needs a Chromium-based browser, such as Chrome or Edge. It does nothing in Safari or Firefox.
• Embedded third-party content carries its own accessibility. The Calendly booking panel on our contact page and embedded YouTube videos are outside our control. If either blocks you, email us and we will book you in or send you the content another way.
• Older PDF downloads. Some guides and reports published before our current review may not be fully tagged for screen readers. Ask us for a specific one and we will produce an accessible version.
• Reading level in legal and regulatory material. We measure every sentence, and where a module covers law the wording sometimes has to carry length and precision that the reading-age formula marks down. We take accuracy over the score, and we explain terms at first use instead.
• Machine narration. Narration is synthesised rather than recorded in a studio. It is checked back against the script automatically, and corrected when it mispronounces something, but occasional stress on the wrong word is possible. Captions are always exact.

If you run our modules on your own LMS

A licensed module is a self-contained SCORM 1.2 package, and its accessibility travels with it. What we cannot control is the player your learning management system wraps around it. Some players open the module in a small popup, some strip keyboard shortcuts, and some do not pass through captions properly.

Our modules scale down to fit smaller player windows rather than clipping. If your system does something we have not seen, tell us and we will look at it with you. A trial exists so your own team can test a module with a keyboard, a screen reader and your actual LMS before any money moves.

Tell us when it does not work

If any part of this site or any module gets in your way, we want to hear about it. Tell us what you were trying to do, what happened, and what you were using, and we will come back to you within 5 working days.

This statement was prepared on 19 August 2026 and is reviewed when the site or the build standard changes.