Accessibility at Reactivid
Reactivid is built to support accessible, caption-first video workflows. We design, test, and iterate with access in mind—and keep improving with real feedback.
We aim for WCAG-aligned experiences, accessible video outputs, and continuous improvement.
Accessibility at Reactivid
Reactivid is built so more people can plan, script, and ship video, regardless of device, input method, or assistive technology. This statement explains how we think about accessibility, which standards we aim for, and how to reach us if something is not working for you.
Commitment & principles
WCAG 2.2 AAReactivid is committed to providing equitable access to our website and application, and to the tooling creators use to produce video content. We design, build, and test with accessibility in mind and treat accessibility defects as functional bugs, not nice to haves.
- Accessibility considered at strategy, UX, content, and engineering stages.
- Keyboard and screen reader support are treated as core interaction modes.
- Contrast, typography, and motion are driven by shared design tokens.
- Feedback loops with creators, editors, and viewers who rely on assistive technologies.
Standards, platforms & testing
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA for the Reactivid marketing site and primary product surfaces. Conformance is currently self assessed, and we are working toward more formal audits as Reactivid evolves.
Testing methods
- Automated checks (landmarks, labels, names/roles/values, contrast)
- Manual keyboard testing (Tab / Shift+Tab, Enter, Space, Esc, arrow keys)
- Screen reader spot checks across key journeys
- Real user feedback from creators who depend on assistive technology
Assistive technology (sample)
- VoiceOver on macOS and iOS (Safari / Chrome)
- NVDA with Firefox or Chrome on Windows
- JAWS with Chrome on Windows (select flows)
- TalkBack on recent Android devices (Chrome)
Supported browsers & devices
- Current and previous major versions of Chrome, Safari, Firefox, and Edge
- Desktop and laptop form factors are primary; tablet layouts are tuned
- Mobile flows prioritize read only and review experiences until editing is fully optimized for touch
We respect reduced motion settings, provide visible focus indicators, aim for ≥ 4.5:1 contrast for text and essential UI, and target 44×44 px minimum hit areas where practical.
How Reactivid is built for access
Design system
- Semantic type scales and heading hierarchy across app and site
- Design tokens for color, spacing, and elevation with theme aware contrast
- Clear visual states for hover, focus, active, and disabled across controls
- Motion used sparingly and never as the only way to understand a change
Product & content
- Descriptive labels and helper text instead of jargon where possible
- Clear error messages that explain what happened and how to recover
- Meaningful alt text for non decorative imagery and iconography
- Consistent terminology across scripting, voiceover, storyboard, and export
Engineering
- Keyboard first navigation and logical tab order
- Native HTML elements preferred, with ARIA used only when necessary
- Programmatic names, roles, and states for complex widgets (e.g., timelines)
- Live regions or inline status text for important, non modal updates
Accessibility in video workflows & exports
Reactivid is not just an accessible interface; it is designed to help you ship more accessible video content where possible.
Authoring & review
- Scripts and voiceover text are kept in sync so you can generate and review captions later in your edit tools.
- We avoid encoding critical information solely in color or animation cues inside storyboards and timing views.
- Exported timing data is structured to support caption and transcript workflows in tools like Adobe After Effects and DaVinci Resolve.
Limits & shared responsibility
- Final accessibility of a video depends on choices made in your NLE (captions, audio mix, on screen text, etc.).
- AI generated text and voiceovers may include errors; human review is required before publishing.
- If you have specific regulatory or compliance requirements, we recommend working with your own counsel or accessibility specialist.
Feedback, issues, & alternate formats
If you experience a barrier while using Reactivid or this website, we want to hear about it. Concrete examples (URL, browser, device, assistive technology, and what you were trying to do) help us investigate and fix issues faster.
How to contact us
- Use our contact form: Go to contact
- Include the page or screen, your browser and device, and any assistive technology you use.
- Tell us what you expected to happen and what happened instead.
We aim to acknowledge accessibility related reports within a reasonable timeframe and prioritize fixes based on severity and impact.
Requesting alternate formats
- You can request important information about Reactivid in alternate formats (for example, large print, accessible PDF, or text only) by contacting us through the contact form.
- Where feasible, we will provide an alternate format or a suitable accessible alternative within a reasonable time.
- If we cannot meet a particular request, we will explain why and work with you to identify other options where possible.
This statement will evolve as Reactivid grows and as we learn from users. If you rely on a specific assistive technology or workflow, your feedback is especially valuable.
Tell us how we can improve Reactivid
If you run into an accessibility issue in the Reactivid app or on this site, we want to hear from you. Use the contact form to describe what you were trying to do, what happened instead, and what would make the experience work better for you. If you are comfortable sharing them, details like the page or screen, your browser and device, and any assistive technology you use (for example screen reader, magnification, switch, or voice control) help us reproduce and fix issues faster.
- Where Page/screen
- Device Browser + OS
- AT Screen reader / magnifier / voice
- What Expected vs actual
We aim to reply within 5 business days.