This accessibility statement applies to Southampton Solent University LibGuides (https://mypc.solent.ac.uk).
This website is run by Southampton Solent University. We want as many people as possible to be able to use this website. That means you should be able to:
- change colours and contrast levels using browser or device settings
- zoom in up to 400% on desktops without the text spilling off the screen
- navigate most of the website using a keyboard
- listen to the website using a screen reader (including the most recent versions of Narrator, NVDA, and VoiceOver)
AbilityNet has advice on making your device easier to use if you have a disability.
How accessible this website is
We know that some parts of this website are not fully accessible:
- The booking grid, which serves as the main booking interface for most users, is not accessible, as it is too complex to navigate via a screen reader and keyboard. The mobile interface offers an alternative way to make a booking.
- The sign in screen is not fully accessible. Note in particular that it is not possible to tab to the sign in button, though it can be activated by hitting the Return key when the focus is on the password field (i.e., you type your password, then hit return). There are further problems with the coding of this page, including that the title and language of the page are not coded, feedback on form errors is not automatically read out, and the purpose of certain fields is not properly identified. It is not possible to zoom on the sign in page when using a mobile phone.
Feedback and contact information
If you find any problems not listed on this page or think we're not meeting accessibility requirements, contact: library.loans@solent.ac.uk. Alternatively, you may go direct to James Clark, Library Systems and Discovery Manager, email: james.clark@solent.ac.uk, telephone via the library main desk: 023 8201 3681.
If you need information on this website in a different format like accessible PDF, large print, audio recording etc.:
We'll consider your request and get back to you within 5 working days.
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
Southampton Solent University 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
This 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-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
- On the sign-in page, the username field is not properly coded so that it can be programmatically identified and completed via autocomplete functions. This means that the username needs to be remembered and typed by users. This fails WCAG 1.3.5 Identify Input Purpose (AA) and subsequently 3.3.8 Accessible Authentication (Minimum) (AA). We have reported this problem to ITS (the system vendor). We do not currently have a date by which this will be fixed.
- On the sign-in page, resizing of text is disabled for mobile devices. This means that users cannot make all or part of the screen larger according to their needs. This fails WCAG 1.4.4 Resize Text (AA). We have reported this problem to ITS (the system vendor). We do not currently have a date by which this will be fixed.
- The sign in page does not have a title element. This makes it more difficult for the user to perceive on which page they are on; screen readers will sometimes read the page URL instead. This fails WCAG 2.4.2 Page Titled (A). We have reported this problem to ITS (the system vendor). We do not currently have a date by which this will be fixed.
- On the sign-in page, the sign in button is under focus jointly with the password form field, but has not visible focus itself. This means that a user needs to know to hit the Return key after filling the password field rather than attempt to tab to the Sign in button. This fails WCAG 2.4.7 Focus Visible (AA). We have reported this problem to ITS (the system vendor). We do not currently have a date by which this will be fixed.
- The sign-in page does not have a language element. This means that the user relies on screen readers automatically recognising the language of the page, or relying on defaults, to have it read properly. This fails WCAG 3.1.1 Language of Page (A) and consequently 3.1.2 Language of Parts (AA). We have reported this problem to ITS (the system vendor). We do not currently have a date by which this will be fixed.
- On the sign-in page, the name and role of the three form fields (Language, Username, and Password) cannot be programmatically determined. This means that screen readers may not be able to read aloud correct information to the user, though most readers will read the placeholder in the Username and Password fields. This fails WCAG 4.1.2 Name, Role, Value (A). We have reported this problem to ITS (the system vendor). We do not currently have a date by which this will be fixed.
- On the sign-in page, the error message that is displayed when a field is left blank cannot be programmatically identified as a status message. This means that is not read by common screen readers. This fails WCAG 4.1.3 Status Messages (AA). We have reported this problem to ITS (the system vendor). We do not currently have a date by which this will be fixed.
Disproportionate burden
We are not making any disproportionate burden claims at this time.
Content that's not within the scope of the accessibility regulations
This website has no content that is not within the scope of the regulations at this time.
What we're doing to improve accessibility
We have made customizations to the log-in page so that all elements can be accessed via keyboard and screen reader. We raise issues with our vendor where appropriate. We raised the issue of insufficient colour contrast on the mobile system, and were told that a solution to this was in testing. We expect to have a more accessible version of the mobile system in place by July 2022.
Preparation of this accessibility statement
This statement was prepared on 21st September 2020. It was last reviewed and revised on 2nd October 2024.
The last test of this website was completed on 2nd October 2024.
The test was carried out internally. The full processes for booking and managing bookings via the mobile (accessible) view was tested using automated testing tools and a full audit of these processes was carried out to the WCAG 2.2 AA standard. The mobile view represents an accessible alternative to the main booking grid, and so the grid view was excluded from testing.
