Accessibility
VerbaCut's accessibility target, current limitations, and how to request help or report a barrier.
Launch configuration incomplete. The legal operator, address, contact, and effective date must be provided through server environment settings and reviewed by qualified counsel before this policy is treated as effective.
1. Our target
VerbaCut is working toward WCAG 2.2 Level AA across signup, upload, caption editing, timing, style selection, checkout, account, export, deletion, support, and policy flows. This is a target, not a current conformance certification.
2. Product principles
- Keyboard access and a visible focus indicator for every action.
- Programmatic labels, instructions, errors, names, roles, and values.
- Text contrast, 200% zoom, responsive reflow, reduced motion, and non-color status cues.
- A non-drag alternative for timeline and trim operations.
- Caption editing guidance that helps creators produce readable, synchronized subtitles.
3. Known preview limitations
The editor still needs a full nonvisual equivalent for the video preview and timeline, stronger focus management for transient menus, and additional assistive-technology testing across mobile devices. These items must be resolved before claiming WCAG conformance.
4. Get help or report a barrier
Use Support and choose Accessibility. Describe the page, task, assistive technology, browser or device, and the format of any accommodation you need. VerbaCut should acknowledge the report and offer a reasonable alternative while the issue is investigated. Use the Support form; a direct support email has not yet been configured.
Questions
Use Support and choose the category that matches your request. Do not include passwords, API keys, payment-card information, or unnecessary sensitive media.