This accessibility statement applies to the University of Westminster Eploy Candidate Portal.
This website is run by The University of Westminster. We want as many people as possible to be able to use this website.
We’ve also made the website text as simple as possible to understand.
My Computer My Way has advice on making your device easier to use if you have a disability, and the AT Hive can help you find assistive technologies that work for you.
How accessible this website is
We know some parts of this website are not fully accessible. You can see a full list of any issues we currently know about in the Non-accessible content section of this statement.
Feedback and contact information
If you need information on this website in a different format such as accessible PDF, large print, easy read, audio recording or braille, or if you find any problems not listed on this page or think we’re not meeting accessibility requirements, email [email protected] for information on how to report an accessibility problem and request alternative formats.
Enforcement procedure
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).
Technical information about this website’s accessibility
The University of Westminster is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-accessible content listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
- Within the Cookies banner there are two additional tabstops that lack an accessible name or role and these do create a mismatch between the visible and programmatic focus order. This fails WCAG 2.4.3 Focus Order (A). Our supplier states this will be fixed by the end of March/Early April 2026.
- While logged in to the portal there is a session timeout that logs a user out after a period of inactivity, without warning or with no way to extend that time limit or turn it off. That period of inactivity is less than one hour. This fails WCAG 2.2.2 Timing Adjustbale (A). Our supplier states this will be fixed by the end of March/Early April 2026.
- When uploading files to the system, such as CVs and cover letters, there are restrictions on filetypes. Those file types are listed in text, in close proximity, however, there is no programmatic association between the accepted filetypes and the file upload input, therefore, this information could easily be missed by users of screen readers. This fails WCAG 1.3.1 Info and Relationships (A). Our supplier states this will be fixed by the end of March/Early April 2026.
- Some Login and/or Register inputs lack autocomplete attributes with correctly formed name value pairs, or in the case of the login page’s email input, it has an autocomplete with a value of “no”. This fails WCAG 1.3.5 identify Input purpose (AA). Our supplier states this will be fixed by the end of March/Early April 2026.
- When radio buttons or checkboxes are present across the system, typically during the application forms and these controls are required to have one (or more) options selected by the user, to progress, the fieldset element that contains the controls has the aria-required attribute present, this is invalid ARIA and fails WCAG 1.3.1 Info and Relationships (A). Our supplier states this will be fixed by the end of March/Early April 2026.
- On the file upload inputs the visible label does not match the accessible name. the visible label is “Select or drop files here” while the accessible name is “Upload file from my computer”. This fails WCAG 2.5.3 label in Name (A). Our supplier states this will be fixed by the end of March/Early April 2026.
- On the change password page, there are radio buttons for the question “Update password”, that text is not programmatically associated to the Yes and No answers as no programmatic grouping element such as a fieldset and lagend have been used. This fails SC 1.3.1 Info and Relationships (A). Our supplier states this will be fixed by the end of March/Early April 2026.
- The inputs on the change password page lack autocomplete attributes with valid values. This fails WCAG 1.3.5 Identify input Purpose (AA). Our supplier states this will be fixed by the end of March/Early April 2026.
- After confirming a user wishes to update their password, the New password field appears and does so in an error state, with an error message present. This fails SC 1.3.1 Info and Relationships (A). Our supplier states this will be fixed by the end of March/Early April 2026.
- Within the Update Password function, there are known parameters for an acceptable password. These parameters are not presented to a user in text. This fails WCAG 3.3.2 Labels or Instructions (A). Our supplier states this will be fixed by the end of March/Early April 2026.
- When selecting a slot for interview, the slots have no logical programmatic grouping, however, these items are laid out in card-type components and can be visually identified as independent blocks of information. This fails WCAG 1.3.1 Info and Relationships (A). Our supplier states this will be fixed by the end of March/Early April 2026.
- When refining vacancies using the fileter facets, should a keyboard user click a checkbox in the side panel, their focus is highjacked and automatically sent back to the beginning of that group of checkboxes. This is most obvious when the selected item was not the first item in the group. This fails WCAG 1.4.3 Focus Order (A). Our supplier states this will be fixed by the end of “Late” 2026.
- Within the candidate dashboard, there are tables which are used to present languages spoken, certificates/qualifications gained, references and other information necessary for the application process. These tables are 2-dimensional in nature and should have both row and column headers, however, at present the tables only have column headers. This fails WCAG 1.3.1 Info and Relationships (A). Our supplier states this will be fixed by the end of “Late” 2026.
The Eploy system is a new system and has been a long-running project. We initially tested the system in May 2025 and have worked with our supplier to resolve a number of accessibility issues. We will continue to work with our supplier to resolve the remaining issues, by the dates given.
If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Feedback and contact information’ section of this statement.
Disproportionate burden
At this time, we have not made any disproportionate burden claims.
Content that’s not within the scope of the accessibility regulations
At this time, we have not identified any content that is not within scope of the accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on 18 February 2026. It was last reviewed on 23 February 2026.
Testing was last carried out on 20 January 2026. The test was carried out internally by the University of Westminster Digital Accessibility Team, using a combination of manual techniques, automated and semi-automated tools and testing with a range of devices, browsers, operating systems and assistive technologies. Testing was completed against WCAG 2.2.