You’re offline. This is a read only version of the page.
This statement applies to content published on My Imperial Portal, it does not apply to content on any external websites or systems that we may feature links to.
We want as many people as possible to be able to use this website. For example, that means you should be able to:
AbilityNet has advice on making your device easier to use if you have a disability.
Parts of this platform are not fully accessible. For example:
We work to achieve and maintain WCAG 2.1 AA standards, but it is not always possible for all our content to be accessible. Where content is not accessible, we will state a reason, warn users, and offer alternatives.
Imperial College London is committed to making its platforms accessible in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Imperial College My Imperial app is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the known issues listed below.
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.
On all pages, the decorative image found within the hamburger menu contains inappropriate alternative text. Which may cause confusion to screen reader users. This fails 1.1.1 non-text criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Most pages have incorrect heading structures. Headings are not correctly nested in hierarchical order. This fails 2.4.1 bypass blocks criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
A field set without a legend is present across all form pages. This fails 1.3.1 info and relationships criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Across all pages, all sections of the pages that tested, no content is contained within ARIA landmarks, which means page regions are not identified with landmarks. This fails 1.3.1 info and relationships criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Pages are missing descriptive page titles. This fails 2.4.2 page titles criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Identical link texts present: On the ‘Qualifications’ section of the application, there are multiple instances of ‘add qualification’ on this page, with no way to differentiate between them. This fails 2.4.4 Link Purpose (in context) criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Text Description Not Provided for Error Fields: On the ‘Add Qualification’ page, the text error does not highlight which form field is incorrectly entered. Because the form field that is invalid is not identified to the user, they may not be aware of which form field requires their attention. This fails 3.3.1 error identification criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Mandatory Fields Do Not Show Text Error: On the ‘Visa & Immigration’ application page, if the user submits the form with empty mandatory fields, an error is displayed which is not user friendly, displaying the full html error instead of simple text. This fails 3.3.1 error identification criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Low contrast issues: On the Home Dashboard, the menu navigation options text has a low contrast (4:1) On the Applications page, the applications link on the grey background has a low contrast (4.1:1) the selected page number has a low contrast (1.1:1) On all New Application pages, the completed pages in the side menu have a low contrast (3.5:1) the previous page button text has a low contrast (4.4:1) This fails 1.4.3 contrast (minimum) criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Across all pages, the cookies button has a contrast low contrast of 2.5:1 against the page background. On pages where a slider is present, the inactive slider has a low contrast of 1.8:1 against the page background. This fails 1.4.11 non- text contrast (minimum) criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Tab Order is Not Logical: On the homepage, a hidden tab stop is present between 'Applications' and 'References’. This fails 2.4.3 focus order criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Visible Tab focus indicator is missing on select elements: On select pages, such as the 'Disabilities' and 'About you' pages, the user is not provided a visible focus indicator for certain elements. On the 'Disabilities' page, the dropdown arrows for each disability are not highlighted correctly. On the 'About' page, no indicator for the 'Previous' button has been observed, this also affects pages where this button lacks styling. This fails 2.4.7 focus visible criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Autocomplete Attribute Not Present: On the 'About you' and 'Address' pages, fields such as 'Email', 'Phone' and the users name, do not contain an 'auto complete' attribute. This fails 1.3.5 Identity Input purpose criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Mobile- content announced incorrectly: On all pages on mobile devices, content is incorrectly announced across multiple pages. Some examples are: ‘Menu’ side nav, where the user is navigated to the main content first. On the Dashboard, the ‘Application’ and ‘References’ buttons do not announce until the user has swiped multiple times on the element, as each model receives focus on mobile devices. This fails 4.1.2. Name role Value criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Mobile – Unable to Upload Files Using Dragon Naturally Speaking; When interacting with any upload feature using Dragon Naturally Speaking, users are unable to interact with the component using any known voice commands. This fails 4.1.2. Name role Value criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
Missing start and end tags -Elements not nested according to their specifications -Elements contain duplicate attributes -IDs that are not unique, except where the specifications allow these features. This fails 4.1.1. Parsing criterion. We are aiming to resolve this by February 2024. (However, this cannot be addressed without the Vendor’s intervention. Therefore, this date may change depending on their timeline.)
N/A
If you need information on this website 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 SLCRMteam@imperial.com.
We’ll consider your request and get back to you in enter a response time based on our SLAs, max 7 working days.
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).
The test carried out by our external quality assurance company Zoonou consisted of an accessibility review of the My Imperial Portal against WCAG 2.1 Level A and AA criterions. Testing was conducted against the application and the accompanying pages. One user journey was conducted against the 7 assistive technologies specified below.
Target Template URLs
On the test environments:
Last updated: This statement was prepared on 12/09/2023. It was last updated on February 2024.