This accessibility statement applies to the website located at https://extensions.royalholloway.ac.uk
This website is run by Royal Holloway University of London. We want as many people as possible to be able to use this website. For example, that means you should be able to:
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website using a screen reader (for example the most recent versions of JAWS, NVDA)
In order to make our website easier to read and navigate, you can change display settings such as:
- text size
- colour and contrast
- screen magnification
Please see the following links for more information on how to change the display settings in your browser:
- Internet Explorer display settings
- Windows Edge display settings
- Chrome display settings
- Firefox display settings
- Safari display settings
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible this website is
We know some parts of this website are not fully accessible, we are working on these parts of the site and are committed to producing an accessible site for all users. Those parts with accessibility problems are as follows:
- The colour contrast between text and the background may not be enough to make the text easy to read for all users.
- When using a screen reader it may be difficult to identify exactly where some hyperlinks go just by using the link text.
- The text language is not defined in the page so some people who use screen readers or other technologies that convert text into speech may need to make manual adjustments to ensure the text is processed in the correct language.
- Some images do not have alternative text, these are not necessary to the operation of the website but may lead to confusion if viewed with a screen reader.
- Some aria labels used to help screen readers understand the text may not be in the expected format which may cause some users using screen readers confusion.
- When using a screen reader it may be difficult to identify different elements on the page.
- Some form inputs do not have labels which may make it difficult for someone with a screen reader to understand what the input field is for.
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille please contact the team via email.
We’ll consider your request and get back to you as soon as we can.
Reporting accessibility problems with this website
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 the team via email.
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).
Contacting us by phone or visiting us in person
Information about accessibility whist visiting us in person is displayed on our physical accessibility guide website.
If you need to contact us by phone you can do so on the following number: 01784 434455.
Technical information about this website’s accessibility
Royal Holloway University of London 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 and exemptions listed below.
The content listed below is non-accessible for the following reasons:
Non-compliance with the accessibility regulations
The following items are currently not compliant with WCAG 2.1 AA criteria:
- Some elements do not have sufficient colour contrast.
- The contrast between some foreground and background colours do not meet WCAG 2 AA contrast ratio threshold of 4.5:1 (WCAG: 1.4.3)
- Some links must have discernible text.
- Some link text that identifies the purpose of the link needs additional context (WCAG: 2.4.4, 4.1.2)
- <html> element does not have a lang attribute.
- The language is not specified in appropriate attribute in the html element (WCAG: 3.1.1).
- Some images do not have alternate text.
- Some <img> elements do not have alternate text or a role of none or presentation, although these images are not necessary to the operation or understanding of the application. (WCAG: 1.1.1)
- Some elements use allowed ARIA attributes that are not allowed.
- The following ARIA attribute is used which is not in the list of allowed attributes: aria-expanded="false" (WCAG: 4.1.2).
- ID attribute value must be unique.
- Not all ID attributes are unique on the page (WCAG: 4.1.1).
- Some form elements do not have labels.
- Some of the text boxes that are used to input information do not have labels which may make them difficult to use when using a screen reader (WCAG: 1.3.1 & 4.1.2)
- Links with the same name have a similar purpose.
- Some link text that identifies the purpose of the link needs additional context (WCAG: 2.4.9)
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
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.
What we’re doing to improve accessibility
We have a series of training material in place that we are using to educate our content editors in how to produce accessible content.
We are currently reviewing and improving the accessibility of our websites across the university and will be making further improvements this year.
Preparation of this accessibility statement
This statement was prepared on 19/09/2020. It was last reviewed on 19/09/2020.
This website was last tested in September 2020. The test was carried out by our internal teams using the Axe accessibility testing tool and manual testing across a subset of pages that represent the different template layouts used throughout the website.