Accessibility

1. Our target

We target WCAG 2.2 (the Web Content Accessibility Guidelines, version 2.2) at Level AA across the marketing site, the account area and the editor. Version 2.2 specifically, because it adds the criteria a video editor actually runs into: focus must not be obscured, a dragging movement must have an alternative that does not require dragging, and interactive targets have a minimum size.

We do not claim conformance. Conformance is a testable statement and we have not finished testing. This page says what we have done and what we have not, and we will update it as that changes.

2. What is in place

• Every interactive control is reachable and operable with a keyboard, in a logical order, with a visible two-part focus ring that works on both light and dark surfaces.
• A "Skip to content" link is the first focusable element on every page.
• Colour contrast is held to a floor in the design tokens themselves — 4.5:1 for body text, 3:1 for large text, borders and state indicators — so a component cannot ship below it.
• Colour is never the only way information is conveyed: links are underlined, states carry text or shape as well as hue.
• Text scales to 200% without clipping or horizontal scrolling, and layouts are verified at 390px width as well as at desktop widths.
• Motion respects prefers-reduced-motion. With it set, animations are reduced to a minimum and autoplaying video does not start.
• Autoplaying media on the marketing site is muted, loops, and has a visible pause control.
• Status changes during processing are announced to screen readers through live regions, not only shown as a moving bar.
• Automated accessibility checks run against every public page in our test suite, and a violation fails the build.

3. Known limitations, stated plainly

• Automated testing catches roughly a third of accessibility problems. Ours runs without a real layout engine, so contrast is verified at the token level rather than on the rendered page.
• A manual screen-reader pass over sign-up, checkout, upload, plan approval, export and cancellation has not been completed and recorded yet. Until it has, treat our coverage of those flows as unverified.
• The editor is an information-dense tool. The timeline in particular involves precise positioning; a non-dragging alternative is required by our own target and is not finished.
• Captions produced by Flinzo are machine-generated from your audio. They need your review before you publish — their accuracy is not something we can promise, and accessible output is ultimately your editorial decision.
• We have not had an independent accessibility audit.

Full conformance cannot be established by automated tooling. It requires manual testing with assistive technology and expert review, and we will say so on this page until both have happened.

4. Tell us about a barrier

If something on Flinzo blocks you, write to us. Tell us the page, what you were trying to do, and the assistive technology and browser you use if you know them. We aim to acknowledge within 5 business days and to give you either a fix or a timeline within 30 days. If we cannot fix something quickly, we will look for a way to get you the result another way.

Accessibility contact

support@flinzoai.com

This statement was last reviewed on 2026-10-15.