Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
- Some interactive elements do not have accessible names, so people using assistive technologies may not understand their purpose. This fails WCAG 2.2 success criterion 1.1.1 (Non‑text Content).
- Some menus are not placed within landmark regions, making them harder for screen‑reader users to find. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
- Some elements are coded as lists even though they are not visually lists, which may confuse assistive technologies. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
- Some lists contain incorrect HTML structure, such as <ul> or <ol> elements that do not directly contain <li>, <script>, or <template> elements. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
- Some form fields use placeholder text instead of visible labels, so users may not understand the purpose of the field. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
- Breadcrumbs are not placed within a navigation landmark, making them harder to locate with assistive technologies. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
- The order of content does not always match the visual layout, which can make keyboard navigation confusing. This fails WCAG 2.2 success criterion 1.3.2 (Meaningful Sequence).
- Some links are not visually distinguishable from surrounding text, making them difficult to identify. This fails WCAG 2.2 success criterion 1.4.1 (Use of Colour).
- Some text and non‑text elements do not meet minimum colour‑contrast requirements, making them difficult to see. This fails WCAG 2.2 success criteria 1.4.3 and 1.4.11 (Contrast Minimum and Non‑text Contrast).
- Some images contain text, meaning users cannot adjust the text size or style. This fails WCAG 2.2 success criterion 1.4.5 (Images of Text).
- Some content does not reflow correctly at 400% zoom and may require two‑dimensional scrolling. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).
- Some interactive elements cannot be accessed using a keyboard. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard).
- The first interactive element on the page is not a “skip to main content” link, making it harder for keyboard and screen‑reader users to bypass repeated content. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks).
- Breadcrumbs, menus, and search functionality are not always placed within landmark regions, making them harder to find with assistive technologies. This fails WCAG 2.2 success criterion 2.4.1 (Bypass Blocks).
- Some links do not have discernible text, so their purpose is unclear. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose).
- Some interactive elements do not show a visible focus indicator, making it difficult for keyboard users to see where they are on the page. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).
- Some form elements do not include their visible label in their accessible name, which may confuse screen‑reader users. This fails WCAG 2.2 success criterion 2.5.3 (Label in Name).
- Some touch targets are smaller than the recommended minimum size, making them difficult to activate. This fails WCAG 2.2 success criterion 2.5.8 (Target Size Minimum).
- Some links that point to the same destination use different link text, which may confuse users. This fails WCAG 2.2 success criterion 3.2.4 (Consistent Identification).
- Some form labels are not visible or not clearly associated with their fields. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions).
- Some interactive elements do not have the correct role assigned in the code. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
- Some links do not have discernible text, so their purpose is unclear. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
- Some frames do not have accessible names, making their content difficult for screen‑reader users to identify. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
- Some form elements do not have labels, making them difficult to understand or complete. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
We are working with our supplier Productive Digital to remediate or mitigate the above non-compliances and expect these to be completed by [date of completion supplied by vendor].)
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.
Live video
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
3rd Party content
Third-party content that’s under someone else’s control that we didn’t pay for or develop.
What we’re doing to improve accessibility
The University of Manchester is committed to improving digital inclusion, ensuring that everyone has equitable access to information, technology, resources, and opportunities for learning and engagement, regardless of ability. We are undertaking a program of activity working with our Equality, Diversity, and Inclusion Division and Disability Advisory and Support Service to improve digital experiences for users with disabilities.
Preparation of this accessibility statement
This statement was prepared on 24.02.26
It was last reviewed on 13.02.26
This website was last tested on 13.02.26 against the WCAG 2.2 AA standard.
The test was carried out by manual, automated and keyboard testing. The most viewed pages were tested using automated testing tools by our website team. A further audit of the website was carried out to the WCAG 2.2 AA standard.
You can read the full accessibility test report here.
