Accessibility at MOSION.
MOSION is building a mobile-first film platform and Studio workflow that should be usable by more people, in more contexts, on more devices. This page explains our current accessibility approach across mosion.app and studio.mosion.app.
- We treat accessibility as an ongoing product responsibility, not a one-time checklist.
- We review public pages, navigation, and key forms with readability, keyboard use, and responsive layouts in mind.
- If something blocks you, we want a direct report so it can be reviewed and fixed.
What this page covers
This page covers the public MOSION website, the public waitlist flow, the MOSION Studio landing page, and the Studio application flow. It does not guarantee that every future release is fully conformant with any specific accessibility standard, but it does state the direction and support path we are actively maintaining.
How we approach accessibility
We aim to keep navigation predictable, content readable, forms understandable, and core tasks operable across modern browsers and current mobile devices. Accessibility work is handled as part of ongoing design and implementation review, especially around structure, focus flow, interaction states, and mobile responsiveness.
Our target direction is practical alignment with modern accessibility expectations, including WCAG-style concerns such as contrast, keyboard access, zoom and reflow behaviour, semantic structure, and clear link and form labelling.
Current areas of support
- Responsive layouts that adapt across desktop and mobile breakpoints.
- Semantic headings, lists, buttons, links, and form fields across the public site and Studio application flow.
- Visible hover and focus-aware interaction styling on core navigation and form controls.
- Direct support channels by email when a task cannot be completed independently.
Where issues may still exist
MOSION is still evolving, and some interface areas may not yet meet the standard we want. Prototype previews, promotional media treatments, and newly released flows may require additional refinement for assistive-technology compatibility, focus order, motion tolerance, or descriptive labelling.
If you encounter an issue, we would rather hear about the exact blocker than hide behind a generic statement. Reports with device, browser, and task details are the fastest way to get a meaningful fix.
If you need help or another route
If a page, form, or control is difficult to use, contact us and describe what you were trying to do. We can review the issue and, where appropriate, help you complete the task through an alternative support path.
What to include in an accessibility report
- The page or feature you were using.
- The device, operating system, browser, and any assistive technology involved.
- The exact step that failed, and what you expected to happen instead.
- A screenshot or screen recording if you have one.
Accessibility contact points
For public-site accessibility questions, contact support@mosion.app.
For Studio accessibility questions, contact partners@mosion.app.