GaydarTM
Accessibility

Accessibility at Gaydar

We're building Gaydar to work for everyone, including users with disabilities. Here's what we've implemented and what we're working on.

Accessibility at Gaydar

Last Updated: October 4, 2026

What changed on October 4, 2026:

  • Reduced motion: we now say what the site does. When your device asks for reduced motion, it reduces or turns off its animations.
  • Color contrast: we now describe how we check it, with automated tools (axe and Lighthouse) against WCAG 2.1 AA.
  • We now cover the home-page film and the IRL map illustration. Both have a text description for screen readers, and the film starts without sound.
  • We added a Last Updated date.

We're building Gaydar to work for everyone, including users with disabilities. Here's what we've implemented and what we're working on.

1. Our Commitment

  • Gaydar aims to conform to WCAG 2.1 Level AA on our website and to meet iOS and Android platform accessibility standards in our mobile app.
  • Accessibility is treated as a product requirement, not an afterthought. New features are reviewed against accessibility standards before release.

2. What we've implemented (website)

  • Semantic HTML landmarks (header, main, footer, nav)
  • Skip-to-content link for keyboard users
  • Visible keyboard focus indicators on all interactive elements
  • Reduced motion: when your device asks for reduced motion, the site reduces or turns off its animations.
  • Alt text on all meaningful images; decorative images are marked aria-hidden
  • Accessible form labels and error messages
  • We test the site's color contrast against WCAG 2.1 AA with automated tools (axe and Lighthouse).
  • Screen-reader-only utility class for context that's otherwise visual
  • The home-page film starts without sound. Buttons let you turn the sound on and pause the film. The film has a text description for screen readers. If your device asks for reduced motion, the film stays on a still image until you press play.
  • The IRL map illustration on the home page has a text description for screen readers.

3. Mobile app accessibility

  • Full VoiceOver (iOS) and TalkBack (Android) support on all screens
  • Dynamic Type support: the app respects the user's system font size preference
  • Sufficient touch target sizes (minimum 44x44 points per Apple / 48dp per Google)
  • Color is never the only indicator of meaning
  • Reduced motion preferences honored

4. Known limitations

  • Some animated illustrations on the marketing site use decorative motion that can be visually busy. When your device asks for reduced motion, the site reduces or turns off its animations.
  • The interactive location grid on /security is a visualization and may be hard to parse with a screen reader alone. A text description is provided in the surrounding paragraphs.
  • Verified selfie capture requires a working front-facing camera; we are exploring alternative verification paths for users who cannot use cameras.

5. Report an accessibility issue

If you encounter an accessibility barrier, email accessibility@gaydarapp.com with a description of the issue and the page or screen where it occurred. We aim to respond within 5 business days and resolve issues within 30 days where technically feasible.

6. Standards we reference

  • WCAG 2.1 Level AA (Web Content Accessibility Guidelines)
  • Section 508 (US federal)
  • EN 301 549 (EU)
  • Apple Accessibility Guidelines (iOS)
  • Android Accessibility Guidelines