Accessibility Statement

Last updated:
Version:
1.0

Accessibility Statement

DearHim, Inc. Last Updated: 5/8/26

Our Commitment

DearHim, Inc. is committed to ensuring that the Service is accessible to as many people as possible, including people with disabilities. We strive to meet or exceed the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as published by the World Wide Web Consortium (W3C).

We work to design, develop, and maintain our websites and applications with accessibility in mind, and we routinely test and audit our experience to identify barriers and remove them.

What We've Built In

Current accessibility features include:

  • Keyboard navigation: All interactive elements (buttons, links, form fields) are reachable and operable using only a keyboard.
  • Screen reader support: We use semantic HTML, ARIA roles where appropriate, and alt text for images so screen readers can communicate the content of our pages.
  • Color contrast: Text and UI elements meet WCAG 2.1 AA color contrast ratios for legibility.
  • Resizable text: Text on our website resizes up to 200% without breaking layout.
  • Focus indicators: Keyboard focus is visually indicated on every focusable element.
  • Skip-to-content links: A "Skip to main content" link appears at the top of each page for keyboard users.
  • Form labels and error messages: Forms have programmatically associated labels and clear, descriptive error messages.
  • Captions and transcripts: Where we publish audio or video content, we provide captions or transcripts.
  • Reduced motion: We honor the prefers-reduced-motion system setting and minimize animation accordingly.

Known Limitations

We are honest about where we still have work to do. As of this writing, we are working on:

  • AI character voice notes: We do not yet provide automatic transcripts for every AI-generated voice note. Users can request transcripts on demand. Full automatic transcription is in development.
  • Some AI-generated images: Alt text for AI-generated character portraits is generic ("AI-generated character portrait of [Character Name]"). We are exploring more descriptive alt text generation.
  • Onboarding flow: Some animation-heavy onboarding steps may be challenging for users with motion sensitivities. The prefers-reduced-motion setting reduces this; we are working on a fully animation-free alternative path.

How to Report an Accessibility Issue

If you encounter a barrier on our Service, please tell us. We take accessibility issues seriously and treat them as bugs to fix.

Please include:

  • A description of the issue (what you were trying to do, what happened).
  • The page or feature where it occurred (URL or screen name).
  • Your assistive technology and browser/OS, if applicable (e.g., "JAWS 2024 + Chrome on Windows 11").
  • Any suggested fix.

We respond to accessibility reports within 5 business days. We aim to remediate confirmed issues within 30 days where technically feasible. For more complex issues, we will provide a target remediation date.

Third-Party Content

Our Service incorporates third-party services (Stripe, Clerk, etc.). While we choose accessibility-aware vendors, we do not control all third-party experiences. If you encounter an accessibility barrier in a third-party-provided portion of the Service, please report it to us anyway — we will work with the vendor or find a workaround.

Ongoing Improvement

Accessibility is not a one-time task. We:

  • Conduct internal accessibility reviews on new features before launch.
  • Periodically engage with external accessibility consultants for audits.
  • Train our engineers and designers on accessibility principles.
  • Treat user reports as a primary input for our remediation roadmap.

Standards Conformance

We work toward conformance with:

  • Web Content Accessibility Guidelines (WCAG) 2.1 Level AA (current target)
  • Section 508 of the US Rehabilitation Act (where applicable, e.g., government partnerships)
  • EN 301 549 v3.2.1 (the European standard)
  • Americans with Disabilities Act (ADA) Title III principles

We do not currently claim full conformance with WCAG 2.2 (the most recent guidelines), but we plan to update our target to WCAG 2.2 AA in 2027.

Contact