Accessibility statement

Learning should be open to everyone who needs it. This statement explains how we make the Nialtus platform accessible, what we have tested, where we still fall short, and how to tell us about a problem.

Our standard

We design and test Nialtus to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We believe the platform is partially conformant: most of it meets the standard, and the known exceptions are listed below. We have not yet had an independent third-party audit.

What this statement covers

The Nialtus platform itself: the learner experience (catalog, lessons, assessments, certificates, transcripts), manager and administrator screens, the course builder and the lesson blocks it produces, emails the platform sends, and this website.

It does not cover content that an organization uploads or links to, such as SCORM, xAPI or cmi5 packages, PDFs, videos, documents, external websites and third-party embeds. The accessibility of that content depends on how it was made, and it is the responsibility of the organization that publishes it. We give authors tools to help, described below.

What we do

• Keyboard access: every screen, menu, dialog and interactive lesson block can be used with a keyboard alone, with visible focus.
• Screen readers: form fields, buttons and controls have accessible names, and dialogs announce themselves and keep focus inside until closed.
• Color and contrast: text colors are checked against their backgrounds every time a page is shown. If a workspace chooses brand colors that would be hard to read, Nialtus adjusts the text shade just enough to meet the standard, without changing the brand color itself.
• Display choices: every learner can choose light, dark or high-contrast display. High contrast ignores workspace colors entirely.
• Languages and direction: the interface works in 20+ languages, including right-to-left Arabic, and each course can declare its own content language so text reads in the right direction.
• Phones and tablets: pages reflow to small screens without horizontal scrolling, with touch targets large enough to tap.
• Ongoing checks: an automated accessibility test runs every night across learner, manager, author and admin pages, in English and Arabic, on desktop and phone sizes, and flags any new problem before customers find it.

Tools we give course authors

• An accessibility check in the course builder that flags missing image descriptions, videos without captions, audio without transcripts, skipped headings, unclear link text and colors that fail contrast.
• Image descriptions, with an option to mark an image as decorative, and AI-suggested descriptions the author reviews before saving.
• Video captions in several languages, uploaded as caption files or drafted by AI for the author to review.
• Transcripts for audio, and an “Accessible version” option for third-party content such as SCORM packages and PDFs.

Known limitations

• Content uploaded by organizations (SCORM, xAPI, cmi5, PDFs, videos) may not be accessible. Authors can attach an accessible alternative.
• YouTube videos use YouTube’s own player and captions.
• PDF downloads such as certificates, transcripts and reports are not yet fully tagged for screen readers. The same information is available on screen.
• Manual testing with every screen reader and browser combination is still in progress. We have tested primarily with automated tools and keyboard-only use.

Feedback and contact

If something in Nialtus is hard to use, or you need information in a different format, email [email protected] with the page and what happened. We aim to reply within five working days. If you are a learner, you can also contact the administrator of your organization’s workspace.

About this statement

Nialtus is provided by Learning Everest Private Limited. This statement was last reviewed on 24 October 2026 and is updated when the platform changes.