Accessibility Statement for Learning Pool LMS

As the provider of the Learning Pool LMS, we are committed to providing a platform that is accessible to the widest possible audience.

We want everyone who uses the LP LMS to find the experience rewarding. In support of this vision, we strive to make the LP LMS as accessible as possible to users whatever their level of ability. A guide to achieving this we use the Web Content Accessibility Guidelines (WCAG) 2.1. Our ultimate goal is for the LP LMS to meet Level AA standards, WCAG’s recommended level of conformance for entire sites.

Technical information about the Learning Pool Learning Management Systems accessibility

Learning Pool is committed to making its Learning Management System accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance Status

The Learning Pool Learning Management System is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard. While core areas of the platform are conformant with the WCAG 2.1 standard, we still have work to do. We are investing significantly in further development to bring more areas of the platform to the AA standard with our 3rd party testing organization, the Digital Accessibility Centre

As we grow the platform this will be a continuous focus for us to ensure that the LMS is as compliant with the standard as possible.

Non-accessible content

LPLMS-4874: Success Criterion 4.1.2 Name, Role, Value – Understanding Name, Role, Value | How to Meet Name, Role, Value (Level A):
When using a keyboard on the landing page, users can use the tab key to navigate to elements that are disabled making them seem functional. These items slow down the progression of the page and can cause confusion.

We plan to ensure that disabled options do not take focus. One option we will explore will be to add an attribute of ‘disabled’ to the button, and check via JavaScript if the calling element has this attribute; if it does then to not perform the function.

Released on 30.05.2022. Version: learningpool-12.34.35

LPLMS-4873: Success Criterion 1.3.1 Info and Relationships – Understanding Info and Relationships | How to Meet Info and Relationships (Level A): -Estimated June 2024
When navigating the login page, Multiple top-level headings were found. A page should only have a single <h1> to ensure that screen reader users understand which heading defines the page.

We plan to ensure that there is one (and only one) level-one heading with a hierarchical structure of sub-headings as needed from h2 to h6.

LPLMS-4879: Success Criterion 1.3.1 & 2.4.4 Info and Relationships – Understanding Info and Relationships | How to Meet Info and Relationships | Understanding Link Purpose (In Context) | How to Meet Link Purpose (In Context) (Level A): – Resolved 23/11/2022
Disabled content was found during the audit process that did not advise users if it was disabled and non-functioning.

As this is a pseudo-element, the attribute disabled may not work, so we plan to use the attribute aria-disabled=”true” in its place.

LPLMS-4880: Success Criterion 1.3.1 (Level A) Info and Relationships & 3.2.3 Consistent Navigation (Level AA):

When viewing the landing page it was identified that the tooltip information for “Support via web”, “Support via e-mail” and “Support by phone” are not offered to screen reader users..

We plan to ensure that the informational content is contained within the HTML, and not displayed via CSS.

Fixed by LPLMS-4880. Released on 22.08.2022. Version: 12.42.5

LPLMS-4881: Success Criterion Success Criterion 2.1.1 Keyboard & 2.4.3 Focus Order (Level A):

LPLMS-4882: Success Criterion 1.3.1 Info and Relationships | How to Meet Info and Relationships (Level A): Estimated June 2024

When viewing the homepage landmark types must be appropriate for its content. A landmark element was used, but the mark-up of which did not conform to the list specified by W3C. These landmarks could be very confusing for screen reader users.

We plan to ensure the element has been used inappropriately. The element should be used to display information linked to the website, but not to the page. e.g. Other sections on the site, search facilities or promotions.

LPLMS-4884: Success Criterion 1.3.1 Info and Relationships & 2.4.1 Bypass Blocks (Level A): Estimated June 2024
When viewing some pages there was a visually hidden top-level heading with the same text content. This makes it difficult for screen reader users to find the start of the main content using heading navigation and stops them from easily working out the content of the page.

We will ensure that the structure of the pages on the site have the correct hierarchical structure.

