Divine

Accessibility

How we work toward making Divine usable with assistive technology.

Effective date: May 16, 2026

Divine is a voice-first product, which cuts two ways for accessibility. Interfaces that work through voice tend to work well with screen readers, so VoiceOver and TalkBack are first-class concerns from the first build. The same design choice creates a real barrier for users who are Deaf or hard of hearing, which we address explicitly below rather than paper over.

Conformance target

We design and build to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, on the marketing website, and to Apple’s and Google’s platform accessibility guidelines in the App. We treat WCAG 2.2 AA as the floor, not the ceiling, and prioritize fixes that materially affect how a user reaches the core experience of meeting and talking to someone.

What we’ve done so far

The Divine app (iOS & Android)

  • VoiceOver (iOS) and TalkBack (Android) labels on interactive elements, including buttons, navigation tabs, and gesture-based controls.
  • Dynamic Type support — text scales with the system font-size setting, including for legal, profile, message, and gift screens.
  • Color and contrast meeting WCAG 2.2 AA in primary surfaces. We are continuing to audit secondary surfaces (older Stories templates, gift detail sheets).
  • Haptic feedback on key interactions in addition to visual feedback.
  • Reduce Motion respected: hero animations and the Aurora background are simplified when Reduce Motion is on.
  • Large-tap-target sizing on calls-to-action throughout the App so interactions stay reachable for users with motor differences.
  • Audio focus management so screen readers, voice match audio, and music apps do not fight over audio output.

The divineapp.io website

  • Semantic HTML structure, with headings in document order on every page.
  • Keyboard navigability across the entire site — every link, button, and form element is reachable with Tab.
  • Visible focus rings on all focusable elements (pink outline at a 3-pixel offset for keyboard users).
  • Color contrast against the dark theme reviewed at AA-or-better minimums.
  • Skip-to-content support and a single, clear landmark structure (header, main, footer).
  • Alt text on every meaningful image; decorative imagery marked as such so screen readers don’t announce it.

Where we know we still fall short

We’re being honest: voice-first products are not yet as accessible to Deaf and hard-of-hearing users as we want them to be. Specifically:

  • Live captions during voice match. Not yet shipped. We are evaluating on-device live transcription so a Deaf user can read what the other person is saying in real time.
  • Voice messages. We do not automatically transcribe voice messages today. Senders can include a text note alongside a voice message, and we plan to add automatic captioning.
  • Voice match flow. The match flow is currently voice-only. We are designing a text-bridge fallback so a user who cannot speak or hear can still match and chat.
  • Older avatars and gift assets. Some have alt text we’d like to improve.

Independent audit

We have not yet engaged a third-party accessibility auditor. Prior to public launch we will engage a recognized firm in this space — candidates include Deque, Level Access, and TPGi — and publish the firm name and audit date on this page. This is a commitment, not a completed audit.

VPAT / ACR availability

A Voluntary Product Accessibility Template (VPAT 2.5) and Accessibility Conformance Report (ACR) will be available on request once our first audit is complete. Email support@divineapp.io with the subject line “VPAT Request.” This is intended primarily for procurement teams.

Conformance frameworks

  • WCAG 2.2 Level AA — current target.
  • U.S. Section 508 — intent to conform.
  • Americans with Disabilities Act Title III — operating in good-faith compliance.
  • European Accessibility Act (EAA), in force from 28 June 2025 — we will meet its requirements before offering the App to users in EU Member States.

Roadmap (target dates — not commitments)

  • Live captions during voice match: [TBD — target Q1 2027 once an on-device transcription solution is selected]. Target — not a commitment.
  • Automatic transcription of voice messages: [TBD — target Q4 2026]. Target — not a commitment.
  • Text-bridge fallback for users who cannot speak or hear: [TBD — target Q2 2027]. Target — not a commitment.

Phone, TTY, and VRS alternative contacts

We are email-first today. We accept callbacks from any U.S. telecommunications relay service (TRS) provider, including TTY relay at 711 and Video Relay Service providers (Sorenson, ZVRS, Convo Relay, Purple). If you are using a relay service, ask the operator to email support@divineapp.io on your behalf, and we will reply via the same channel.

Accessibility lead

Accessibility at Tiger LLC is owned by [TBD — name and contact to be published prior to public launch].

How we test

  • Manual screen-reader walkthroughs of the iOS and Android Apps before every major release.
  • Automated checks (axe, Lighthouse) on the marketing site as part of our build process.
  • Color-contrast checks against AA on every design change.
  • Periodic external reviews when we’re working on a flow that materially affects accessibility.

If you hit a barrier

If anything on Divine makes the App or this site harder for you to use because of a disability, we want to know. Every accessibility report receives a human response.

Email support@divineapp.io with the subject line “Accessibility” and include:

  • What you were trying to do.
  • Which screen, page, or feature you hit the problem on.
  • What happened, what you expected, and (if you can) your device, OS version, and assistive technology you were using (VoiceOver, TalkBack, Switch Control, etc.).

We aim to respond within five business days. For urgent issues that block account access, we’ll move faster.

Alternative ways to reach us

If email is not accessible to you, you can also use any of the following:

  • Postal mail: Tiger LLC, California, United States. (Email us first for the specific address; we don’t publish a full mailing address on the marketing site for safety reasons but will send it on request.)
  • Through a trusted friend, family member, advocate, or interpreter authorized to contact us on your behalf.

Third-party content

Some content within Divine is created by other users (profile bios, voice messages, posts, Stories). We cannot guarantee the accessibility of every piece of user-generated content, but we provide moderation reporting tools and accessibility-friendly controls so you can mute, block, or hide content that isn’t working for you.

Updates to this statement

We update this statement whenever we ship a material accessibility change.