Accessibility Statement for Learning Pool LMS

Our approach to accessibility

Learning Pool considers accessibility throughout all phases of our product development cycle, from research and design through development and QA. We believe that designing to benefit people with disabilities creates products that better serve all users.

We work hard to meet level AA of the WCAG 2.2 standards through a combination of research, implementation techniques, tools, and testing. Our goal is to continuously improve and enhance the experience for all users. We build accessibility standards into all the components of our design system to deliver an inclusive experience across products.

Conformance status

While we are continuously working to improve the usability of our products, Learning Pool LMS is currently partially conformant with WCAG 2.2 level AA standards. This means that some parts of the platform do not fully conform to the accessibility standards.

Recent accessibility focused developments completed: 

• 1.3.1 Info and Relationships Level A & 2.4.6 Headings and Labels AA: 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.
• 2.1.1 Keyboard (Level A): Some functions on the Homepage were only available to mouse users using mouse hover, leaving keyboard users unable to view this.
• 2.4.3 Focus Order & 4.1.2 Name, Role, Value | Success Criterion 2.1.1 Keyboard (Level A): 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.

Added for WCAG 2.2:

• 2.4.11 Focus Not Obscured (AA): When the user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
• 2.5.7 Dragging Movements (AA): All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.
• 2.5.8 Target Size (Minimum) (AA): The size of the target for pointer inputs is at least 24 by 24 CSS pixels
• 3.2.6 Consistent Help (A): If a web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple web pages within a set of web pages, they occur in the same relative order to other page content, unless a change is initiated by the user.
• 3.3.7 Redundant Entry (A): Information previously entered by or provided to the user that is required to be entered again in the same process is either: auto-populated, or available for the user to select. Except when: re-entering the information is essential, the information is required to ensure the security of the content, or previously entered information is no longer valid.
• 3.3.8 Accessible Authentication (Minimum) (AA): A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least an a) An Alternative authentication method or b) A mechanism which is available to assist the user in completing the cognitive function test or c) an object recognition test is to recognize objects. Or (d) Personal Content to identify non-text content the user provided to the website.

Roadmapped accessibility focused developments:

• 1.3.1 Info and Relationships | How to Meet Info and Relationships (Level A): When viewing the homepage landmark types must be appropriate for its content.
• 1.3.1 Info and Relationships (Level A) & 2.4.6 Heading and Labels (Level AA): While viewing the catalogue page, Data Tables have been found without a summary or caption.
• 1.3.1 Info and Relationships (Level A): 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.
• 2.4.3 Focus Order (Level A): While viewing a collapsible topic course page and when the accordion is opened, it expands content above the current position.
• 1.3.1 Info and Relationships (Level A): While viewing a quiz activity, a heading has been added without any reason of structure or information.
• 1.3.1 Info and Relationships & 4.1.2 Name, Role, Value (Level A): While viewing a quiz activity, It was found that an aria tree element did not have an associated label.
• 4.1.1 Parsing (Level A): While viewing a questionnaire activity, Certain ARIA roles are ‘parental’ and needed ‘child’ elements to by correct in syntax.
• 3.2.2 On Input & 1.3.1 Info and Relationships (Level A): While viewing the questionnaire activity, when an element is activated, the page is updated without warning the user beforehand.
• 4.1.2 Name, Role, Value (Level A): 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.
• 3.2.2 On Input (Level A): 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.
• 1.3.1 Info and Relationships & 4.1.2 Name Role Value (Level A): When viewing the login page an error message was found with repeated text.
• 2.4.1 Bypass Blocks (Level A): When viewing the login page a skip to content link was found but did not move the navigational focus. Only the viewport was moved.
• 4.1.2 Name Role Value (Level A):  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.
• 2.4.7 Focus Visible & 1.4.11 Non Text Contrast (Level AA): 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.
• 2.4.6 Headings and Labels Level AA (Level AA): When viewing the course catalogue page, It was found that some labels were not descriptive of the field they are associated with.
• 3.2.3 Consistent Navigation & 3.2.4 Consistent Identification (Level AA): 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.

Preparation of this accessibility statement

Learning Pool’s Dedicated Design/UX Team conducts continuous audits and reviews (latest 04/25) along with QA testing for each release.

This page was last updated on the 19 June 2025.

Software used for audit purposes

• NVDA
• VoiceOver (MacOS and iOS)
• Native magnifier (built into OS)
• Voice Control for Mac or iOS (speech to text)
• Native OS features (high contrast mode)
• WAVE
• axe DevTools
• Google Lighthouse (built into Chrome Dev Tools)
• Color Contrast Analyzer
• Tab Order Visualizer ( Chrome Dev Tools)
• Accessibility Insights
• Hemingway Editor
• Mobile specific:
  
  • Accessibility Scanner (Android)
  • Xcode Accessibility Inspector (iOS)

VPAT

Learning Pool has undertaken a Voluntary Product Accessibility Template (VPAT) that is available upon request via hello@learningpool.com. The VPAT, can also be referred to as an Accessibility Conformance Report (ACR) and outlines the accessibility of Stream Learning Management System (LMS). (May 2022)

User feedback

We love to hear any accessibility-related feedback. If you have any trouble with Learning Pool LMS, please get in touch with us through any of the following options:

• Email us at support@learningpool.com
• Call us on +44 345 074 4114
• Get in touch at learningpool.com