Accessibility Statement

1. Summary

2. Scope

This statement applies to Domu Match services delivered through the website and progressive web experience at domumatch.com (including subdomains we use for the product), excluding:

• Third-party websites, widgets, or documents that we link to but do not operate (for example your bank, a landlord, or a government portal).
• Embedded or redirected experiences on another company’s domain (notably Persona during ID verification), except where we choose and control the integration points on our own pages.
• User-generated content (such as chat messages or profile photos) where the material originates from other users.

We review major product updates for accessibility impact and update this statement when our position materially changes.

3. Our commitment

We design and build Domu Match so that students and young professionals in the Netherlands can complete core tasks - sign up, verify, complete onboarding, view matches, chat, and manage settings - without unnecessary barriers. That includes support for keyboard use, visible focus, logical headings, and compatibility with common assistive technologies where we control the code.

Domu Match is operated from the Netherlands by DMS Enterprise (eenmanszaak), trading as Domu Match (handelsnaam), KVK 97573337. This matches the identification in our Privacy Policy and Terms of Service.

4. Technical standards and law

We aim to meet WCAG 2.2 Level AA success criteria for web content we control. WCAG is an internationally recognised standard referenced in European technical specification EN 301 549 and in national transpositions that apply to certain categories of ICT procurement and services.

Domu Match is a consumer-facing platform, not a government body. Depending on how laws such as the European Accessibility Act apply to our services over time, we will align our practices and this statement with applicable obligations. Regardless of specific legal classification, accessibility is part of how we want the product to work for every user.

5. What we implement (and keep improving)

Structure and navigation

• Semantic HTML and landmarks so pages have a sensible outline.
• A “skip to main content” link in the marketing navigation.
• Consistent navigation patterns across major sections where the product allows.

Visual design and readability

• Light and dark appearance options where the interface supports them, respecting system preference where appropriate.
• Focus styles on interactive controls so keyboard users can see where they are.
• Responsive layouts so content reflows when you zoom or use a smaller viewport.

Forms and errors

• Labels and instructions tied to inputs.
• Error messages that identify what went wrong and how to correct it, where the platform surfaces validation.

Media and non-text content

• Meaningful alternative text for informative images we add in the product and marketing site.
• When we publish video or audio with essential information, we work toward captions or transcripts as production capacity allows.

6. Keyboard and assistive technology

Core flows are intended to be usable with a keyboard: Tab and Shift+Tab to move between focusable elements, Enter or Space to activate buttons and toggles, and Escape to close many overlays and dialogs where implemented.

We test with and design for common combinations such as VoiceOver on Apple platforms, TalkBack on Android, and screen readers on Windows. No two setups behave identically; if something fails in your environment, tell us the browser, version, and assistive technology so we can reproduce it.

7. Testing and quality

We combine automated checks (for example axe-core in development workflows), manual keyboard review, and targeted testing with assistive technologies on critical journeys. During beta we may ship iterative UI changes; we treat regressions as bugs to be fixed or tracked.

8. Known limitations

Despite our efforts, some limitations may apply:

• Beta features and experiments may temporarily miss polish (focus order, announcements, or labelling) before we stabilise them.
• Persona’s verification UI lives on Persona-controlled domains; accessibility there depends on Persona. If you cannot complete verification, contact us - we will work with you on a reasonable alternative where the law and our risk controls allow.
• Optional analytics, session replay, or marketing tools load only after consent; their interfaces are partly controlled by vendors listed in our Cookie & Local Storage Statement.
• Very old browsers or assistive technology versions may not support modern web standards we rely on; we test recent stable releases.

9. Feedback and complaints

Your reports directly influence our backlog. Please include the URL, a short description of the barrier, what you expected, and what happened instead. Screenshots or screen recordings help but are not required.

For self-service information you can also use our Help Center, FAQ, and Safety pages. For how we process personal data and the rules of the platform, see the Privacy Policy and Terms of Service.

If you are not satisfied with our reply, you may escalate using the same contact channel and ask for a review. This does not affect any statutory rights you may have under Dutch or EU consumer or equality law, which depend on your situation.

10. Alternative formats and reasonable adjustments

If you need information from this statement in another format, or need a reasonable adjustment to use Domu Match, contact us. We will discuss options with you openly and without prejudice.

11. Updates

We review this statement at least once a year and after substantial product changes. The “Last updated” date at the top changes when we publish a meaningful revision.

Accessibility Contact

If you need this statement in another format (for example plain text or a larger print layout), email us at domumatch@gmail.com and we will try to accommodate you within a reasonable time.