Accessibility
Accessibility at KindDate
Last updated
Everyone deserves a calm, usable way to prepare for a date. This page describes what we have built for accessibility, where we know we still fall short, and how to tell us when we get it wrong.
Our commitment
Dating already asks a lot of people; the tools around it should not add friction. KindDate aims to meet WCAG 2.1 Level AA across the site and to keep Aria usable whether you navigate by mouse, keyboard, touch, or screen reader. Accessibility is treated as part of the design, not a checkbox at the end.
What we've built for
- Keyboard navigationthroughout, with a visible “skip to content” link and clear focus outlines.
- Screen-reader structure — one main heading per page, logical heading order, landmarks, and labels on icon-only controls.
- Focus management in Aria — opening the chat moves focus into it, Escape closes it, and focus returns where you left off.
- Readable colour and type — text is sized and coloured to stay legible, and body text targets AA contrast.
- Reduced motion— animations respect your “reduce motion” system setting.
- Honest AI labelling — Aria is always identified as AI, in text, so nothing about the experience is misleading.
Voice and the talking avatar
Aria can be used entirely by text— voice is never required. The spoken “Call Aria” experience and its animated avatar are an enhancement, and they work best on a desktop Chrome browser today. The avatar is decorative: everything Aria says is also available as text, so you never lose meaning if the animation is off, slow to load, or unsupported on your device.
Known limitations
We would rather name gaps than hide them. Current known limitations include:
- The real-time voice call is best on desktop Chrome; on other browsers and on mobile we point you to the text experience rather than a broken one.
- The 3D avatar is a large asset; on slow connections it may take time to appear, which is why it is optional and text-first.
We are working to widen support, and we track accessibility issues alongside functional ones.
How we test
We check pages with automated accessibility tooling, keyboard-only walkthroughs, and screen-reader passes, and we review colour contrast on text. Automated tools cannot catch everything, so real feedback from people who use assistive technology is genuinely valuable to us.
Tell us where we fall short
If something on KindDate is hard to use with your assistive technology, we want to know. A staffed public contact channel is not published yet, and a dedicated accessibility contact will be added here before the product asks you to rely on it. In the meantime, the Support page collects the most common questions, and you can ask Aria to explain any page you are on.
This statement reflects the current public preview and will be updated as the product grows and as we address the limitations above.