Accessibility Statement

Effective date: July 30, 2026

Dateagent should be usable by everyone, including people with disabilities. This statement describes honestly where we are today — including what does not work yet — rather than what we intend to build.

Our standard

We are working toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA on our websites and web invitation pages, and toward Apple's accessibility guidance for iOS in our app. This is a target we have not yet met. Specific known failures are listed below.

Where we stand today

Guest web pages (invitations, RSVP, receipts)

This is the stronger of our two surfaces, and it is the one most guests use — a guest can RSVP entirely in a browser without installing anything.

• Forms are keyboard-operable. Every control on the RSVP and receipt pages is a native form element with an explicit label. There are no click-only controls that a keyboard cannot reach, and no custom tab ordering.
• Zoom works. No page suppresses pinch or browser zoom, and layouts reflow rather than clipping when text is enlarged.
• Images carry text alternatives, and decorative graphics are hidden from screen readers rather than announced.
• Structure is semantic. Pages use a main landmark and real headings in order, with meaningful elements for host notes and date options.

iOS app

• Dark mode is fully supported across the app, not merely on isolated screens.
• Text size follows your iOS setting. Nothing in the app opts out of Dynamic Type scaling. We have not verified that every screen lays out well at the largest sizes, so some text may truncate.

We do not claim support for any accessibility feature in the App Store's accessibility labels for the iOS app. That declaration and this statement are deliberately consistent: we would rather claim nothing than claim something a person cannot actually rely on.

Where we fall short

We would rather write these down than let you discover them.

In the iOS app:

• VoiceOver is incomplete. Standard buttons are announced correctly, but many custom controls — including some icon-only buttons in the invitation-creation flow — have no spoken label, and photos are not described. Someone relying on VoiceOver will hit unlabelled controls in core flows.
• Voice Control is not usable, for the same reason: controls without a name cannot be spoken to.
• Reduce Motion is not respected. The app's animations play regardless of that iOS setting.
• Some colour contrast is insufficient. A secondary text colour used for captions and supporting labels does not meet the WCAG AA contrast minimum against a light background.
• A few states are shown with colour alone, notably selected times when building an invitation.

On guest web pages:

• Dialogs do not move keyboard focus when they open, so a keyboard or screen-reader user is not placed inside them automatically.
• Photo descriptions are generic — every image of a date option shares the same description rather than describing each photo.

In process: we have no automated accessibility testing and no per-release accessibility review.

If accessibility blocks you

If any of the above stops you from doing something — or you need this statement or any policy in an alternative format:

Email: [email protected] (subject "Accessibility")

We aim to respond within 5 business days. Where a feature is not accessible yet, we will complete the task with you another way, including handling it directly on your behalf. We prioritise anything blocking a core flow: signing in, creating an invitation, and RSVPing.

Guests never need an account or the app to RSVP — the web pages above are always available as an alternative to the iOS app.

Review

This statement is reviewed at least annually and whenever major features ship, and it is re-checked against the code rather than restated from memory. Last review: July 30, 2026.