Accessibility statement - jobs site

The University of Sheffield is committed to making its job page website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

The statement below applies to the new jobs site hosted at http://jobsite.sheffield.ac.uk/ which launched on Monday 16 December 2024.

Accessibility statement 

In response to the Cabinet Office Accessibility Audit and following the Accessibility Audit finding (as shown above) the University of Sheffield has implemented a new replacement recruitment system, including job web pages, on 16 December 2024, to address the previously reported accessibility issues (note - the previous accessibility audit is no longer applicable as at 16 December 2024).

This accessibility statement applies to the jobs site, which is hosted at http://jobsite.sheffield.ac.uk/, is public and part of the University website.u

In support of the recruitment system an accessibility audit of the new jobs web pages was undertaken in line with the Web Content Accessibility Guidelines version 2.2 AA standard.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed in the report (read the PDF report).

Non-accessible content

The content listed below is non-accessible for the following reason(s):

Non-compliance with the accessibility regulations

We know some parts of this website are not fully accessible and have summarised the report below. You can also view the summary as a spreadsheet. 

The pages referred to are:

• Page 1 - Global Header and Footer
• Page 2 - Job Landing Page
• Page 3 - Create an Account
• Page 4 - Candidate Profile
• Page 5 - Search and Apply - List View
• Page 6 - Search and Apply - Map
• Page 7 - Job Categories
• Page 8 - Job Description

Button, accordion or disclosure

Interactive elements with no accessible name

This can be found on pages 5 and 6 on iOS, with the bell icon-button for job alerts under the search button. The button does not have an accessible name.

Expandable element is not programmatically identified

This can be found on page 4 on desktop and iOS, with the "Upload a CV" disclosure within the "My Documents" section. The disclosure has an expandable panel. However, it is not programmatically determined as expandable.

Custom focus indication fails contrast

This can be found on page 3 on desktop, with the input fields under the "Career Opportunities: Create an Account" heading, such as "Email Address", "Retype Email Address", "Choose Password", and so on.

This can be found on pages 5 and 6 on the desktop, with the "Search for a job" and "Search by location" input fields within the search region.

Heading

Heading semantics

This can be found on page 2,4,5 and 6 on desktop and iOS.

Image

Decorative image has redundant text alternative

This can be found on page 2 on desktop and iOS, with the images preceding the "Members of staff smiling", "Firth Court building" and "Firth Court building" links under the "A remarkable place to work" heading.

The images are decorative. However, the images are exposed to assistive technology with text alternatives, "Members of staff smiling", "Firth Court building" and "Firth Court building" using `aria-label` and `title` attributes.

That is, the decorative images have redundant text alternatives.

This can also be found on page 7 on desktop and iOS, with the banner image at the top of the page. The image is decorative. However, the image is exposed to assistive technology with the text alternative "Member of staff inside a lab" using `aria-label` and `title` attributes. That is, the decorative image has a redundant text alternative.

Informative image has inappropriate text alternative

This can be found on page 8 on desktop and iOS, with the image that contains the logo images at the bottom of the page.

The image has the text alternative "Logos Collage" using `alt`. This text alternative does not communicate the purpose of the image.

Reflow causes loss of content

This can be found on page 8 on desktop, with the image for the logo images at the bottom of the page.

The image is informative. However, the image is cut off when the page is reflowed.

Decorative icon not hidden from assistive technology

This can be found on pages 5 and 6 on desktop, with the bell icon preceding the "Get Job Alerts for This Search" button below the search panel.

The icon is decorative. However, it is not hidden from assistive technology.

This can also be found on page 8 on desktop, with the bell icon preceding the "Create an alert for this job?" button below the search panel.

The icon is decorative. However, it is not hidden from assistive technology.

Input field

Additional information is not associated with input field

This can be found on pages 5 and 6 on desktop and iOS, with the checkboxes for the filters within the accordion panels under the "Refine your search" heading, such as "Human Resources", "Health & Safety", and so on.

Every checkbox has the number of the applicable jobs pinned to it. However, this number is not programmatically associated with the checkbox.

Autocomplete value inappropriately set to off

This can be found on page 2 on desktop and iOS, with the "Enter Email Address" input field within the" Keep in touch" section.

Inappropriate autocomplete value used

This can be found on page 3 on desktop and iOS, with the input fields under the "Career Opportunities: Create an Account" heading, such as "Email Address", "Retype Email Address", "Choose Password", and so on.

The input fields have `autocomplete` attributes set to `chrome-off`. This value is inappropriate.

This can also be found on page 4 on desktop and iOS, with the input fields within the "Profile Information" section, such as "First Name", "Middle Name", "Preferred Name", and so on. The input fields have `autocomplete` attributes set to `chrome-off`. This value is inappropriate.

Autocomplete attribute has not been used

This can be found on page 4 on desktop and iOS, with the "Date of birth" input field within the "Profile Information" section.

The input field does not have an appropriate `autocomplete` attribute.

Error messages that appear on blur have no programmatic call-to-action

This can be found on page 3 on desktop and iOS, with inline error messages pinned to the form fields within the "Career Opportunities: Create an Account" section, such as "Email Address", "Retype Email Address", and so on.

When the user navigates away from a form field leaving it with an invalid or no entry, the inline error message is dynamically added to the page pinned to the relevant input field.

This can also be found on page 4 on desktop and iOS, with the inline error messages pinned to input fields within the "Profile Information" section, such as "Title", "First Name", and so on.

When the user navigates away from a form field leaving it with an invalid or no entry, the inline error message is dynamically added to the page pinned to the relevant input field.

This can also be found on page 4 on desktop and iOS, with the inline error messages pinned to the form fields within the "Previous Employment" section, such as "Company Name", "Job Title", and so on.

