Non accessible content
Non compliance with the accessibility regulations
This section of the accessibility statement will list the different aspects of the website that do not meet accessibility regulations. We are currently going through an extensive programme of testing our websites and applications. This page will be updated as these are completed.
This page was last updated on 9 July 2021.
If you need information on the affected websites in a different format like accessible PDF, large print, easy read, audio recording or braille or if you find any accessibility issues not listed on this page then please contact Imperial’s Web Accessibility team in ICT.
Some documents and content are exempt from the regulations (such as live video content and PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services), so we do not currently have any plans to make them accessible. But if you need to access information in one of these document types, you can contact us and ask for an alternative format.
Main Imperial website pages
The majority of content under www.imperial.ac.uk/ is created and published using Imperial's main content management system, terminal four (T4) site manager.
We have recently carried out extensive automated and manual testing of a number of samples pages, in order to test all combinations of templates and content types.
Sample pages used for testing
Sample of pages used for testing
For testing on the main Collge website, we tested the following URLs:
We are also in the process of upgrading to the latest version of site manager. Part of this process will be to review the accessibility of the editing interface.
- For the Whats on and Alumni section the :focus state is barely visible - WCAG regulations 1.4.3 (Contrast), 3.3.2 (Labels or Instructions)
User focus directed to new content
- For What's on the :focus state is very hard to see on each event block, no focus state on search bar, Calender is not keyboard focusable
- When new results are loaded into the page after clicking "show more", the focus should go to the next item
Custom controls have associated labels
- Slideshow controls are <span> tags. They should be <buttons>. Slides are focusable, but controls are not - WCAG regulation 1.4.3 Contrast, 3.3.2 Labels or Instructions.
Custom controls have ARIA roles
- Tabs do not have ARIA roles
- Chosen.js search filters do not have ARIA roles
- Slideshow controls do not have ARIA roles
Offscreen content hidden from screen readers
Slideshow (offscreen) slides are not hidden from screen readers.
Imperial login page
When accessing certain restricted applications of web pages you will be directed to an Imperial Collge London log in screen where users are promted for their Imperial username and password. There are currently a couple of accessibility issues with this page:
- The imperial College London logo and link to homepage do not display a focus state
- The Imperial College London logo image does not have a text alternative
- The text fields and button on the login form do not have associated labels
Non-accessible content in specific sections
The following covers content under www.imperial.ac.uk/ that is created and published using different content management systems:
- Imperial Stories
- Events and What's on
- Staff Professional Web Pages (PWPs)
- PWP editor
- News stories
- News editor
Third party content
Our website contains third-party content and tools. We do not have control over and are not responsible for the accessibility of this content, but we will in all cases try to work with the third party to improve accessibility.
Forms and surveys
We use a third party tool called Qualtrics for surveys and web forms. Some of these forms will be embedded on pages on the main Imperial website. Please read the accessibility statement for Qualtrics for details of how accessible the application and content is.
We are using a third party tool called Hotjar to allow visitors to the website to provide in-page feedback about their experience. As these are aspects are out of our control, we cannot provide any timescales on a fix.
It is not possible to maintain a tab focus in the popup.
Although the "next" button can be reached via keyboard tabbing, after pressing enter and then tabbing again to read a question, the keyboard focus will immediately be lost and the focus will return to the main page, essentially making it impossible to complete a poll via keyboard.