Skip to content

Accessibility at Ellwood Bristol

We build websites and AI-first products that are usable for everyone. From landing pages to dashboards and creator tools like Reactivid, we design for keyboard access, readable contrast, clear structure, and accessible media outputs—and we keep improving with real feedback.

Read our accessibility statement Share accessibility feedback

We aim for WCAG-aligned experiences, semantic UI, reduced-motion support, and accessible video outputs (captions and transcripts) where media is involved.

Inclusive by default Clear structure, predictable UI patterns, and readable typography across our products.
Keyboard & focus Logical tab order, visible focus states, and shortcut-friendly flows.
Screen reader support Accurate labels, roles, and names—tested on real assistive tech where possible.
Contrast, motion & media Token-driven themes, reduced-motion options, and caption-first media workflows.

Accessibility at Ellwood Bristol

Ellwood Bristol builds AI-first software products that should work for more people—regardless of device, input method, or assistive technology. This statement explains how we approach accessibility, which standards we aim for, and how to reach us if something is not working for you.

Products
Ellwood Bristol web properties and product surfaces (including Reactivid for scripting, voiceover, and video prep)
Owner
Ellwood Bristol Inc. (Sault Ste. Marie, Ontario, Canada)
Last updated

Commitment & principles

WCAG 2.2 AA

Ellwood Bristol is committed to providing equitable access to our websites and products. We design, build, and test with accessibility in mind and treat accessibility defects as functional bugs, not nice to haves. This applies to our marketing surfaces and to product workflows—especially Reactivid, where accessible, caption-first video creation is a core product goal.

  • 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 users who rely on assistive technologies, plus continuous iteration.
Scope
Public marketing site(s), documentation, and Ellwood Bristol product surfaces (including Reactivid workflows like scripting, voiceover, storyboard, and export)
Out of scope
Third party sites we link to, customer-hosted infrastructure, and legacy exports not created with accessibility features enabled
Assessment model
Self assessment with a mix of automated and manual reviews

Standards, platforms & testing

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across Ellwood Bristol marketing surfaces and primary product experiences. Conformance is currently self assessed, and we are working toward more formal audits as our product suite 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 people 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 Ellwood Bristol builds for access

Design system

  • Semantic type scales and heading hierarchy across products and sites
  • 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 user journeys and feature areas

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 where applicable
  • Live regions or inline status text for important, non-modal updates

Accessibility in video workflows & exports

For media-focused products like Reactivid, accessibility is not just an interface requirement; it also influences how creators can 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 an Ellwood Bristol product 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 our products 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.
Contact Ellwood Bristol

This statement will evolve as our products grow and as we learn from users. If you rely on a specific assistive technology or workflow, your feedback is especially valuable.