1. Our target
We aim to meet WCAG 2.2 at level AA, the Web Content Accessibility Guidelines, across our marketing site, our public pages, and the web app. This is an ongoing goal. It is not a claim that every page or feature already meets it.
2. What we have done
- Keyboard use: the main navigation, the mobile menu, the example format tabs, sign-up and sign-in forms, and our legal pages can be used with a keyboard alone. A skip link at the top of each marketing page jumps to the main content. Keyboard focus is shown with a visible outline.
- Mobile navigation: on small screens, the links open from a Menu button. Sign in stays visible in the header at every width.
- Motion: the home page has a Pause animations control. It stops or starts the looping example videos, the scrolling platform list, and the animated hero. If your device asks for reduced motion, those animations are turned off, example videos do not start on their own, and you can still play a video with its controls.
- Captions: clips you render include captions, either burned into the picture or as a selectable subtitle track. You can also download an SRT subtitle file and a full timestamped transcript for each project.
- Screen readers: decorative graphics, including the dashboard illustration on the home page and the hero artwork, are hidden from assistive technology so the content is not read twice.
- Text contrast: we have darkened small grey text on light backgrounds and brightened dim text on dark backgrounds to meet the 4.5:1 contrast ratio for body text.
3. Known limitations
- The web app: some screens in the signed-in app are still being improved. If a screen is hard to use, please tell us and we will prioritize it.
- Clip content: clips do not yet include speaker labels or audio description. Captions are generated automatically from the speech, so they can contain mistakes.
- Third-party services: checkout is provided by Creem, and bot verification on sign-up and sign-in is provided by Cloudflare Turnstile. Their own accessibility is their responsibility. If one of these steps blocks you, contact us and we will try to help.
4. How we test
We run automated accessibility checks during development and review changes with the keyboard. Screen reader testing is being expanded. We have not yet had an independent accessibility audit.
5. Feedback and contact
If you find something that is hard to use or cannot be used, email support@aiclipper.video. Please include the page address, the browser or device, and the assistive technology you use if you can. We aim to reply within 5 business days, and we will tell you if a fix will take longer.