Skip to main content

Accessibility of Remotion products

This page documents how Remotion's products (Remotion Player, Remotion Studio, Remotion Editor Starter, and others) meet accessibility standards. This is a common question we get from enterprises who need to ensure their suppliers meet accessibility standards.

This page is about product accessibility, not website conformance. For a statement about the accessibility of our websites, see:

Remotion Player​

The Remotion Player is the component that most users will embed into their page if they are working on a Remotion app.
Based on our latest internal review against WCAG 2.1 AA, the Player:

  • Has play, pause, mute, and fullscreen buttons that are keyboard-operable, carry accessible names, and show a visible focus indicator.
  • Does not yet expose the seek bar and volume slider as keyboard-operable sliders with an accessible role, name, and value.
  • Does not yet expose the mute button's pressed state, or the time display, to assistive technology.
  • Renders composition content to real DOM elements, so text content remains readable by screen readers.

We consider the Remotion Player to partially support modern accessibility standards, and we are working through the remaining gaps above.

Editor Starter​

Out of the box, we try to follow these best practices:

  • Keyboard navigation is possible
  • Clear focus indicators
  • Buttons have appropriate labels
  • Contrast ratios are sufficient

The Editor Starter is a template whose code is being adopted into customer code bases.
It therefore becomes the responsibility of the customer to ensure that the Editor Starter meets their desired accessibility standards.

Remotion Studio​

The Remotion Studio is not considered a product for end-users, but a helper tool for developers.
We are not giving any guarantees on its accessibility. Our latest internal review against WCAG 2.1 AA found several open issues, including:

  • The composition search dialog and the "Render via CLI" dialog do not trap keyboard focus, so it can escape to the page behind them.
  • The composition search input relies on a placeholder instead of a persistent, programmatically associated label, and some elements inside the search dialog cannot be reached by keyboard alone.
  • Status messages such as "Copied command!" are not announced to screen readers, and the search placeholder text does not meet the 4.5:1 contrast requirement.

We are addressing these issues over time.

Other products​

Do not expose any user interfaces and are therefore not subject to accessibility concerns.

User code​

Remotion runs code provided by the customer and cannot guarantee that the code meets accessibility standards.

Templates​

Are not part of the core Remotion framework and explicitly excluded from this accessibility statement.
If using a template, users must ensure themselves that the code they adopt meets their desired accessibility standards.

Reporting an accessibility issue​

You may file an issue to report an accessibility issue.
We will do our best to address any issues you report.

Customers eligible for prioritized support may also report issues through the channels set up for them.

Certifications​

Remotion does not currently hold any accessibility certifications.
If you are interested in that Remotion obtains certain certifications, contact us at hi@remotion.dev to discuss this as an add-on for your Enterprise License.