Accessibility statement

How can you use this website?

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:

change colours, contrast levels and fonts.
zoom in up to 300% without the text spilling off the screen.
navigate the website using just a keyboard, you can use links to skip over the navigation and get to content quicker.
listen to most of the website using a screen reader, including the most recent versions of JAWS, NVDA, and VoiceOver. For example, in Microsoft Edge, you can read aloud the pages by pressing Ctrl + Shift + U.
view the website on a tablet or mobile device in either orientation.

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.

How accessible is this website?

We know some pages of this website are not fully accessible:

For very small devices, the website will work but you may experience some minor text-overlaps in some pages (usually when viewed in portrait). We tested using small devices like Sony Ericsson XZ2 compact.
Interactivity such as inter-linked text, keyword searches, selection from drop-down menu listings, maps, and timelines are frequently used to provide rich visual interfaces to engage with media and data in the field of digital humanities. We design all of our sites to have text-based alternative navigation routes for access to and displays of the content, but some presentations of that content may not function as intended.
Some of the interactive elements, especially timelines, may have colour or contrast issues.

What should you do if you can't access or are having difficulty using this website?

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.

Email: ResearchComputingRSE@warwick.ac.uk

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.

Complaints

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.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website's accessibility

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. As a small team, we draw on the “disproportionate burden” component of the regulations where we are unable to fully meet all requirements.

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

Non-compliance with the accessibility regulations

Not all elements of the interactive timelines satisfy the minimum contrast criterion.
Navigation of the website using just a keyboard is currently not to the standard required. For some interactive elements, the focus outline of the currently highlighted link is not clear and the order of links that are selected when pressing the tab key does not follow the order of the items on the page.

Issues with technology?

The vast majority of our website works correctly on any web technology – we have built this website using open-source software (e.g., Omeka S) 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.

Omeka S Accessibility Statement https://omeka.org/s/docs/user-manual/accessibility/

For security reasons, we only support TLS 1.2 and higher security protocols; this means that some older Web Browsers will not show the site. For accessibility reasons, web browsers we support do recommend use of JavaScript and where JavaScript is disallowed in the browser, visitors may experience that some of the pages may not work properly.

How do we test this website?

The research computing 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 (or Microsoft Edge Developer) tools for web developers and manually test against the accessibility objectives covered in this statement.

What are we doing to improve accessibility?

Our first priority is to ensure that accessibility is core to current and future work developed by the Research Computing 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.