Accessibility statement for Anglia Ruskin University
This website is run by Anglia Ruskin University. We want as many people as possible to be able to use this website. For example, that means you should be able to:
We’ve also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
We know some parts of this website are not fully accessible:
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: webfeedback@anglia.ac.uk.
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).
Anglia Ruskin University is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
The content listed below is non-accessible for the following reasons.
Some of our video content does not have captions. This fails WCAG 2.1 success criterion 1.2.2 (captions (pre-recorded))
Some of our video content does not have an audio description or media alternative. The fails WCAG 1.2.3 (Audio Description or Media Alternative (Prerecorded))
You cannot skip to the main content from the keyboard or when using a screen reader. This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks - level A). We plan to fix this by September 2020.
In a small number of instances, such as tables, html is used to format content. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships). We plan to fix this by September 2020.
On some pages WAI-ARIA landmarks are not named. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships). We plan to fix this by September 2020.
On a small number of pages there are heading tags which are missing text. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships). We plan to fix this by September 2020.
On some pages the ID used for an element is not unique. This fails This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships) and success criterion 4.1.1 (Parsing). We plan to fix this by September 2020.
There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option). This fails WCAG 2.1 success criterion 2.4.1 (bypass blocks).
There’s no way to select seats using a keyboard only when booking for performances in our Mumford Theatre. This fails WCAG 2.1 success criterion 2.1.1 (Keyboard)
We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal.
Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).
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.
Any new PDFs or Word documents we publish will meet accessibility standards.
This website was last tested on 25 October 2019. The test was carried out by Anglia Ruskin University based on a sample of most-visited pages and with the assistance of SiteImprove. All flagged priority issues were investigated and, where possible, addressed.
We tested:
We have a rolling programme of updating the content and design of this website in accordance with the guidelines set out by the WCAG and will continue to assess and improve our accessibility based on these guidelines, user testing and user feedback.
This statement was prepared on 25 October 2019. It was last updated on 2 March 2020.