Accessibility statement

This accessibility statement covers all resources provided through nimbl, Anspear’s system for mobile learning on smartphones, tablets and the web. These resources can be accessed through the nimbl and Anspear apps for Android and Apple devices, other apps branded to our partner organisations, and their accompanying web portals accessed via web browsers.

At Anspear, we recognise the importance of ensuring our resources are accessible to as many people as possible. Our learning materials are primarily text-based and may present challenges for users with visual impairments, dyslexia, or other accessibility needs. We therefore make every reasonable effort to reduce barriers and support inclusive access wherever possible.

AbilityNet provides guidance on making your device easier to use if you have a disability.

How accessible is the App?

Features that help to make nimbl more accessible include:

  • Compatibility with text-to-speech and screen reader technologies (see below)
  • Keyboard navigation, Aria labels and screen reader compatibility for courses accessed via the web
  • Options to increase text size:
    • via device settings on Android
    • by rotating iPhones into landscape mode
    • by zooming in on the web (text does not flow off screen)
  • Dual text and audio activities in many publications
  • Consideration of colour contrast and visual clarity during content design
Known accessibility limitations

We are aware that some parts of the app and web service are not fully accessible:

  • Keyboard navigation within the course library on the web could be improved
  • Some form inputs and buttons in the course library are not optimally labelled for screen readers
  • On Android and iOS, there is a limit to how much text size can be increased
  • Some images may be missing alternative text
  • Some video content may not include a text alternative
  • A very small number of interactions require dragging movements and currently do not provide a non-drag alternative
Text-to-speech and screen reader support

Our primary approach to accessibility is ensuring compatibility with platform-level assistive technologies:

  • Web browsers: Major browsers including Safari, Firefox and Chrome provide text-to-speech features or extensions. Our resources are compatible with these tools.
  • Android: The TalkBack screen reader (Android 5 or later) is compatible with our resources.
  • Apple devices: The built-in VoiceOver screen reader on iPhones and iPads is compatible with our resources.
Feedback and contact information

If you need any learning or reading resources in an alternative format, such as PDF or Word document, please contact:

We will consider your request and aim to respond within 2 working days.

Reporting accessibility problems

We are always looking to improve accessibility. If you encounter any issues not listed on this page or believe we are not meeting accessibility requirements, please contact us using the details above.

Technical information about accessibility

Compliance status

This app and its associated web services are partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.2 Level AA, due to the non-compliances listed below.

Non-accessible content
Images

Some images do not have appropriate text alternatives, which means users of screen readers may not be able to access the information.
This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).

We ensure that newly published content meets accessibility standards for image use.

Video

While many externally hosted videos include captions or transcripts, some videos currently do not.
We aim to provide transcripts or captions for all new video content.

Navigation and interaction
  • Keyboard navigation within the web-based course library can be difficult in some areas
  • Focus visibility may not always be sufficiently clear
  • The purpose of some links in the course library may not be determinable from link text alone

These issues fail WCAG 2.2 success criteria 2.1.1 (Keyboard), 2.4.7 (Focus Visible) and 2.4.4 (Link Purpose).

In addition, a small number of interactions rely on dragging movements without a non-drag alternative, which fails WCAG 2.2 success criterion 2.5.7 (Dragging Movements).

We plan to address these issues by improving keyboard focus handling, adding ARIA landmarks and labels, and reviewing interaction patterns to reduce reliance on drag-only controls.

Compatibility with assistive technologies

In some cases, the name and role of user interface components may not be programmatically determinable.
This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).

We plan to improve ARIA labelling to ensure better compatibility with screen readers.

Disproportionate burden

On Android and iOS devices, it is not currently possible to increase text size to 200%. However, partial text scaling is available through system settings or by rotating the device to landscape. The achievable text size depends on screen width.

Preparation of this accessibility statement

This statement was prepared on 22 March 2022.
It was last reviewed and updated on 12 December 2025.