This website is run by the University of Warwick. We want as many people as possible to be able to use this website.
On this website, you should be able to:
This website is designed for a broad public audience so we aim to make the website text as simple as possible to understand.
If you have a disability then AbilityNet has advice on making your device easier to use.
We support our staff and students in their use of assistive software that you may find helpful.
We know some pages of this website aren't fully accessible:
We’re always looking to improve the accessibility of this website. Please contact us if you have any problems. It helps if you can be specific and detailed, if there are things you like and find useful, it would be great to hear about them. To report accessibility problems or ask about anything to do with accessibility use the contact details below.
Call: 024 765 73737 and ask to log your call for the Academic Technology team.
When you contact us by email or phone there is a process in place that will acknowledge your contact, tell you who is dealing with it and give you a timescale by which you can expect a reply. Once you have reported a problem with our website or asked for an alternative format, but you are not happy with our response, you can use our complaints process to register your difficulty; this helps us improve our systems.
If you are unhappy with the response you receive having contacted us using the details above, you can make a formal complaint to the University using our procedure for Feedback and Complaints.
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
The University of Warwick is committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This service is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
We are working to meet the compliance as specified in The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 by the September 2020 deadline. Meanwhile, the content listed below is non-accessible for the following reasons.
This website is pending an accessibility audit as at the latest date of publishing (02/10/2019).
The vast majority of our website works correctly on any web technology – we have built this website using open source software that has given consideration to accessibility as a core requirement of the technical platform, however some of the ways we have implemented and customised this software may alter its accessibility.
Drupal Accessibility Statement: https://www.drupal.org/about/features/accessibility
Academic Technology, the IT Services team responsible for publishing and maintaining this website test the customisations to these platforms that we make against the web browsers we support and we test our website infrastructure in these browsers as a minimum along with tablets and mobile devices too at the point of design.
For sites released since September 2019 we have a checklist that includes accessibility before we release a new site, or make significant changes. We use the Google Chrome Lighthouse tool for web developers and manually test against the accessibility objectives covered in this statement.
Our first priority is to ensure that accessibility is core to current and future work developed by the Academic Technology team by design, and where we work with academic colleagues who use this website to publish material, giving them tools and guidance on how to do so in an accessible way.
In addition, through our ongoing commitment to maintaining completed web outputs for past research, we will keep the core open source software patched and inherit any accessibility improvements made to these underlying platforms. We will also be auditing and testing our older websites to update and make our accessibility statements more informative and where we can reasonably make changes to our systems to make them more accessible, we will plan to make those changes