Accessibility statement for ZetaSafe (Mobile Application)

Application accessibility statement in line with Public Sector Body (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018

This accessibility statement applies to:

the (Android) (iOS) mobile application ZetaSafe which can be downloaded from various mobile application stores.

This is a third party mobile application produced by ZetaSafe and purchased and used by Estates at the University of Edinburgh. We want as many people as possible to be able to use this application. For example, that means you should be able to:

  • Use the application without needing to repeat information
  • Encounter no moving, flashing or scrolling text
  • Use the application without encountering any cognitive function tests

We’ve also made the application’s text as simple as possible to understand. However, some of our content is technical, and we use technical terms where there is no easier wording, we could use without changing what the text means.

Customising the application 

AbilityNet has advice on making your device easier to use if you have a disability. This is an external site with suggestions to make your computer more accessible:

AbilityNet - My Computer My Way

How accessibile this application is 

We know some parts of this application are not fully accessible:

  • Some colour contrasts do not meet minimum WCAG 2.2 AA requirements 
  • Not all non-text content has a text alternative 
  • Some information is conveyed by colour only
  • Pinch and expand doesn’t work on all content
  • iOS screen reader is not fully compatible with reading some content 
  • Android version can’t be viewed clearly in landscape mode
  • Pop ups open without warning 
  • Some required fields are not labelled as such
  • Some pop ups disappear quickly without the user doing anything

Feeback and contact information 

If you need information on this application in a different format, including accessible PDF, large print, audio recording or braille:

  • Email: Craig.Marc@ed.ac.uk
  • Telephone: 07816 147 633
  • British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service.

We’ll consider your request and get back to you in 5 working days.

Reporting accessibility problems with this application 

We are always looking to improve the accessibility of this application. If you find any problems not listed on this page, or think we’re not meeting accessibility requirements, please contact:

  • Email: Craig.Marc@ed.ac.uk
  • Telephone: 07816 147 633
  • British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service.

We’ll consider your request and get back to you in 5 working days.

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 please contact the Equality Advisory and Support Service (EASS) directly:

Contact details for the Equality Advisory and Support Service (EASS)

The government has produced information on how to report accessibility issues:

Reporting an accessibility problem on a public sector website

Contacting us by phone using British Sign Language 

British Sign Language service 

Contact Scotland BSL runs a service for British Sign Language users and all of Scotland’s public bodies using video relay. This enables sign language users to contact public bodies and vice versa. The service operates from 8.00am to 12.00am, 7 days a week.

Contact Scotland BSL service details.

Technical information about this application's accessibility 

The University of Edinburgh is committed to making its websites and applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. 

Compliance Status 

This application is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard, due to the non-compliances listed below.

The full guidelines are available at:

Web Content Accessibility Guidelines (WCAG) 2.2 AA standard

Non accessible content

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

Noncompliance with the accessibility regulations 

The following items to not comply with the WCAG 2.2 AA success criteria:

We aim to improve our applications accessibility on a regular and continuous basis. See the section below ('What we're doing to improve accessibility') on how we are improving our app accessibility. 

The majority of the application is out with our control and we are working with the suppliers to address the issues listed above. Where items are within our control we are working towards solving these problems and expect significant improvements by June 2027.

Disproportionate burden 

We are not currently claiming that any accessibility problems would be a disproportionate burden to fix.

Content that’s not within the scope of the accessibility regulations 

At this time, we believe no content is out with the scope of the accessibility regulations.

What we’re doing to improve accessibility 

We will continue to address the accessibility issues highlighted, working alongside the software suppliers to deliver a solution or suitable workaround. Unless specified otherwise, a complete solution or significant improvement will be in place for those items within our control by June 2027. 

While we are in the process of resolving these accessibility issues, we will ensure reasonable adjustments are in place to make sure no user is disadvantaged. As changes are made, we will continue to review accessibility and retest the accessibility of this application.

Preparation of this accessibility statement 

This statement was prepared on 15th June 2026. It was last reviewed on 15th June 2026.

The application was last tested in June 2026. The testing was carried out by the Disability Information Service at the University of Edinburgh using manual methods. The app was tested on mobile, primarily using iOS (iPhone 13, iOS version 26.5) and Android (Samsung Galaxy A40).

We manual tested the following:

  • Spell check functionality;
  • Options to customise the interface (magnification, font, background colour, etc);
  • Data validation;
  • Warning of links opening in new tab or window;
  • Information conveyed in the colour or sound only;
  • Flashing, moving or scrolling text;
  • Tooltips and text alternatives for any non-text content;
  • Time limits;
  • Compatibility with mobile accessibility functionality (Android and iOS);
  • compatibility with Mobile screen readers TalkBack and Voice over;
  • Any drag functionality and alternatives;
  • Help functionality being located in the same place on each page;
  • Colour contrasts;
  • The need for any specific keystrokes;
  • The ability to view the application in landscape and portrait mode;
  • No need to re-enter data already submitted;
  • Any cognitive tests.

Change Log 

This article was published on