Accessible by design — with honest limits

Our target

We aim to meet WCAG 2.2 Level AA for the public site and the caption editor. That includes keyboard access, visible focus, sufficient contrast, semantic headings, form labels, reduced-motion support and captions for our own demo video.

What is in place

• Semantic landmarks, a skip link, and one H1 per page.
• Keyboard-operable navigation, dialogs and FAQ sections.
• Visible focus rings and sufficient text contrast on the marketing site.
• Reduced-motion support; animations are disabled when the operating system requests it.
• Captions and a text alternative for product demo media where autoplay would otherwise be required.
• Form controls with labels, and errors that are announced rather than color-only.

Known limitations

• The editor is a dense, desktop-class interface. It is usable with a keyboard, but it is not optimized for small touch screens.
• AI-generated captions can mishear names, accents, crosstalk and jargon. Review and correct captions before publishing, especially for regulated or public-sector content.
• Some third-party checkout and Google sign-in surfaces are controlled by those providers, not by us.
• Very old browsers without WebCodecs cannot export video in the browser; SRT/VTT downloads still work.

Captions and compliance

Auto-generated captions are a starting point, not a guarantee of legal compliance. WCAG 1.2.2 requires accurate, synchronized captions for prerecorded video. For public-sector, education, healthcare or regulated content, plan a human review pass for wording, timing, speaker labels, punctuation and meaningful sounds.

Feedback

If you hit an accessibility barrier, email support@autocaptions.org with the page, the browser and assistive technology you used, and what happened. We will respond on business days and prioritize barriers that block a core task.