This accessibility statement applies to the University of Westminster’s implementation of the Learnwise Liby AI chatbot, the chatbot is a standalone widget, but is currently implemented on Libguides.
This website is run by The University of Westminster. We want as many people as possible to be able to use this website.
We’ve also made the website text as simple as possible to understand.
My Computer My Way has advice on making your device easier to use if you have a disability and the AT Hive can help you find assistive technologies that work for you.
How accessible this website is
We know some parts of this website are not fully accessible. You can see a full list of any issues we currently know about in the Non-accessible content section of this statement.
Feedback and contact information
If you need information on this website in a different format such as accessible PDF, large print, easy read, audio recording or braille, or if you find any problems not listed on this page or think we’re not meeting accessibility requirements, email [email protected] for information on how to report an accessibility problem and request alternative formats.
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
The University of Westminster 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.
This application is not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. Due to the non-compliances listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
- Programmatic relationships for expandable content, related items such are rich text responses, and questions are not related to answers. The primary heading "Liby" appears as a heading and should be a heading but is not marked up as such. This fails WCAG 1.3.1 Info and Relationships (A).
- Whilst the widget generally reads in that correct sequence, that sequence is not programmatically determinable, as there is no relationship between an answer and a question, so a user navigating with cursor keys and a screen reader would be forced into a situation where they have to put in additional effort to make sense of the answers and determine which questions they belong to. This fails WCAG 1.3.2 Meaningful Sequence (A).
- Visually chat questions and answers are styled in a way which makes it clear which is which. Questions appear in a dark green speech bubble, positioned to the right of the widget, whilst answers do not appear in a bubble and occupy the full width of the widget, this understanding is only possible for sighted users. There may be situations where users of screen readers would want to quickly find items in their chat history and due to the lack of logical markup, this would not be an easy task. This fails WCAG 1.3.3 Sensory Characteristics (A).
- On Samsung Internet and Chrome, on an Android device, the chat button ;only works in landscape orientation. This fails WCAG 1.3.4 Orientation (AA).
- The chat button does not expand the chat window at a simulated screen width of 320px, it does not work on an iPad with Safari, and it does not work with Chrome, Firefox or Samsung Internet on Android. This fails WCAG 1.4.10 Reflow (AA).
- The chat button can be moved across the screen, presumably so a user can ask questions about a particular piece of content they seek clarity on, and need to prevent the chat window obscuring content. The moving can only be achieved with long press on mobile, right click on desktop, or a dragging action using left pressed mouse button with and releasing the button once reaching the desired location. No keyboard equivalent was detected. This fails WCAG 2.1.1 Keyboard (A).
- The responses use a fluid-like typing effect, which in essence is text being animated into view, using a combination of CSS and JS. The responses can often take significantly longer than five seconds to be wholly presented to the user, and there is no way to turn this animation off. This fails WCAG 2.2.2 Pause, Stop, Hide (A).
- The chat widget contains an iFrame, the iFrame lacks a title attribute. This fails WCAG 2.4.1 Bypass Blocks (A).
- Multiple non-interactive elements have tabindex attributes present, adding them into the widget's focus order. Opening the chat history does not move focus or set logical focus on to the first interactive element of the new panel, or the panel itself. This fails WCAG 2.4.3 Focus Order (A).
- At some viewports or zoom levels the chat wholly obscures focused items, it does not auto-close when focus leaves it and there is no standard exit mechanism present, such as pressing Esc, whilst focus is elsewhere on the page, a user would need to tab back to the element to close it. This fails WCAG 2.4.11 Focus Not Obscured (Minimum) (AA).
- The visible label for the chat button is 'Liby', whilst the accessible name is 'LearnWise Support Button', which does not match. This fails WCAG2.5.3 Label in Name (A).
- There is limited use of correct roles, states or properties across most elements of the widget, which would make understanding what interacting with controls is likely to do unclear to users of assistive technologies. It would also be impossible to determine the state of controls, particularly those that disclose additional content of controls. This fails WCAG 4.1.2 Name, Role, Value (A).
- Nothing is announced automatically when a question is asked, a user of a screen reader would need to go off searching for the answer, there is not even a sound to indicate something may have happened. This fails WCAG 4.1.3 Status Messages (AA).
We will provide the Learnwise team with a copy of the audit and determine their steps for making the application accessible. We will update this statement in due course.
If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Feedback and contact information’ section of this statement.
Disproportionate burden
At this time, we have not made any disproportionate burden claims.
Content that’s not within the scope of the accessibility regulations
At this time, we have not identified any content that is not within scope of the accessibility regulations.
Preparation of this accessibility statement
This statement was prepared on 11 July 2025. It was last reviewed on 11 July 2025.
Testing was last carried out on 11 July 2025 against the WCAG 2.2 AA standard. The test was carried out internally by the University of Westminster Digital Accessibility Team, using a combination of manual techniques, automated and semi-automated tools, and testing with a range of devices, browsers, operating systems and assistive technologies.