Accessibility

Built for as many people as we can, honest about who we can't yet reach.

How TalkHereNow works for users with different needs, what we've designed in, and where we still have work to do.

Last updated: July 1, 2026 v1.0 Talk Here Now LLC

The short version

Voice and text are interchangeable inputs, you can use either, switch any time. AI Friend replies appear as on-screen text bubbles, not just audio. The 3D AI Friend is, by nature, a visual experience; users with no or low vision can still talk to the AI Friend by voice and can ask the AI Friend to describe what the camera sees. We aim for WCAG 2.1 Level AA on the parts of the experience that aren't fundamentally visual. We are honest about what's still out of reach.

01

What accessibility means at TalkHereNow

We build for everyone we can reach. We are honest about who that doesn't yet include.

TalkHereNow is a browser-based augmented-reality experience, which means some of what makes the Service distinctive, the 3D AI Friend placed in your camera view, the back-camera motion sensing, the spatial placement, is inherently visual and physical. We have not pretended otherwise. Where the experience can be made accessible, we have made it accessible. Where it currently can't, we'll say so plainly on this page.

Our target conformance level for the parts of the Service that aren't fundamentally visual (the age gate, AI Friend selection, chat overlay, settings, account flows, and legal pages) is WCAG 2.1 Level AA. We are working toward that target, not claiming we are fully there. Where we know we fall short, we'll list it below.

02

Voice and text are interchangeable

You can talk to the AI Friend with your voice, or you can type into the chat overlay (see the Trust & Safety page for a description of how conversations work). Both reach the AI Friend. Both are first-class inputs, neither is a fallback or a degraded experience.

What this means in practice:

  • If you are Deaf or hard of hearing, you can type your messages and read the AI Friend's replies. AI Friend replies always appear as on-screen text bubbles, in addition to the spoken voice. You do not need to enable a captions setting; this is the default.
  • If you cannot type easily, motor impairment, repetitive strain, situational, you can speak. Your speech is converted to text by your browser's built-in speech-recognition feature. We don't transmit your raw audio to any AI provider for speech recognition; it runs in the browser.
  • If you switch between voice and text mid-conversation, the AI Friend handles it without prompting. Memory of the conversation is the same regardless of which input you used.

The chat overlay sits at the bottom of the screen in portrait and along the side in landscape. It is always reachable. You can dismiss the voice mode at any time and type instead.

03

Vision and what the AI Friend can describe for you

The 3D AI Friend is, by definition, a visual element placed in the camera view of your phone. If you are blind or have low vision, you will not see that AI Friend. The conversation, however, is fully usable by ear, the AI Friend speaks, and the speech recognition lets you reply by voice without ever needing to interact with the visual interface.

There is one feature worth flagging for users who can't see the visual overlay: the eye button. When you tap it (or ask the AI Friend to "take a look"), the AI Friend receives a description of what your camera is pointed at and responds with a short summary. We built this as a conversational feature, but in practice it is also a way to ask, "what's in front of me right now?", which we think makes the Service genuinely useful for users with limited vision, not just accessible in the legal-compliance sense.

What we can't currently do for vision-impaired users:

  • Audio cues for the AI Friend's spatial position (we don't generate spatial audio descriptors of where the AI Friend is "standing")
  • Audio descriptions of the AI Friend's facial expressions or body language
  • Audio narration of UI elements that have visual-only state (for example, "AI Friend is loading")

These are real gaps. If they would make the Service usable for you, please tell us at support@talkherenow.com, we want to know.

04

Motion, motion sickness, and reduced-motion settings

Augmented reality can trigger motion sickness, eye strain, or vestibular discomfort. Our Terms of Service recommend using the Service while stationary in a safe, private location and discontinuing use if you experience any of these.

For users sensitive to animation in general:

  • We respect the prefers-reduced-motion browser/system setting on non-essential UI elements (intro animations, screen transitions, decorative effects). When reduced motion is requested, those animations are shortened or removed.
  • The 3D AI Friend's body movements are part of the conversation and are not reduced by this setting, because the AI Friend's gestures are how the AI Friend communicates. If this is a problem for you, please tell us.
  • Photosensitive epilepsy: we do not use rapidly flashing or strobing visual effects in any part of the Service. The animated background uses slow, low-contrast motion only.
05

Screen readers, keyboard navigation, and contrast

The non-visual parts of the Service (age gate, AI Friend selection, account flows, settings, and these legal pages) are built with the following in mind:

  • Semantic HTML where possible, landmarks, headings, form labels, and ARIA attributes used correctly rather than decoratively
  • Visible focus indicators for keyboard navigation
  • Text contrast targeting WCAG 2.1 AA minimums (4.5:1 for normal text, 3:1 for large text and UI controls)
  • Captions on instructional video where used

We test on iOS VoiceOver and Android TalkBack. We have not formally audited the experience with a JAWS or NVDA user; if you use either and find barriers, we will fix them.

Known gaps as of this date:

  • The 3D scene itself is not screen-reader-narrated. We don't currently produce a continuous textual description of what the camera view is showing.
  • The AI Friend carousel uses swipe gestures on mobile. Keyboard alternatives for the swipe are not yet exposed.
  • Some of the in-experience controls (mute toggle, end-session button) need stronger ARIA labels.

We are working through these as we find them. The Report an Accessibility Issue path below is the fastest way to tell us about one we've missed.

06

Mobile-only is a real constraint

TalkHereNow requires a phone or tablet with a working camera, motion sensors, and a current mobile browser (iOS Safari 16 or newer, Android Chrome). The Service does not run on a desktop computer. This is not an accessibility choice, it is a fundamental property of the camera-based engine. We mention it here because users sometimes ask whether a desktop screen reader can drive the Service: it cannot.

For users whose primary computing device is a desktop, including many users of advanced assistive technology, this is a real exclusion. We do not have a planned workaround. We are sorry.

07

Reporting an accessibility issue

If something in the Service is unusable, hard to use, or just frustrating because of how we built it, please tell us. We treat accessibility reports the same way we treat safety reports: a real human reads every one, and we respond.

Email support@talkherenow.com with the subject line "Accessibility" and whatever detail you can share:

  • What you were trying to do
  • What assistive technology you were using, if any (screen reader name and version, voice control, switch device, etc.)
  • What happened (or didn't)
  • Your phone and browser, if you can share them

We confirm receipt within 24 hours and respond within five business days. For urgent issues, barriers that prevent you from completing a critical task like cancelling a subscription, we respond faster.

We do not require you to have an account to send a report. We do not require you to disclose a disability. We do not gatekeep on whether your barrier is "really" an accessibility issue versus a usability bug, those distinctions are not yours to draw.

08

Standards we work toward

We aim for WCAG 2.1 Level AA on the non-visual portions of the Service. We monitor the European Accessibility Act and applicable US state laws (including California's Unruh Civil Rights Act and the Americans with Disabilities Act as interpreted in the consumer-web context) and update our practices as those laws and their interpretations evolve.

We do not currently issue a VPAT (Voluntary Product Accessibility Template). When we have completed our first formal third-party accessibility audit, we will publish the summary findings here.

09

Versioning

This page is dated at the top. The commitments on this page, interchangeable voice and text input, AI Friend replies always shown as text, real-human review of every accessibility report, are commitments, not aspirations. We add to the "known gaps" list as we find new ones, and we remove items as we fix them.

For comments on this page or on our accessibility approach, write to support@talkherenow.com with the subject line "Accessibility."

Talk Here Now LLC  •  1712 Pioneer Avenue, Ste 135, Cheyenne, WY 82001