Go Jauntly is a social impact company which strives to get more people outside to enjoy the mental and physical benefits of connecting with nature and our surroundings. To do so, we are continually working on our features with the aim of making them inclusive for all.
Accessibility Statement
This accessibility statement applies to the website and mobile application Go Jauntly on iOS and Android. This statement was prepared on 22nd July 2021.
Key accessibility features of our iOS mobile application include:
Filter walks by selecting the wheelchair-friendly feature when you search.
Zoom in using iOS zoom features for larger text for those who are partially sighted, while low vision users can easily listen to all text using “Speech” in iOS settings.
Use “VoiceOver” in iOS settings to navigate more easily throughout the app with larger labels, clearer descriptions and a more intuitive order for those who are blind or have low vision.
We also have local features such as station accessibility information for each TfL station in London, provided by TfL’s open data.
Audio-narrated walks include written transcripts for the hard of hearing.
Key accessibility features of our Android mobile application include:
Filter walks by selecting the wheelchair-friendly feature when you search.
Use “Screen Reader” in Android settings to navigate more easily throughout the app with larger labels, clearer descriptions and a more intuitive order for those who are blind or have low vision.
Audio-narrated walks include written transcripts for the hard of hearing.
In addition, we work closely with partners to encourage clearer descriptions and pictures of routes, for example the surface condition of paths, and to ensure that there are step-free options for our partner walks.
When making design improvements to the app we consider accessible practices and implement recommended techniques such as:
Providing users enough time to read/use content;
Avoiding moving, blinking and scrolling information;
Providing tool tips and informative error messages;
Presenting content in meaningful sequence;
Avoiding use of colour alone for conveying information.
Compliance status
We have completed a thorough audit of our mobile application against The Web Content Accessibility Guidelines (known as WCAG 2.1).
Currently we pass on 44 out of 50 level AA and 20 out of 28 of level AAA. This mobile application is therefore considered partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.
Non-compliance with the accessibility regulations:
Some buttons are unlabelled and some buttons do not work when you double tap. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content). We plan to fix this by December 2022 at the latest. When we publish new content we’ll make sure our use of images meets accessibility standards.
Some of our content cannot be presented in different ways without losing information or structure. This partially fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships). We plan to fix this by December 2022 at the latest. When we publish and present new content we’ll make sure it meets accessibility standards.
We could make it easier for users to see and hear content including separating foreground from background. This partially fails WCAG 2.1 success criterion 1.4.3 [Contrast (Minimum)]. We plan to fix this by December 2022 at the latest. When we publish new content and features we’ll make sure it meets accessibility standards.
As we are a mobile application, some of our functionality is not available from a keyboard. This technically fails WCAG 2.1 success criterion 2.1.1 (Keyboard). We plan to adjust what we can by December 2022 at the latest. When we publish new content and features we’ll make sure all functionality meets accessibility standards.
Not all of our user interface components can be programmatically determined or maximise compatibility with current and future user agents including assistive technologies. This partially fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value) and 4.1.3 (Status Messages). We plan to fix this by December 2022 at the latest. When we publish new content we’ll make sure all user interface components meet accessibility standards.
Content that’s not within the scope of the accessibility regulations:
Not all content is accessible when using our mapping features, yet maps are essential to providing our service.
What we’re doing to improve accessibility
Our team is working hard to comply with all guidelines by the end of 2022. We will ensure that, from now on, all new technology or features of Go Jauntly will be fully compliant with WCAG 2.1 level AA.
Technical information about this mobile application’s accessibility
Go Jauntly is committed to making its mobile application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Reporting accessibility problems with this mobile application
We’re always looking to improve the accessibility of our mobile application. If you find any problems not listed on this page, think we’re not meeting accessibility requirements, or have any questions, suggestions or comments on the inclusivity of our design, please contact us via hi@gojauntly.com
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Preparation of this accessibility statement
This statement was prepared on 22nd July 2021. It was last reviewed on 22nd July 2021.
Our mobile application was last tested on 22nd July 2021. The test was carried out by us and included a thorough audit of Go Jauntly alongside levels A, AA and AAA of the The Web Content Accessibility Guidelines.