Accessibility at Learnient

Systematic testing, not good intentions

We audit Learnient using automated accessibility testing across every major page and user journey — including admin interfaces, learner dashboards, form modals, and reporting screens. Testing runs across both light and dark modes, and covers the full WCAG 2.1 AA ruleset including colour contrast, keyboard navigation, ARIA attributes, and form labelling.

Our testing uses axe-core — the same accessibility engine used by professional auditors and embedded in browser tools like the axe DevTools extension. We test programmatically rather than by hand so results are consistent, repeatable, and not dependent on who remembered to check what before a release.

Colour contrast

Every text element in the platform meets WCAG AA contrast ratios — 4.5:1 for normal text and 3:1 for large text. This applies in both light and dark mode. We test this automatically and fix failures before they ship.

We also support custom brand colours — and when a customer sets their brand colour, we automatically calculate an accessible variant for dark mode so your brand colours never create accessibility failures in the interface.

Built-in accessibility checker for colour contrast for course authors

When administrators build courses in Learnient, they're not left to figure out accessibility on their own. The course builder includes a real-time accessibility checker that analyses content as it's created — covering colour contrast ratios, text readability, and element labelling.

The checker runs across both light and dark mode, so authors can see how their content performs for learners using either setting. Issues are flagged inline with clear guidance on how to fix them, rather than surfaced after the fact.

This means accessibility isn't just a platform concern — it's built into the content creation workflow.

Screen reader support

All interactive elements have accessible labels. Icon-only buttons, form inputs, progress bars, and toggle switches all have descriptive text accessible to screen readers. We use semantic HTML and ARIA attributes correctly throughout.

Keyboard navigation

Every feature in Learnient is accessible without a mouse. Navigation, forms, modals, dropdowns, and course player controls all work via keyboard. Focus states are visible throughout.

Form accessibility

All form inputs have associated labels. Required fields are marked both visually and programmatically. Error messages are associated with their inputs so screen readers announce them correctly. We do not rely on placeholder text as a label substitute.

Dark mode

Learnient has a full dark mode implementation. Every UI element — including navigation, cards, tables, forms, and modals — has been tested for contrast compliance in dark mode. We treat dark mode as a first-class accessibility feature, not an afterthought.

User-generated content

Learnient is a platform for creating and delivering training. That means course content — headings, body text, callout boxes, images — is authored by your administrators, not by us.

We provide accessible course building tools and sensible defaults. When an administrator chooses a custom colour for a callout box, for example, we automatically suggest accessible text colour combinations. However, we cannot programmatically prevent all possible content-level contrast failures in user-created material, in the same way a word processor cannot guarantee an accessible document.

Platform interface elements are fully within our control and meet WCAG 2.1 AA. Content created within the platform is the responsibility of the content author, supported by our accessible authoring tools.

To support accessible content creation, the course builder includes a real-time accessibility checker covering contrast, labelling, and dark mode compatibility. Authors are guided towards accessible choices at the point of creation rather than discovering issues after publishing.

Customer-configured branding

The platform supports custom branding including banner images, button colours, and brand colour palettes. Contrast compliance of customer-configured banner button colours depends on the colours chosen by the customer. We surface this in our documentation and provide guidance on accessible colour selection.

Third-party components

Some third-party UI library components have known minor accessibility quirks that are outside our direct control, pending fixes from upstream maintainers. Where these exist, we document them and work around them where possible.