This accessibility statement is for the LSBU Library, Skills and Customer Service website hosted on LibGuides by SpringShare.
It specifically covers published pages using the domain library.lsbu.ac.uk/ including the platforms used to provide services such as room and event bookings and service requests: lsbu-uk.libcal.com and lsbu-uk.libwizard.com
Other sites that are linked to from this domain are not covered by this statement. Visit LSBU Accessibility Statement for its main website and Moodle.
Links to external websites and platforms’ Accessibility Statements can be found in the Third-Party Suppliers Accessibility Statements tab above. We have also produced a LibGuide on ebook accessibility.
Not all our third-party suppliers currently have accessibility statements in place. However, we are working with the library community and Searchbox to encourage third party suppliers to publish accessibility statements for users.
These details will be added to the Third Party Suppliers Accessibility Statements tab, as they are made available. If you require accessible content from one of our third-party suppliers, please email: library@lsbu.ac.uk
We have listed any accessibility and assistive technology compatibility issues found during testing, in this statement. If you find an issue that has not already been identified, please contact us
We want as many people as possible to be able to use this website in a way that suits them. You should be able to:
We have also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
You can also find information and accessibility tips directly from your device brand: Android, Apple Mac OS, Windows
You can adjust the accessibility settings in your web browser so webpages are displayed in a way that better suits your individual needs. For tips on how to change your web browser settings, select your chosen browser to link through to their support pages:
Our colleagues at Kent University have put together a comprehensive selection of productivity tools that support accessibility that you may find helpful. Please note this software has not been tested and is not supported by LSBU.
We know some parts of this website are not fully accessible:
If you need information on this website in an accessible format please: email: library@lsbu.ac.uk
We will consider your request and get back to you in one week.
We are always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we are not meeting accessibility requirements, please email: library@lsbu.ac.uk letting us know the details so we can investigate.
We will respond to your email within one week and let you know what we are doing to address the issue you have raised.
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 are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Find out how to contact us Please check our help desk opening hours if you are planning to visit in person.
London South Bank University is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.
The content listed below is non-accessible for the following reasons.
Keyboard users may struggle to navigate events and training hosted on LibCal as there are keyboard traps in the dropdown menu used in some advertised events. This fails WCAG 2.1 success criterion 2.1.2 (keyboard trap). If you require support booking an event or workshop please email askalibrarian@lsbu.ac.uk
The areas of non-compliance listed below affect a number of webpages and so the information below details the non-compliance rather than the specific webpage or content.
Some images do not have a text alternative, or the text alternative does not correctly describe the image so people using a screen reader either, cannot access the information or the information provided is unhelpful. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
Some images used as links are missing text alternative. Text alternative should describe the purpose of the link so people using screen readers can access the information. This fails WCAG 2.1. success criterion 1.1.1 (non-text content).
Some images are missing an alternative attribute. This should be used to specify a short text alternative so people using screen readers can access the information. This fails WCAG 2.1. success criterion 1.1.1 (non-text content).
We plan to add text alternatives for all images by the end of the third quarter of 2021, 30/09/2021. We will sure our use of images meets accessibility standards when we publish new content.
Some accessible names do not contain visible label text. Visible label text helps people who use screen readers or speech input to navigate a website providing them with a better experience. This fails WCAG 2.1 success criterion 2.5.3 (label in name).
We will make sure our use of accessible names meets the accessibility standards as we publish new content.
Some links only have image elements and are missing alternative text. The alternative text should describe the purpose of the link so people using screen readers can access the information. This fails WCAG 2.1 success criterion 1.1.1 (non-text content).
Some image elements are missing alternative attributes. An alternative attribute should be used to specify a short text alternative so people using screen readers can access the information. This fails WCAG 2.1 success criterion 1.1.1. (non-text content).
We will make sure our use of links and alternative attributes meet the accessibility standards as we publish new content.
Some form fields are not labelled. This means people using screen readers will not understand if it is a required field or not. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
We will make sure our use of form fields meets the accessibility standards as we publish new content.
Tables containing caption elements have been used to structure content making it confusing, for people who use screen readers. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
We will make sure our use of tables to structure content meets the accessibility standards as we publish new content.
There are some heading tags with no content. Text not intended as a heading should not be marked up with heading tags as this makes it confusing for people using screen readers. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
We will make sure our use of heading tags meets the accessibility standards as we publish new content.
Some of the align attributes are not supported by HTML5 and the presentational mark-up used is now obsolete in HTML5. These issues make it difficult for people using screen readers. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
We will make sure our use of align attributes and presentational mark-ups meets the accessibility standards as we publish new content.
The heading structures used on this website are not logically nested. This makes it difficult for people using screen readers to follow the information presented. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships).
We will make sure our use of heading structures meets the accessibility standards as we publish new content.
The iframe element requires a non-empty title attribute that identifies the frame. This fails WCAG 2.1 success criterion 2.4.1 (bypass block).
We will make sure our use of accessible names meets the accessibility standards as we publish new content.
Several links do not contain meaningful text making it difficult for people using screen readers to determine the purpose of the link. This fails WCAG 2.1 success criterion 2.4.4 (link purpose – in context).
We will make sure our use of images meets accessibility standards as we publish new content.
Headings and labels are missing from some content making it difficult for people using screen readers to navigate the webpages. This fails WCAG 2.1 success criterion 2.4.6 (headings and labels).
We will make sure our use of headings and labels meets the accessibility standards as we publish new content.
When a keyboard user navigates the webpages, there is no indication of keyboard focus. This makes it difficult for keyboard users to know where the focus is on the webpage. This fails WCAG 2.1 Success criterion 2.4.7 (focus visible).
We will make sure our use of keyboard focus functionality meets the accessibility standards as we publish new content.
Several pages have duplicate ID attributes. Duplicate ID attributes are known to cause problems for screen readers. This fails WCAG 2.1 success criterion 4.1.1 (parsing).
We will make sure our use of ID attributes meets the accessibility standards as we publish new content.
Some anchor elements are missing valid links. Text input, checkbox input and select elements on some pages do not have a name available to an accessibility API. This prevents assistive technologies such as screen readers understanding where the focus is. This fails WCAG 2.1 success criterion 4.1.2 (name role value).
We will make sure our use of heading structures meets the accessibility standards as we publish new content.
Some of our interactive forms are difficult to navigate using a keyboard because, for example, some form controls are missing a ‘label’ tag.
Several of our forms are built and hosted through third party software and ‘skinned’ to look like our website.
This includes our online payment forms for adding print credit or paying for printing and binding online services. You can top up your print credit and pay for these services at our help desks if you are unable to do so online.
We have assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they are not essential to providing our services. For example, we do not plan to fix obsolete help sheets.
Any new PDFs or Word documents we publish will meet accessibility standards.
We are actively improving the accessibility of this site by addressing known issues that have been identified in the initial audits of the site. The audit process will continue so all webpages are in this site: library.lsbu.ac.uk/ are reviewed for their accessibility.
Library and Learning Resources will adopt the approach of universal design, to ensure that new content is created with accessibility at the centre of the design process.
This statement was first published on 22 September 2020. It was last updated on 3 February 2025.
This website was last tested on 12 May 2023. The testing was carried out by an internal Library and Learning Resources team.
For details on the approach used to decide on a sample of pages to test please visit our LibGuide Audit Strategy
