Technical information about this website鈥檚 accessibility
乱伦大神 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.
The website is partially compliant with the AA standard, due to the the non-compliances and exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Issues with content
- headings on some of our pages do not appear in a logical order. This does not meet WCAG 2.2 success criterion 1.3.1 Info and Relationships
- some pages contain text that looks like a heading, but is not coded as a heading. This does not meet WCAG 2.2 success criterion 1.3.1 Info and Relationships
- some of our pages contain empty headings. This does not meet WCAG 2.2 success criterion 1.3.1 Info and Relationships
- some of our links do not make sense or are unhelpful when removed from the context of surrounding content. This does not meet WCAG 2.2 success criterion 2.4.4 Link Purpose (in context)
- some of our list items - <li> - do not have a <ul> or <ol> parent element. This does not meet WCAG 2.2 success criterion 1.3.1 Info and Relationships
- some lists are coded in a way that is based on presentation rather than function, so a single list may be separated into two and read as separate lists. This can be confusing for users of assistive technology and does not meet WCAG 2.2 success criterion 1.3.1 Info and Relationships
- some of our pages use colours which do not have high enough contrast between text and background. This does not meet WCAG 2.2 success criterion 1.4.3 Contrast (minimum)
- some of our ARIA attributes do not have valid values. This does not meet WCAG 2.2 success criterion 4.1.2 Name, Role, Value
- some of the pages on our website are intended for use as marketing materials to specific audiences, and are therefore not included in the navigation of the site. This does not meet WCAG 2.2 success criterion 2.4.5 Multiple Ways
- in some pages where more than one language is used, this cannot be programmatically determined. This does not meet WCAG 2.2 success criterion 3.1.2 Language of Parts
- on our Maps page, the Focus Order is not the same as the reading order and some of the fields are not focusable which does not meet WCAG 2.2 success criterion 2.4.3 Focus Order
Issues with images, video & audio
- some images do not have a text alternative, or have an inappropriate text alternative. This does not meet WCAG 2.2 success criterion 1.1.1 Non-text Content
- some <video> elements do not have captions. This does not meet WCAG 2.2 success criterion 1.2.2 Captions (pre-recorded)
- some videos which have additional visual content do not have audio descriptions or transcripts. This does not meet WCAG 2.2 success criteria 1.2.3 Audio Description or Media Alternative (Prerecorded) and 1.2.5 Audio Description (Prerecorded)
Issues with interactive tools & transactions
- some of the forms and interactive search pages on our website are not appropriately labelled or do not have labels. This does not meet WCAG 2.2 success criterion 3.3.2 Labels or Instructions
- some forms have labels which are not associated with the appropriate form fields, which does not meet WCAG 2.2 success criterion 1.3.1 Info and Relationships
- the labels used on buttons across the website are not always consistent, and some buttons which carry out the same function may have different text. This does not meet WCAG 2.2 success criterion 3.2.4 Consistent Identification
- some of our interactive elements such as tabs and accordions are not functional using a keyboard. This does not meet WCAG 2.2 success criterion 2.1.1 Keyboard
- for some of our interactive elements, there is no visible keyboard focus indicator, showing where you are on the page. This does not meet WCAG 2.2 success criterion 2.4.7 Focus visible
- some of our interactive elements such as tabs and accordions do not use appropriate mark-up to identify states. This does not meet WCAG 2.2 success criterion 4.1.2 Name, Role, Value
- some of our buttons and other interactive elements don鈥檛 have enough space between them. This does not meet WCAG 2.2 success criterion 2.5.8 Target Size (minimum)
- some of our tab elements with role="tablist" do not have child elements with role="tab" present. Some of our tab elements with role="tab" do not have a parent with role="tablist" present. This does not meet WCAG 2.2 success criterion 1.3.1 Info and Relationships
- some of our search pages and interactive elements do not utilise status messages to update screen readers of a change in state. This does not meet WCAG 2.2 success criterion 4.1.3 Status Messages
- some of our forms have labels which do not match the accessible name. This does not meet success criterion 2.5.3 Label in Name
PDFs & other documents
- Many of our older PDFs and Word documents don鈥檛 meet accessibility standards - for example, they may not be structured so they鈥檙e accessible to a screen reader. This doesn鈥檛 meet WCAG 2.2 success criterion 4.1.2 Name, Role, Value
Third-party content
Some of the functions on our website are provided by third-party suppliers, and we do not have direct control over the accessibility of these elements. We work with suppliers by raising accessibility issues and pushing for them to be resolved.
- the cookie pop-up on our website has colour contrast issues which do not meet WCAG 2.2 success criterion 1.4.3 Contrast (minimum) and on some pages the cookie notice may obscure content, which does not meet WCAG 2.2 success criterion 2.4.11 Focus Not Obscured (minimum)
- on our library pages, we display third party calendars showing opening hours and availability for resources. These calendars are not coded in a way that is useful to users of assistive technology which doesn鈥檛 meet WCAG 2.2 success criterion 4.1.2 Name, Role, Value, and have problems with focus order which does not meet WCAG 2.2 success criterion 2.4.3 Focus Order
- when using the Chatbot, keyboard users may not be able to navigate away. This does not meet WCAG 2.2 success criterion 2.1.2 No Keyboard Trap
- the button to open the Hotjar survey does not have an accessible name. This does not meet WCAG 2.2 success criterion 4.1.2 Name, Role, Value
How we aim to resolve these issues
We are taking a continuous improvement approach to improving accessibility, working through the issues identified in this statement. We are prioritising issues which have the highest impact on users. We have recently completed a two-year project to improve digital accessibility, during which we greatly reduced the number of instances of each of the points listed above.
Content that鈥檚 not within the scope of the accessibility regulations
PDFs & other documents
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they鈥檙e 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.
Maps
Maps are exempt from the accessibility regulations, but where we have a map on a page, we will provide other information in an accessible format, such as an address or directions.
Third-party content
Third-party content that鈥檚 under someone else鈥檚 control that we did not pay for is exempt from accessibility legislation. For example, we know that you cannot pause, stop or hide the Discover Uni widget included in our course pages, but we are required to display this and we have reported our accessibility concerns to the owner.