Accessibility Statement

1. Our commitment

Learn Amp is committed to making our platform as inclusive and accessible as possible.

Our aim is to provide a delightful experience for all users. In order to do so, our first step is to make it accessible and usable. This means paying particular attention to ensuring we serve those who have special requirements or require assistive support.

We’re committed to:

ensuring our platform continually conforms with internationally recognised accessibility standards.
conducting regular accessibility audits.
being transparent about any exceptions and our plans to address them.
making continual improvements in a timely manner, alongside feature development.
listening to, and acting on, feedback from customers on how we can improve.

2. Our practices

Accessibility should never be an afterthought. To that end, we have processes in place that help us to ensure we uphold our commitment to building an accessible and inclusive platform.

Accessibility is baked into our product strategy as standard.
Our design personas include accessibility requirements.
Our accessibility standard is upheld across all system roles.
We run automated axe-core accessibility tests against WCAG 2.2 Level A and AA criteria across 100+ pages, with over 130 Cypress accessibility test scenarios.
We use an ESLint accessibility plugin for Vue.js components to catch issues during development.
Accessibility is a key requirement in any procurement process for customer-facing technology.
We provide accessibility training for our employees to encourage a culture of inclusion and awareness.

3. Platform compliance

Learn Amp is largely compliant with W3C's Web Content Accessibility Guidelines (WCAG) 2.2 Level A and Level AA. A description of known exceptions can be found in the next section.

Learn Amp also meets the following WCAG 2.2 Level AAA criteria where evidence supports compliance:

3.3.8 / 3.3.9 Accessible Authentication: No CAPTCHAs, cognitive tests, or puzzles are required at any point in the authentication flow. SSO and password managers are fully supported, and paste is not blocked on password fields.

Our platform includes the following accessibility features:

Keyboard navigation and focus management

Skip-to-content links on every page, allowing keyboard users to bypass repeated navigation.
Full keyboard operability for core workflows including navigation, forms, modals, and content browsing.
Focus traps in modal dialogs with escape key support, ensuring keyboard users can navigate in and out of overlays.
Visible focus indicators on interactive elements.

Screen reader support

ARIA attributes throughout the application: aria-label, aria-describedby, aria-live, aria-expanded, aria-hidden, and role attributes across Vue components and views.
Semantic HTML landmarks (nav, main, article, section) for screen reader navigation.
Visually hidden text (.sr-only) providing additional context for screen reader users.
Live regions (aria-live, role="alert", role="status") for dynamic content updates, notifications, and status messages.

Media accessibility

YouTube videos display closed captions by default, with auto-generated caption support enabled.
Contrast checking utilities built into the branding configuration to help customers maintain accessible colour choices.

Visual accessibility

Responsive design that reflows at all viewport widths, supporting text resizing up to 200%.
Dynamic language attribute on the page with RTL support for Arabic.
prefers-reduced-motion support to respect user animation preferences.

Authentication

No CAPTCHAs, puzzles, or cognitive function tests required for login, password reset, or any authentication flow.
Full SSO (OAuth2) support and compatibility with password managers.
Paste is not blocked on password fields.

4. Known Exceptions

In our efforts to improve the system, we must first identify the areas we need to improve then systematically resolve these. The following table describes known issues in our platform.

Exception	Commitment	Timeframe	Related WCAG Section
Drag-and-drop components (reordering lists, checklists, drawer resize) do not have keyboard-only alternatives.	We will add keyboard-based reordering (e.g. arrow keys or move-up/move-down buttons) as alternatives to drag-and-drop interactions.	2027	2.5.7 Dragging Movements
Some interactive elements have `outline: none` without a replacement focus indicator.	We will audit and replace all instances of `outline: none` with visible alternative focus styles.	Q3 2026	2.4.7 Focus Visible
Personal data input fields (name, email, address, phone) do not include `autocomplete` attributes.	We will add appropriate `autocomplete` attributes to all personal data fields to support browser autofill and assistive technologies.	Q3 2026	1.3.5 Identify Input Purpose
Some components trigger actions on pointer-down events rather than pointer-up/click.	We will migrate pointer-down triggered actions to click events or add undo mechanisms.	Q2 2026	2.5.2 Pointer Cancellation
Some extra-small and icon-only buttons may fall below the 24x24px minimum target size.	We will audit and increase the minimum size of interactive targets to meet the 24x24px threshold.	Q3 2026	2.5.8 Target Size (Minimum)

5. Exclusions

Although we make accessibility a requirement of our procurement process and provide tools to encourage creating accessible content, we cannot guarantee the accessibility of content added to Learn Amp (including integrations, libraries and user added content.)

6. Found an Accessibility Issue?

Please contact our team at product@learnamp.com.