Pioneers in Remote Therapeutic Monitoring (RTM) Software for Physical Therapists

Learn How to Quickly and Easily Implement Remote Therapeutic Monitoring Into Your Practice

Learn How to Quickly and Easily Implement Remote Therapeutic Monitoring Into Your Practice

Accessibility

We’re committed to making MovementRx easy for everyone to use, regardless of ability, device, or context. Our goal is to provide a fast, consistent, and inclusive experience across our website and related web services.

Our Standards & Approach

  • WCAG 2.2 Level AA: We design and evaluate our site against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.
  • Apple Human Interface Guidelines (HIG): While this website does not use iOS native code, we align relevant HIG accessibility and usability principles (clarity, legibility, adequate target size, motion sensitivity) to guide patterns and interactions.
  • WAI‑ARIA (as needed): We use semantic HTML first, and apply ARIA roles, states, and properties only when native semantics are insufficient.
  • Continuous improvement: Accessibility is an ongoing effort integrated into our design reviews, code reviews, and release checklists.

What We Do

Structure & Semantics

  • Use proper headings, lists, tables with headers, and landmark regions for clear page structure.
  • Keep link text meaningful and avoid using color alone to convey information.

Color, Contrast, and Motion

  • Maintain color contrast ratios that meet AA targets.
  • Avoid relying on color alone; include icons, labels, or text.

Forms & Feedback

  • Provide explicit labels, instructions, and helpful error messages.
  • Identify required fields and input formats in advance.
  • Prevent data loss where feasible (e.g., confirm before destructive actions).

Images, Audio, and Video

  • Provide alternative text for meaningful images.
  • Avoid text embedded in images where possible; otherwise, provide equivalent text.
  • For time‑based media we aim to provide captions, transcripts, or audio descriptions, as appropriate.

Responsiveness & Zoom

  • Support content reflow and zoom to at least 200% without loss of functionality.
  • Ensure touch targets are reasonably sized and have adequate spacing.

Compatibility

  • Test with current versions of major browsers (Chromium‑based, Firefox, Safari, Edge) on desktop and mobile.
  • Validate with a range of assistive technologies (for example, screen readers and platform accessibility settings) to the extent feasible.

Third‑Party Content

Some features (e.g., video hosting, analytics, chat or checkout experiences) may be provided by third parties. We select vendors that prioritize accessibility and encourage them to meet WCAG 2.2 Level AA. Where we cannot control third‑party code, we provide workarounds or alternatives when possible.

Requesting Accommodations & Alternative Formats

If you need content in an alternative format (for example, a PDF converted to accessible HTML or plain text), or have trouble using any part of the site, contact us. We’ll respond and work with you to meet your needs.

Contact options

Testing & Governance

  • Design & Code Reviews: Accessibility checks are part of our definition of done.
  • Automated Checks: We run automated audits for common issues (contrast, landmarks, labels, names/roles/values).
  • Manual Testing: We verify keyboard paths, focus order, announcements, and error handling on representative pages and components.
  • Regression Prevention: Issues found are tracked and re‑checked in future releases.

Known Limitations (Dynamic)

We continuously test and improve accessibility across our website and related services. Because our accessibility backlog changes regularly, we don’t publish a static list of “known issues.” If you encounter any barrier, please tell us so we can investigate and prioritize a fix:

Third-party components. Some embedded services (e.g., media hosting, analytics, chat) are provided by third parties. Where we can’t fully control their code, we work with vendors to resolve issues or provide alternatives where feasible.

Formal Compliance & Laws

MovementRx strives to align with WCAG 2.2 Level AA and applicable accessibility laws and guidance in the regions we serve. Where specific technical standards are not mandated, we treat WCAG 2.2 Level AA as our internal benchmark for the web.

Statement Details

  • Responsible team: MovementRx Product & Engineering
  • Method of assessment: Self‑evaluation using WCAG 2.2 success criteria, automated tools, and manual testing with assistive tech
  • Date first published: October 21, 2025
  • Last updated: October 21, 2025

We’ll update this page as we release improvements or adopt new standards. Thank you for helping us build an accessible MovementRx for everyone.