Accessibility Statement
Our commitment, and where we currently fall short
Last updated: 16 August 2026
We want Raydance.ai to be usable by everyone. This statement says what we aim for, what we have actually done, and what we know is not yet good enough — because a statement that claims perfection is worth nothing to the person who cannot use the product.
The standard we work to
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. That is the benchmark used by Section 508 of the US Rehabilitation Act, by courts applying the Americans with Disabilities Act to websites, and by the European standard EN 301 549 referenced under the European Accessibility Act.
We have not commissioned an independent accessibility audit. We therefore describe our status as partially conformant: most of the interface meets the standard, and some of it does not. We will not claim full conformity until an audit supports it.
What we have done
- • Semantic HTML with landmarks, so screen readers can navigate by region.
- • Accessible names on interactive controls, and labelled navigation regions.
- • Full keyboard operability for navigation, forms and dialogs, with visible focus indicators.
- • Touch targets sized for motor accessibility on small screens.
- • Light and dark themes, respecting the operating-system preference, with contrast checked against the AA threshold.
- • Text that reflows without horizontal scrolling, and that scales with browser zoom.
- • A component library built on accessible primitives, so accessibility behaviour is inherited rather than reimplemented per screen.
Known limitations
- • Generated images have no automatic alternative text. An image produced from your prompt has no description unless you give it one. We are looking at deriving one from the prompt.
- • Complex creative tools. The workflow builder and canvas-style editors rely on pointer interaction and are not yet fully keyboard-operable. This is the largest known gap.
- • Third-party flows. Payment and age-verification steps run on providers' own pages, whose accessibility we do not control.
- • Motion. Some transitions animate; we honour reduced-motion preferences where implemented, but coverage is not yet complete.
We list these because you are entitled to know before you spend money, not because we intend to leave them there.
Tell us where we failed you
If any part of this service is not accessible to you, write to info@raydance.ai and describe what you were trying to do, what happened, and what you use — a screen reader, keyboard only, magnification, or something else. We aim to reply within five business days.
If a feature is blocking you, we will help you achieve the same outcome another way while we fix it. That offer is genuine; please use it.
Review
This statement is reviewed whenever we make a substantial change to the interface, and at least annually. It was last reviewed on the date shown at the top of this page.