This accessibility statement applies to SafeZone application.
SafeZone, is a CriticalArc mobile phone application. We want as many people as possible to be able to use this application, which means that you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 400% without the text spilling off the screen
- navigate the website using just a keyboard
- navigate the website using speech recognition software
- listen to most of the website using a screen reader
There are a number of customisation options for your browser and device that could help you use this website and other websites more effectively. AbilityNet has advice on making your device easier to use if you have a disability.
Feedback and contact information
Please contact us if you have an accessibility query including:
- If you are experiencing issues with accessing information or using the mobile application.
- If you find an accessibility problem not listed on this statement.
- If you have positive feedback on the accessibility considerations made.
When you contact the SafeZone Team, if there is a process in place to acknowledge your contact, you will receive an email stating who is dealing with your query. This response should also outline an potential timescales by which you can expect a reply.
We aim to respond to all contacts within 3-5 working days.
Reporting accessibility problems with this website
We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG (Web Content Accessibility Guidelines) 2.2 AA standards.
We're always looking to improve the accessibility of this mobile application. If you find any problems not listed on this page or think we're not meeting accessibility requirements, please contact us.
Read tips on contacting organisation about inaccessible websites.
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).
Technical information about this website's accessibility
University College London is committed to making this mobile application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
We believe this website to be fully compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 AA standard.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Applies to Android and IOS: Errors in some forms are only reported with an image. The main forms do have accessible error messages. This fails 3.3.1 Error Identification (A) and WCAG 4.1.2 Name, Role, Value (A).
Applies to Android and IOS: A placeholder has been used to communicate the required form field information. This fails WCAG 3.3.2 Labels and instructions (A) and WCAG 4.1.2 Name, Role, Value (A).
Applies to Android and IOS: The application currently only operates in Portrait mode only. This fails WCAG 1.3.4 Orientation (AA).
Applies to Android and IOS: Our current technology stack limits our ability to support resizable fonts on both Android and iOS. CriticalArc (SafeZone) are currently moving to a new stack which will support this. Font sizes on critical functions, such as the Alert buttons, are designed to be large and with additional colour iconography, so the button is more visable to users, but this cannot be changed by the user. This fails WCAG 1.4.4 Resize Text (AA).
If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Reporting accessibility problems with this website’ section of this statement.
Disproportionate burden
At this time, we have not made any disproportionate burden claims.
Content that’s not within the scope of the accessibility regulations
This section covers issues that we do not need to fix right now. The law calls these exemptions.
Third-party content
Our applications may contain third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make best endeavours to work with the third-party to improve its accessibility. This may include:
- links to non-UCL websites
- content/functionality on our website
- content hosted on other websites, such as social media sites.
To help accessibility compliance across the sector, University College London supports searchBOX, a centralised, independent directory of third-party accessibility information.
searchBOX catalogues the contact information and accessibility statements of third-party suppliers, enables the sharing of community-generated accessibility statements, and allows users to map their supplier ecosystem.
Users can access third-party accessibility statements using the free searchBOX Finder service.
University College London encourages all our partners and suppliers to support this effort by ensuring that their accessibility information is included in the searchBOX directory.
Our testing processes
Testing for this application has been carried out by the developer. If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to the owner who will review the issue, make sure it is included in our plan to fix issues and add it into the accessibility statement when it is next updated.
Please refer to CriticalArc's Accessibility statement for further information.
Preparation of this accessibility statement
This statement was prepared on 14 January 2025 by UCL. It was last reviewed on 8 August 2024. This application was last tested on 8 August 2024 for Version 3.0. The test was carried out by CriticalArc.
What we’re doing to improve accessibility
University College London (UCL) is working with CriticalArc to fix or provide alternatives for all issues that we are made aware of and as identified by our periodic internal testing and auditing processes. The latest information we have on the current issues noted above is as follows.
In terms of a roadmap, we are looking to resolve the remaining items for the SafeZone application, which are currently blocked by technology constraints. These constraints should be addressed in the next 4-5 months as part of a major app re-platforming and accessibility improvements are the first thing that will be deployed. The text resizing is already at testing stage on new apps and we are researching tools to help landscape orientation. All issues noted will be fixed within the next 6 months.