Accessibility statement for the Team Jump mobile application

Last updated: February 2026

This accessibility statement applies to the Team Jump mobile application for iOS and Android, operated by Green Rewards Ltd trading as Team Jump.

Overview

The Team Jump mobile app is designed to support engagement and sustainability programmes. We want as many people as possible to be able to use the app. For example, this means you should be able to:

  • use the app with built-in accessibility features such as VoiceOver (iOS) and TalkBack (Android)
  • adjust text size using your device’s system settings
  • use the app in different orientations where supported by your device
  • navigate most areas of the app using assistive technologies

We aim to make text as clear and simple as possible and consider accessibility as part of ongoing development.

How accessible this mobile app is

The Team Jump mobile app is partially accessible.

We know that some parts of the app are not fully accessible and may present challenges for users of assistive technologies, particularly in areas involving complex interactive or visual elements.

Feedback and contact information

If you find any accessibility problems not listed on this page, or think we’re not meeting accessibility requirements, please contact us:

Email: [email protected]

Responsible team: Product, Team Jump

If you need information available in the app in a different format (such as large print, accessible PDF, easy read, or audio), please contact us using the details above.

We’ll consider your request and aim to get back to you within 10 working days.

Technical information about this mobile app’s accessibility

Green Rewards Ltd trading as Team Jump is committed to making the Team Jump mobile application accessible and aligns with the Web Content Accessibility Guidelines (WCAG) version 2.2 AA.

Compliance status

The Team Jump mobile application has been assessed against the WCAG 2.2 AA standard.

This mobile application is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility guidelines

Some interactive components, such as leaderboards, progress indicators, and data visualisations, may not be fully compatible with screen readers. This may fail WCAG 2.2 success criteria 1.3.1 (Info and Relationships) and 4.1.2 (Name, Role, Value).

Planned action: These components are reviewed as part of ongoing product improvements and major app updates.

Some touch targets may not consistently meet the minimum size requirements introduced in WCAG 2.2. This may fail WCAG 2.2 success criterion 2.5.8 (Target Size).

Planned action: Touch target sizing is being addressed incrementally during UI updates.

Focus order and visual focus indicators may not always be clear when navigating the app using external keyboards or assistive technologies. This may fail WCAG 2.2 success criterion 2.4.3 (Focus Order) and 2.4.7 (Focus Visible).

Planned action: Improvements will be considered as part of future accessibility-focused refinements.

Disproportionate burden

Some historical design decisions and client-specific customisations within the mobile app would require significant redevelopment to fully meet all WCAG 2.2 AA success criteria. At present, addressing all such instances immediately would place a disproportionate burden on the organisation.

We will reassess this position when undertaking major app redesigns or platform upgrades.

Content that’s not within the scope of accessibility guidelines

Third-party integrations

The mobile app integrates with third-party services (for example, fitness trackers or external content providers). These services are outside of our direct control and may not fully meet accessibility standards.

What we’re doing to improve accessibility

We are actively working to improve accessibility across the Team Jump mobile app by:

  • considering accessibility requirements during feature design and development
  • using platform accessibility APIs for iOS and Android
  • reviewing accessibility issues as part of our internal bug reporting and prioritisation process
  • testing core user journeys using built-in mobile accessibility tools

Preparation of this accessibility statement

This statement was prepared on 6 February 2026. It was last reviewed on 6 February 2026.

The Team Jump mobile app was last tested for accessibility on 15 January 2026 against the WCAG 2.2 AA standard.

Testing was carried out by the Team Jump product team using a combination of automated accessibility testing tools and manual testing with platform accessibility features on iOS and Android devices.