[ accessibility ]

Accessibility at Captiv.

Captiv should work for every creator, including people who navigate by keyboard, use a screen reader, or need higher contrast. We orient our work to the Web Content Accessibility Guidelines (WCAG) 2.1 level AA and treat accessibility issues as bugs.

What we’ve implemented

Full keyboard access to core flows, including the upload dropzone, dialogs, and menus
Focus management in every modal (focus traps, Escape to close, focus return)
Visible focus indicators and labeled form fields throughout
Color contrast tuned to meet AA on functional text
Meaningful page titles, landmarks, and alt text on informative images
Buttons and toggles carry proper roles and pressed/expanded states

Known limitations

Captiv is a fast-moving product and some newer or experimental surfaces may lag behind the standard above. When we find a gap (or you report one), fixing it gets prioritized like any functional bug.

Tell us if something is hard to use

If any part of Captiv is difficult to use with assistive technology, we genuinely want to know. Email supportcaptivsocial@gmail.com with the page and what happened, and we'll work on a fix and get back to you.