Our goal
Captions exist to make video accessible, and we want the tool that makes them to be accessible too. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across our public website: the home page, features, pricing, guides, free tools, help and legal pages.
Where we are today
We consider the public website partially conformant with WCAG 2.2 Level AA: some parts don’t fully meet the standard yet, and the gaps we know about are listed below. This is based on our own checks while building the site. It hasn’t been independently audited.
What we do
- Use semantic HTML — headings, landmarks, and labeled links and buttons — so pages work with screen readers.
- Make navigation, forms and dialogs, including cookie settings, usable with a keyboard.
- Check text color contrast against WCAG ratios.
- Respect your device’s “reduce motion” setting for animations.
- Design pages to work on small screens, with touch targets sized for fingers.
- Export captions as SRT and VTT files, which viewers can switch on, resize and have read by assistive technology.
Known limitations
- Video preview in the editor. Captions in the preview are a visual rendering over the video and may not be announced by screen readers. The same words are available as editable text in the transcript panel.
- Timeline editing. Changing when a caption starts or ends by dragging its edges on the timeline needs a mouse, touch or pen; there’s no keyboard alternative yet. You can move the playback position with the keyboard.
- Mobile timeline. On small screens, moving through the timeline relies on touch gestures.
- Visual styling controls. Some caption styling controls, such as color and position pickers, are visual by nature and may be hard to use with a screen reader.
- Burned-in captions. Captions burned into an exported video are part of the picture, so viewers can’t resize them or have them read aloud. For accessible video, publish the SRT or VTT file as closed captions as well.
- Automatic transcripts. Speech recognition makes mistakes. Review captions before you rely on them for accessibility.
- Other companies’ pages. Google sign-in and our payment processor’s checkout are run by those companies, and their accessibility is outside our control.
Tell us about a barrier
If something is hard to use, or you need information in a different format, email support@theautocap.cc with “Accessibility” in the subject, or use our contact form. It helps to include:
- the address of the page;
- what you were trying to do, and what happened;
- your device, browser, and any assistive technology you use.
We aim to reply within 5 business days. If something stops you from using AutoCap, we’ll try to help another way while we work on a fix.
About this statement
We prepared this statement on September 14, 2026, and we’ll review it whenever we make significant changes to the site.