LPLMS-4892: Success Criterion 1.3.1 Infor and Relationships (Level A): Estimated June 2024
When viewing the Homepage, content that would be considered “main content” was not found in the main landmark. If navigating via landmarks, screen reader users would miss this important information.

We will ensure that the structure of the pages on the site have the correct hierarchical structure and that all primary content are contained within the element (or inside the element with the role=”main”)

LPLMS-4893: Success Criterion 2.1.1 Keyboard (Level A): – Estimated June 2024
Some functions on the Homepage were only available to mouse users using mouse hover, leaving keyboard users unable to view this.

We will aim to ensure the menus open on keyboard focus as they do with mouse hover.

LPLMS-4894: Success Criterion 2.4.3 Focus Order & 4.1.2 Name, Role, Value | Success Criterion 2.1.1 Keyboard (Level A): – Estimated June 2024
Keyboard users can use the tab key to navigate to elements that are not visible on the menu located on the homepage. These items slow down the progression of the page and could cause users to lose the focus.

We will aim to ensure that when the menu is closed to add a CSS declaration of “display: none;” to ensure it is not visible by any user.

LPLMS-4904: Success Criterion 1.3.1 Info and Relationships (Level A) & 2.4.6 Heading and Labels (Level AA): – Estimated June 2024
While viewing the catalogue page, Data Tables have been found without a summary or caption. It is not possible for screen reader users to determine the tables contents without traversing it.

We will aim to add a caption element that describes the table as the first child of the table.

LPLMS-4906: Success Criterion 1.3.1 Info and Relationships Level A & 2.4.6 Headings and Labels AA: – Estimated June 2024
While viewing the catalogue page, it was found that some tables displayed column headers that had added and confusing text, which stops screen reader users from determining the purpose of the column.

We will aim to have the instructions for the use of the links put inside (as a child of) an absolute hidden area (hidden with the CSS declaration “display none;”). These instructions can be referenced using aria-described by so that it is read out when the link is in focus, but not when traversing the table.

LPLMS-4907: Success Criterion 1.3.1 Info and Relationships (Level A): – Estimated June 2024
While viewing the Homepage, at certain viewport sizes, when the breadcrumb is enabled the layout does not show correctly and may be missing parts visually.

We will ensure that there is an option to change the background to transparent so it does not cover the menus.

LPLMS-4908: Success Criterion 2.4.3 Focus Order (Level A): – Estimated June 2024
While viewing a collapsible topic course page and when the accordion is opened, it expands content above the current position. Whilst for visual users, this can be seen, screen reader users may not know there is anything “above” where they activated the element..

We will aim to have the expanding content appear below the activating element.

LPLMS-4913: Success Criterion 1.3.1 Info and Relationships (Level A): – Estimated June 2024
While viewing a quiz activity, a heading has been added without any reason of structure or information. This protracts the navigation for screen readers users and can cause confusion

If possible we will correct h1 of the page, but if not, we will remove as it serves no purpose.

LPLMS-4914: Success Criterion 1.3.1 Info and Relationships & 4.1.2 Name, Role, Value (Level A): – Estimated June 2024
While viewing a quiz activity, It was found that an aria tree element did not have an associated label. Screen reading software use the labels to read the name of the widget

We will ensure that this is labelled appropriately and aim to do this by using an already established header by the use of aria-labelledby=”instance-9-header”.

LPLMS-4915: Success Criterion 4.1.1 Parsing (Level A): – Estimated June 2024
While viewing a questionnaire activity, Certain ARIA roles are ‘parental’ and needed ‘child’ elements to bycorrect in syntax.

We will aim to ensure elements with an ARIA role that require child roles contain them.

LPLMS-4916: Success Criterion 3.2.2 On Input & 1.3.1 Info and Relationships (Level A): – Estimated June 2024
While viewing the questionnaire activity, when an element is activated, the page is updated without warning the user beforehand. This can be confusing for some users, especially for screen reader users.

Will will aim to ensure that the focus is not moved by only changing any input element.

