Accessibility
Learning should be usable by everyone
How RLC SCO Nexus is designed, tested, and improved where it still falls short.
Last updated 13 September 2026
In short
- We design and test Nexus against WCAG 2.2 Level AA. We don't claim full compliance, and we tell you honestly where we fall short.
- Routes are checked with keyboard navigation, screen-reader semantics and automated contrast/scanning tools, in both the dark and light themes.
- The whole platform works down to 360px wide and up to 400% zoom, and respects your reduced-motion preference.
- Simulations are desktop-first with a reduced mobile tier, and certificate PDFs aren't yet tagged for screen readers. Ask us for an accessible alternative.
- Tell us about any barrier you hit, and we'll fix it or provide a reasonable alternative.
On this page
Our commitment
RLC SCO Nexusis designed and tested to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We don't claim to be fully compliant, and no independent audit has been carried out yet, but every route we ship is checked against this standard before and after release, not treated as an afterthought.
What we do
- Every control is reachable and operable by keyboard alone, with a visible focus indicator.
- Pages use semantic headings and landmarks, so assistive technology can navigate them directly.
- Form fields are labelled, and errors are announced alongside the field they relate to.
- Colour contrast is checked with automated scanning (axe) in both the dark and light themes, not just eyeballed.
- The platform reflows and remains usable down to 360px wide and up to 400% browser zoom.
- Animated elements respect your operating system's reduced-motion preference. With it enabled, transitions and animations shorten to near-instant throughout.
- Interactive components use correct screen-reader semantics (roles, states and live regions), and meaningful images carry alt text.
- The interface is responsive across phone, tablet and desktop widths.
- The dark/light theme control is itself a labelled, keyboard-operable toggle.
- Lesson content uses a consistent, navigable structure rather than a single unstructured block.
- Simulations support keyboard-driven interaction, not mouse-only operation.
Known limitations
- Simulations are built desktop-first. A reduced feature set is available on phone-width screens rather than the full console experience.
- Certificate PDFs aren't yet tagged for screen readers. If you need an accessible alternative to a certificate, ask us through Contact.
- No independent accessibility audit has been carried out yet. Our own testing is described above.
- We aim for generously sized tap targets throughout, but haven't yet run a dedicated automated check against WCAG 2.2's 24px minimum target size.
Tell us about a barrier
If something doesn't work well with your assistive technology, or you hit a barrier using Nexus, tell us through Contact. We'll fix it where we can, and where we can't fix it immediately, we'll provide a reasonable alternative or adjustment, in the same spirit as the Equality Act 2010's duty on service providers, whether or not a particular part of that Act applies to an independent platform like this one.
The standard we use
We test against WCAG 2.2 at Level AA, the internationally recognised accessibility standard. The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 apply to public-sector bodies and don't apply to an independent platform like Nexus. We use WCAG 2.2 AA as our own benchmark regardless, because it's the right standard to hold ourselves to.