Learning that everyone on the team can use

What we aim for

Our target for custom learning is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That's the standard Australian universities, government agencies and most large employers ask for, and it's the right floor for anything people are required or expected to complete.

We would rather tell you where something falls short than claim a badge. When a build can't meet a criterion, we say which one, why, and what the accessible alternative is, in writing, before it goes live.

Custom learning modules

Accessibility is scoped at the start of a project, not audited at the end. In a custom module we design for:

• Everything working with a keyboard alone, with a visible focus indicator
• Meaningful structure for screen readers: real headings, labelled controls, announced changes
• Captions and a transcript for any audio or video, and no information carried by sound alone
• Text and controls that meet contrast requirements, and nothing that relies on colour alone
• Respecting the reduced motion setting, and no content that flashes
• No time limits a learner can't turn off or extend

We test with automated checks (axe), keyboard-only walkthroughs, and screen reader spot checks in NVDA and VoiceOver. If your organisation has its own accessibility testing, we build time into the project to act on what it finds.

The Conversation Builder and practice conversations

• The builder and the conversation can be used with a keyboard alone, and the conversation is announced to screen readers as it happens.
• Typing is always available. Voice is an option on top, never a requirement: the character's voice can be muted, and speaking your side is a choice.
• Everything the character says also appears as text, including in the hands-free Talk it out mode, where the transcript is one tap away.
• There is no timer. A learner can take as long as they need over each reply.
• The debrief is text, with scores given as words and numbers as well as bars.

A roleplay can be a stressful activity for some people regardless of how the interface is built. We recommend practice conversations are offered as an option with an alternative, rather than as the only way to complete a requirement.

Presentation pieces in the showcase

Some showcase pieces are deliberately visual: The UNIVERSEity and the Universe Builder's output are 3D scenes, and Long Take makes camera films. These are presentation and exploration pieces. They are not accessible to someone who can't see the screen, and we don't pretend otherwise.

Where they are used in learning, they sit alongside an equivalent: the org structure as a searchable list, the traced process as numbered steps, the film as a transcript. The explainer films in the showcase carry captions and a full transcript.

This website

This site is built as plain HTML with real headings, a skip link, labelled forms and sufficient contrast, and works at phone widths. Embedded builds and films open in a full view that traps focus and closes with Escape, and every animation respects the reduced-motion setting. If something on it doesn't work for you, please tell us.

Tell us what isn't working

Email jaredfras1@gmail.com with the page or piece, what you were trying to do, and the browser or assistive technology you use. We'll reply within five business days, and if we can't fix it quickly we'll give you the content another way.