Accessibility Statement
Our commitment to making Zod accessible for everyone, including our conformance targets, the features we've built, and how to reach us if you encounter a barrier.
Our Commitment
Zod is committed to ensuring digital accessibility for people with disabilities. We continuously improve the user experience for everyone and apply relevant accessibility standards.
We believe everyone deserves to find meaningful connections, regardless of ability. Accessibility is not an afterthought at Zod — it is a core part of our design and engineering process. Every new feature we ship is reviewed against accessibility criteria before it reaches users.
This Accessibility Statement covers the Zod website (zod.app), the Zod iOS app, and the Zod Android app.
Conformance Standards
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. WCAG 2.2 is developed by the World Wide Web Consortium (W3C) and defines how to make web content more accessible to people with disabilities.
Current conformance status
The Zod website is partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. We are actively working to resolve known issues (see the Known Issues section below).
Mobile apps
Our iOS app is designed to work with Apple's VoiceOver screen reader and Dynamic Type. Our Android app is designed to work with TalkBack and supports system font size scaling. Both apps are tested regularly with assistive technologies on each major platform release.
We align mobile app accessibility with WCAG 2.2 Level AA where applicable, and additionally follow platform-specific guidelines: Apple Human Interface Guidelines (Accessibility) and Android Accessibility Guidelines.
Accessible Features
Visual accessibility
- High-contrast dark theme with a minimum 4.5:1 contrast ratio for body text
- Text sizes respect your OS-level font size preferences on both iOS and Android
- All informational images include descriptive alt text
- Profile photos can be navigated and described using your device's screen reader
- No information is conveyed by colour alone
- Animations and transitions respect your OS Reduce Motion setting
Motor and interaction accessibility
- All interactive elements are reachable and operable via keyboard on the web
- Touch targets on mobile are a minimum 44×44pt (Apple) / 48×48dp (Android)
- The app supports Switch Control (iOS) and Switch Access (Android)
- No time limits are imposed on core matching or messaging interactions
- We do not use CAPTCHAs that require visual recognition without audio alternatives
Cognitive accessibility
- Simple, plain language used throughout the interface
- Consistent navigation and predictable layouts across all screens
- Error messages clearly describe what went wrong and how to fix it
- Multi-step processes (e.g. profile creation) include progress indicators
- No auto-playing audio or video in the core app experience
Screen reader support
- Semantic HTML with proper heading hierarchy on the web (H1 → H6)
- ARIA labels and roles applied to custom interactive components
- Focus management maintained during navigation and modal interactions
- Live regions used for dynamic content updates (e.g. new message notifications)
- Form fields have programmatically associated labels
Known Issues
We are actively working to resolve the following known accessibility issues. Target resolution dates are estimates and subject to change.
Photo gallery in profile viewer
Target: Q2 2026Swipe gestures in the photo gallery are not fully accessible via VoiceOver/TalkBack. A tap-based navigation alternative is in development.
Video profile prompts
Target: Q2 2026Video content in video prompts does not currently include captions. We are integrating automatic caption generation.
Interactive match map
Target: Q3 2026The distance visualisation map is not fully accessible to screen reader users. A text-only alternative is being designed.
Third-party payment UI
Target: OngoingSome elements of the Stripe payment sheet on web may not meet full WCAG 2.2 AA requirements. We are working with Stripe on improvements.
Third-Party Content
Zod includes content and functionality from third-party services (e.g. Stripe for payments, Zendesk for customer support). While we choose partners who take accessibility seriously, we cannot fully control their accessibility compliance.
If you encounter an accessibility issue on a third-party component embedded within Zod, please let us know. We will raise it with the relevant vendor and, where possible, provide an accessible alternative.
Feedback and Assistance
We welcome your feedback on the accessibility of Zod. If you experience barriers or have suggestions for improvement, please contact our Accessibility Team:
Zevello, Inc.
71–75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom
Email: accessibility@dhabli.com
We try to respond to accessibility feedback within 2 business days. If you need information from our website in a different format (such as accessible PDF, large print, or audio), please email accessibility@dhabli.com and we will do our best to accommodate your request within 10 business days.
Enforcement
If you are not satisfied with our response to your accessibility concern, you may escalate to:
- UK: Equality and Human Rights Commission (equalityhumanrights.com) or contact the Equality Advisory Support Service (EASS)
- USA: US Department of Justice (ada.gov) or file a complaint under Section 508 if applicable
- EU: Your national disability rights authority or ombudsperson
Technical Information
Technologies relied upon
- HTML5, CSS3, JavaScript (ES2022+)
- React / Next.js for the web application
- React Native (iOS and Android apps)
- WAI-ARIA 1.2 for accessible rich internet applications
- SVG for icons (with title elements for screen reader access)
Assessment approach
Zod assessed the accessibility of our products through the following methods:
- Self-evaluation against WCAG 2.2 AA checklist
- Automated testing using axe-core (web) and Accessibility Scanner (Android)
- Manual testing with VoiceOver (iOS/macOS), TalkBack (Android), NVDA (Windows), and JAWS
- User testing sessions with participants who use assistive technologies (conducted bi-annually)
- Third-party accessibility audit (most recent: January 2026, conducted by Deque Systems)
This statement was last reviewed on March 1, 2026.