Accessibility statement

JARAI Studio is committed to making its products usable by everyone, including people who rely on assistive technology.

The standard we target

We aim to meet WCAG 2.1 level AA across the Studio Console, the Client Portal, the Developer Portal, the marketing site, and this help centre. In practice that means:

• Keyboard operability — interactive controls are reachable and usable without a mouse.
• Accessible names — buttons, links, and form fields expose a clear name to screen readers (icon-only controls carry an explicit label).
• Structure — pages use proper headings, landmarks, and reading order.
• Reduced motion — animations are suppressed when your system requests reduced motion.
• Contrast — text and essential UI meet AA contrast against the brand palette.
• Forms — labels are associated with their controls, and errors are announced.

Note

Automated accessibility checks run in the build pipelines of the Studio Console, the marketing site and this help centre, where they carry guards against common regressions (for example, an unlabelled icon button or a low-contrast heading fails a check rather than shipping). The Client Portal and the Developer Portal do not have automated accessibility checks yet, so barriers there are more likely to reach you — please report them.

How this help centre is checked

Every page of this help centre is tested with axe-core (through Playwright, in Chromium) against the WCAG 2.0 and 2.1 level A and AA rules, in both the light and the dark theme, on every proposed change and before every release. A change that introduces a failure cannot be published.

• Last audit: 13 October 2026 — every page, both themes, 0 failures.
• What it found before then: an audit on 8 October 2026 found text below the AA contrast ratio of 4.5:1 — table headings, the titles of note and caution callouts, the search box hint on the home page, and the highlighted current page in the sidebar in the dark theme. All of them were corrected on 13 October 2026.
• What an automated check cannot see: it does not judge whether wording is clear, whether a video’s captions are accurate, or how a page works with every combination of assistive technology. Those still depend on your reports.

Media & captions

Generated video and audio can include captions, transcripts, and audio descriptions. Coverage is tracked on the Accessibility dashboard so gaps are visible and can be closed.

Known limitations

No product is perfectly accessible at every moment. Where we’re aware of a barrier, we prioritise fixing it. If you hit something that blocks you, please tell us — that’s the fastest way to get it fixed.

Report an accessibility barrier

Contact us via Contact support and describe:

• the page or feature,
• what you were trying to do,
• the assistive technology and browser/device you were using.

We’ll acknowledge your report and work to resolve it.