ABCDEFGHIJKLMNOPQ
1
idDescription SummaryWhere it happenedSuccess CriteriaPages AffectedComponent
2
ADR_20580-10Decorative image has redundant text alternativeThis 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.

1.1.1: Non-text content [2.0 A]02, 07Image
3
ADR_20580-26Informative image has inappropriate text alternativeThis 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.
1.1.1: Non-text content [2.0 A]08Image
4
ADR_20580-5Heading semantics used inappropriatelyThis can be found on page 2 on desktop and iOS, with the "Inclusion & Diversity", "Working at the Sheffield" and "Accessibility Statement" links under the "A remarkable place to work" heading.

The links do not title or categorise other content. However, they are inappropriately programmatically determined as headings at level 2.
1.3.1: Info and Relationships [2.0 A]02Heading
5
ADR_20580-12Heading not marked up semanticallyThis can be found on page 4 on desktop and iOS, with the "Key points to note" heading under the "Candidate Profile" heading.

The heading titles the content below it and is visually presented as a heading. However, it is marked up as a `<strong>` element. That is, the heading is not marked up as a heading at level 2.

This can also be found on page 8 on desktop and iOS, with the "Consultant Professor wanted" heading.

The heading titles the content below it and is visually presented as a heading. However, it is marked up as a `<p>` element. That is, the heading is not marked up as a heading at level 2.

1.3.1: Info and Relationships [2.0 A]04, 08Heading
6
ADR_20580-43Additional information is not associated with input fieldThis 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.

1.3.1: Info and Relationships [2.0 A]05, 06Input Field
7
ADR_20580-44Heading link not marked up semanticallyThis can be found on page 5 on desktop and iOS, with the links for the job titles within the search results, such as "Test Position", "Apprentice", and so on.

The links title the content below them and are visually presented as headings. However, they are not marked up as headings at level 3.

1.3.1: Info and Relationships [2.0 A]05Heading
8
ADR_20580-2Autocomplete value inappropriately set to offThis can be found on page 2 on desktop and iOS, with the "Enter Email Address" input field within the" Keep in touch" section.

The input field has an `autocomplete` attribute set to `off` inappropriately.

1.3.5: Identify Input Purpose [2.1 AA]02Input Field
9
ADR_20580-31Inappropriate autocomplete value usedThis 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.

1.3.5: Identify Input Purpose [2.1 AA]03, 04Input Field
10
ADR_20580-37Autocomplete attribute has not been usedThis 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.

1.3.5: Identify Input Purpose [2.1 AA]04Input Field
11
ADR_20580-35Regular text does not have sufficient contrast on hoverThis can be found on page 4 on desktop and iOS, with the "Save" button within the "Education and Training" accordion panel.

On mouse hover, the white (#FFFFFF) text for the button has an insufficient contrast ratio of 1.3:1 against its light blue (#BBE6FC) background.

1.4.3: Contrast (Minimum) [2.0 AA]04Button
12
ADR_20580-32Reflow causes loss of contentThis 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.

1.4.10: Reflow [2.1 AA]08Image
13
ADR_20580-34Custom focus indication fails contrastThis 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.


1.4.11: Non-text Contrast [2.1 AA]03, 05, 06Button, Accordion or Disclosure, Input Field
14
ADR_20580-7Positive tabindex value breaks focus orderThis 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.



2.4.3: Focus Order [2.0 A]01Link
15
ADR_20580-41Focus is not managed appropriately when content is removed from the pageThis 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.

2.4.3: Focus Order [2.0 A]04, 05, 06Not Applicable
16
ADR_20580-42Focus is not managed appropriately when page is dynamically updatedThis 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.

2.4.3: Focus Order [2.0 A]05Not Applicable
17
ADR_20580-4Focused element is completely hidden by sticky footerThis 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.

2.4.11: Focus Not Obscured (Minimum) [2.2 AA]01Link
18
ADR_20580-1Errors messages that appear on blur have no programmatic call-to-actionThis 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.

3.3.1: Error Identification [2.0 A]03, 04Input Field
19
ADR_20580-9Interactive elements do not have a permanent labelThis 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.

3.3.2: Labels or Instructions [2.0 A]02Input Field
20
ADR_20580-6Menu semantics used inappropriatelyThis 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.		4.1.2: Name, Role, Value [2.0 A]01Mega Menu
21
ADR_20580-16Expandable element is not programmatically identifiedThis 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.

4.1.2: Name, Role, Value [2.0 A]04Accordion or Disclosure
22
ADR_20580-19Missing or malformed ARIA on non-collapsible listboxThis 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.

4.1.2: Name, Role, Value [2.0 A]05, 06List-box
23
ADR_20580-20Selected element is not programmatically identifiedThis can be found on page 4 on desktop and iOS, with all dropdowns 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 dropdowns is not programmatically determined as selected.

4.1.2: Name, Role, Value [2.0 A]04List-box
24
ADR_20580-28Heading semantics overridden by button semanticsThis can be found on pages 5 and 6 on desktop and iOS, with the "Job Category", "Work Arrangement", "Faculty" and "School/Department" accordions under the "Refine your search" heading.

The accordion headings are marked up as headings at level 3. However, they are contained within buttons. That is, the heading semantics are overridden by the parent button semantics.

4.1.2: Name, Role, Value [2.0 A]05, 06Heading
25
ADR_20580-38Interactive elements with no accessible nameThis 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.
4.1.2: Name, Role, Value [2.0 A]05, 06Button
26
ADR_20580-46Listbox with no accessible nameThis can be found on page 4 on desktop and iOS, with all dropdowns within the "Profile Information", "Previous Employment" and "Education and Training" accordion panels, such as "Title", "Country", and so on.

The listboxes for the dropdowns do not have accessible names.
4.1.2: Name, Role, Value [2.0 A]04List-box
27
ADR_20580-45Password requirements tracker not programmatically determinedThis 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.

4.1.3: Status Messages [2.1 AA]03Input Field
28
ADR_20580-27Decorative icon not hidden from assistive technologyThis 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.

1.1.1: Non-text content [2.0 A]05, 06, 08Image
29
ADR_20580-14Unordered list not marked up semanticallyThis 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 tiles 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.

1.3.1: Info and Relationships [2.0 A]04, 05, 06List
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100