When the user navigates away from a form field leaving it with an invalid or no entry, the inline error message is dynamically added to the page pinned to the relevant input field.

No live region is declared for this error message. As a result, the error message does not have a programmatic call-to-action. 

Interactive elements do not have a permanent label

This can be found on page 2 on desktop and iOS, with the "Enter Email Address" input field.

The input field relies on the placeholder text "Enter Email Address" as its only visual signifier.

Password requirements tracker not programmatically determined

This can be found on page 3 on desktop and iOS, with the status message for password requirements updates pinned to the "Choose Password" input field, such as "Required: N more characters, NN upper case letter".

On entering text in the input field, the status message is updated to indicate which requirements are still outstanding.

However, no live region is used to communicate these updates. That is, the password requirements updates are not programmatically determined.

Link

Positive tab index value breaks focus order

This can be found on page 1 on desktop, with the "About the University" and "Living in Sheffield" links within the dropdown panel for the "Working at Sheffield" disclosure within the header.

This can also be found on page 1 on desktop and iOS, with the "Guidance on using our recruitment system", "Pre-employment processes" and "Accessibility statement - Jobs portal " links within the dropdown panel for the "Help with Applying" disclosure within the header.

Focused element is completely hidden by sticky footer

This can be found on page 1 on desktop, with the cookies banner within the footer.

The banner obscures part of the page content. However, the elements behind it can still receive keyboard focus. For example, when tabbing through the page, the banner fully obscures the social media links and other links within the footer, such as "Feedback", "Privacy", and others, along with their focus indicators, when they receive focus.

List

Unordered list not marked up semantically

This can be found on page 4 on desktop and iOS, with the "Expand all sections" and "Collapse all sections" buttons under the "Candidate Profile" heading. The buttons are not programmatically determined as unordered list items.

This can be found on page 5 on desktop and iOS, with the buttons for the applied filters, as well as the "Clear All" button, above the search results. The buttons are not programmatically determined as unordered list items.

This can also be found on page 5 on desktop and iOS, with the job details within the job titles within the search result section, such as salary range, employment type, department, and so on.

The job details are not programmatically determined as unordered list items.

This can also be found on page 5 on iOS, with the "Filter", "Sort" and "Job alerts" icon-buttons below the search panel. The buttons are not programmatically determined as unordered list items.

This can also be found on page 6 on desktop and iOS, with the job details within the job slides within the map view, such as salary range, employment type, department, and so on. The job details are not programmatically determined as unordered list items.

Listbox

Missing or malformed ARIA on non-collapsible listbox

This can be found on pages 5 and 6 on desktop and iOS, with the "List view" and "Map view" icon-options following the "Sort by" dropdown above the search results.

The options are marked up using separate `<li>` elements with `role="option"` attributes. However, they are not contained within a `<ul>` element with `role="listbox"` attribute. As well, the `<ul>` container does not have an accessible name.

Selected element is not programmatically identified

This can be found on page 4 on desktop and iOS, with all drop-downs within the "Profile Information", "Previous Employment" and "Education and Training" accordion panels, such as "Title", "Country", and so on.

The selected option within the listboxes for the drop-downs is not programmatically determined as selected.

Listbox with no accessible name

This can be found on page 4 on desktop and iOS, with all drop-downs within the "Profile Information", "Previous Employment" and "Education and Training" accordion panels, such as "Title", "Country", and so on.

The listboxes for the drop-downs do not have accessible names.

Mega menu

Menu semantics used inappropriately

This can be found on page 1 on desktop and iOS, with the dropdown panels for the "Working at Sheffield", "Job Categories" and "Help with Applying" disclosures within the header.

The links within each of the panels are using `role="menuitem"` and are contained within an element that uses `role="menu"`. However, these elements do not have application menu functionality. The elements are standard navigational links. 

1. Observe the components on the page.
2. Inspect the elements and review the DOM.
3. Observe the use of menu semantics.
4. Observe that the components are not an appropriate use case for the role.

Non-applicable

Focus is not managed appropriately when content is removed from the page

This can be found on page 5 on desktop, with the buttons for the applied filters, as well as the "Clear All" button, above the search results.

Upon activating any of the buttons to clear the relevant filter, the button is dynamically removed. However, the focus is set onto the `<body>` element instead of moving onto a logical element, such as the "N to N of NN results" heading preceding the search results, or one of the neighbouring buttons.

This can also be found on pages 5 and 6 on desktop, with the "Previous" and "Next" buttons within the pagination region at the bottom of the page. 

Upon activating any of the buttons to navigate to another page, the button is dynamically removed. However, the focus is set onto the `<body>` element instead of moving onto a logical element, such as the "N to N of NN results" heading preceding the search results, or one of the neighbouring buttons.

Focus is not managed appropriately when page is dynamically updated

This can be found on page 5 on desktop, with the pagination buttons within the navigation region at the bottom of the page.

Upon activating any of the buttons, it becomes disabled. However, the focus is set onto the `<body>` element instead of moving onto a logical element, such as the "N to N of NN results" heading preceding the search results, or one of the neighbouring buttons.

Preparation of accessibility statement

This statement was reviewed and updated on 16 December 2024, following the implementation of the new jobs site.

The new site has been retested by Ability.Net against the WCAG 2.2 AA standard between 13 and 15 November 2024.

Read the updated accessibility test report

Feedback and contact information

If you find any problems not listed on this page or included in this report or think we’re not meeting accessibility requirements, email jobs@sheffield.ac.uk to report these issues.

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, email jobs@sheffield.ac.uk

We’ll consider your request and get back to you.

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).