Accessibility Statement

1. Our Commitment

MotionLab aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our target standard. WCAG 2.1 AA is internationally recognised as the benchmark for accessible web content and covers a wide range of recommendations to make web content more accessible to people with visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

We believe that every user — regardless of ability or the technology they use — should be able to access MotionLab's core features, including assessments, session tracking, and exercise instructions. Accessibility is not an afterthought in our development process; it is a core quality requirement that we evaluate with each new feature and release.

2. Measures We Have Taken

We have implemented the following accessibility measures across the MotionLab platform:

• Semantic HTML: we use appropriate HTML5 landmark elements (main, nav, header, footer, section) and heading hierarchies to ensure content is logically structured for screen readers and assistive technologies.
• Keyboard navigation: all interactive elements — including buttons, links, form inputs, and navigation menus — are fully operable using keyboard-only navigation. Tab order follows a logical sequence, and visible focus indicators are provided.
• Colour contrast ratios: we aim for a minimum contrast ratio of 4.5:1 for body text and 3:1 for large text and UI components, consistent with WCAG 2.1 AA requirements. Our dark theme has been designed with this in mind, using high-contrast whites and greens against dark backgrounds.
• Screen reader support: we use ARIA labels, roles, and descriptive alt text on images and icons to ensure content is interpretable by screen readers such as NVDA, JAWS, VoiceOver, and TalkBack.
• Large touch targets: interactive elements on mobile are sized to meet or exceed the recommended 44x44 CSS pixel minimum touch target size.
• Responsive design: the platform is designed to reflow gracefully at up to 400% zoom without loss of content or functionality.
• No reliance on colour alone: where colour is used to convey information (e.g. mobility score status), supplementary text or iconography is also provided.

3. Current Conformance Status

MotionLab is currently partially conformant with WCAG 2.1 Level AA. Partial conformance means that some parts of the content do not fully conform to the standard.

We conduct internal accessibility reviews as part of our development process and are actively working to close the gap towards full conformance. We have not yet commissioned a formal third-party WCAG audit, but intend to do so as the platform matures. We are committed to being transparent about our current limitations and our progress towards addressing them.

4. Known Limitations

The following known accessibility limitations exist in the current version of the platform. We are actively working to resolve each of them:

• Active session timer screen: the live countdown timer during guided sessions may present challenges for screen reader users. The current implementation updates frequently and may produce excessive announcements in some screen reader configurations. We are evaluating ARIA live region strategies and reduced-motion alternatives to improve this experience.
• Exercise video placeholders: where video demonstrations are planned, placeholder visuals are currently used. These are accompanied by text descriptions, but audio description tracks for video content have not yet been implemented.
• Complex charts and progress graphs: mobility score history graphs may not be fully interpretable via screen readers. We are working to add accessible table alternatives and ARIA descriptions for all data visualisations.
• Mobile application (Android): the Android application is in active development. TalkBack support is being built in from the start, but full conformance has not yet been verified.

5. Technical Specifications

The MotionLab web platform relies on the following technologies for its accessibility implementation:

• HTML5 (semantic elements and ARIA integration)
• WAI-ARIA 1.1 (roles, states, and properties for dynamic content)
• CSS (responsive layout, focus management, motion preferences)
• JavaScript / React (client-side interactivity, focus management, and dynamic content updates)

We test the platform using the following assistive technologies and tools: NVDA with Firefox, VoiceOver with Safari on macOS, TalkBack on Android, keyboard-only navigation across Chrome and Firefox, and automated accessibility scanning tools as part of our development workflow.

6. Feedback & Contact

We welcome feedback on the accessibility of MotionLab. If you encounter any barriers, experience difficulty accessing any part of the platform, or have suggestions for how we can improve accessibility, please contact us:

Email: support@motion-lab.io

Please include a description of the specific barrier you encountered, the assistive technology or browser you are using, and the URL or section of the platform where the issue occurred. We aim to respond to all accessibility feedback within 5 business days, and to provide a substantive update on the issue within 30 days.

7. Formal Complaints

If you are not satisfied with our response to an accessibility concern, you have the right to escalate your complaint. We ask that you first allow us a reasonable opportunity to resolve the issue directly, as described in Section 6.

If the matter remains unresolved after 30 days of raising it with us, you may wish to contact the relevant enforcement or supervisory body in your jurisdiction. In the United Kingdom, the Equality and Human Rights Commission (EHRC) oversees accessibility obligations under the Equality Act 2010. In the European Union, the European Accessibility Act and local implementing legislation may provide further avenues for redress.

We take all accessibility complaints seriously and will document, investigate, and respond to formal complaints in a timely and transparent manner.