LPLMS-4918: Success Criterion 4.1.2 Name, Role, Value (Level A): – Estimated June 2024
When navigating the course catalogue, Pseudo buttons must be marked up correctly to allow keyboard and screen readers users to interact with the element on the page.

Will will aim to add text to the icon, this can be visually hidden using the already established “sr-only” class. Will will aim to add an attribute of aria-expanded so screen reader users can tell the status of the button. This will need to be updated via JavaScript when activated.

LPLMS-4921: Success Criterion 3.2.2 On Input (Level A): – Estimated June 2024
When navigating to a course, when clicking on enrol, when the button is pressed, instead of activating the button, it submits the form that encapsulates it.

We will aim to ensure that all active elements operate as expected.

LPLMS-4930: Success Criterion 1.3.1 Info and Relationships & 4.1.2 Name Role Value (Level A): – Estimated June 2024

When viewing the login page an error message was found with repeated text. One of the repeated segments was encoded as a link that did not do anything.

We will aim to remove the link and its text from the alert element.

LPLMS-4931: Success Criterion 2.4.1 Bypass Blocks (Level A): – Estimated June 2024
When viewing the login page a skip to content link was found but did not move the navigational focus. Only the viewport was moved. This leaves keyboard and screen reader users unable to use the functionality.

We will aim to have the tabindex attribute added from page load.

LPLMS-4932: Success Criterion 2.4.1 Bypass Blocks (Level A): – Estimated June 2024
When viewing the homepage it was found that there was not a “Skip to content” link as the first interactive element. Keyboard users utilise this link to bypass navigation and jump straight to the content avoiding the repeated content on all pages.

We will aim to have the tabindex attribute added from page load.

LPLMS-4969: Success Criterion 4.1.2 Name Role Value (Level A): -Estimated June 2024
When viewing the homepage it was found that expandable elements must be marked up correctly to allow keyboard and screen readers users to interact with the element on the page.

We will aim to encapsulate the links and button properties & text into one element (be it a link or button) that shares the properties.

LPLMS-4971: Success Criterion 2.4.3 Focus Order (Level A): – Estimated June 2024
When viewing the required learning page, Keyboard users rely on a logical tab order (left to right, top to bottom) to determine where the focus is going to travel to next. The tab order does not follow a logical order, going from the header to the right-hand side before going to the left-hand side.

We believe that this issue is caused by the DOM order, which is not the same as the visual order, due to CSS. We will aim to ensure that the visual and semantic order of page are equivalent.

LPLMS-4972: Success Criterion 2.4.7 Focus Visible & 1.4.11 Non Text Contrast (Level AA): – Estimated June 2024
When navigating the home page some items navigated to via the tab key on the keyboard do not have contrasted highlighting to advise keyboard users what they can interact with. The items that do have a highlight do not have a very distinct one that is sometimes too hard for low vision users to determine.

We will ensure that the colour of the focus indicator is sufficiently contrasted (with a ratio of at least 3.1)

LPLMS-4973 Success Criterion 2.4.6 Headings and Labels Level AA (Level AA): – Estimated June 2024
When viewing the course catalogue page, It was found that some labels were not descriptive of the field they are associated with. Screen reader user rely on accurate descriptions to determine what needs to be entered

We will move the tooltip to outside of the legend, so it is not read to screen reader users when viewed out of context.

LPLMS-4975 Success Criterion – 3.2.3 Consistent Navigation & 3.2.4 Consistent Identification (Level AA): – Estimated June 2024
When viewing a course page with collapsible topics some functions were only available to keyboard users, as the element did not respond to mouse hover or click.

We will aim to ensure that the click event works for users.

Let us know what you think

If you continue to enjoy using the LP LMS, or if you had trouble with any part of it, please get in touch. We’d like to hear from you in any of the following ways:

• email us at [email protected]
• call us on +44 345 074 4114
• get in touch at learningpool.com

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).

Preparation of this accessibility statement

This statement was prepared on 26/05/2022 when it was first published. It was last reviewed on 19/04/2023.

The testing was based around a learner journey, which targeted the login page, web pages, dashboards, course catalogue and course pages.