Skip to main content

Website Accessibility Statement

Ƶapp is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.


This accessibility statement applies to the Ƶapp website at durham.ac.uk.


Compliance Status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.


a) Non-accessible content


The content listed below is non-accessible for the following reason(s):


(i) Non-compliance with the accessibility regulations


WCAG 1.4.10 Reflow


Reflow or ‘responsive web design’ helps visually impaired users who may need to enlarge text on a webpage and read it in a single column without scrolling in more than one direction. It also helps users who are viewing the page on a mobile device. All content and functions must still be fully available in the adjusted size.


Issue: Our job search page is currently non-compliant.


Estimated to be resolved by: July-August 2024


WCAG 2.2.2 Pause, stop, hide


Content that moves, flashes or updates automatically can be a severe distraction, making it difficult to use an app or web page.


Moving, flashing or scrolling information that starts automatically and lasts more than 5 seconds, must have a way to pause, stop or hide it.


Issue: The Discover Uni (Unistats) widget, found on all undergraduate course pages is currently non-compliant. 
Estimated to be resolved by: July-August 2024


WCAG 2.4.4 Link purpose (in context)


The purpose of each link must be clear from the link text alone or from its immediate context. Users may tab through a set of links on a page, or may view a list of links using assistive technology. Clear link text makes navigation easier.


Issue: Our course search results pages have links with generic text ('view course')
Estimated to be resolved by: July-August 2024


WCAG 4.1.2 Name, role, value


Assistive technologies gather information about interactive elements and components from the code and share it with users. This means they need to be able to identify the name and function of components, set states, properties and values, and notify users of changes to these. 


ARIA attributes may be used on custom components to add this information. ARIA attributes should be used correctly as errors can make accessibility worse.


Issue: Our chatbot widget (Holly) found on some of our web pages is currently non-compliant.
Estimated to be resolved by: July-August 2024


(ii) The content is not within the scope of the accessibility regulations


The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.


We do not plan to add captions to live video streams because live video is .


Preparation of this accessibility statement

This statement was prepared on 2 February 2024 after an audit was carried out by the Government Digital Service, Accessibility Monitoring Team.

Last Updated: 9 July 2024

Feedback and Contact Information

Lucian Hudson, Director of Advancement, Marketing and Communications


The Palatine Centre


Stockton Road





Switchboard: +44 (0)191 334 2000


More ways to get in touch:



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).