This statement covers the public MazelMeet website, including the waitlist, referral links, Yenta interest form, partner inquiry form, support pages, and table feedback. The iPhone app is covered by its own accessibility work.
Accessibility statement
Last reviewed July 18, 2026
MazelMeet is committed to making the website usable for as many people as possible, regardless of ability, device, or assistive technology. Accessibility is treated as part of the build, not an afterthought, and we welcome reports that help us do better.
Conformance target
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across the public website. That target guides how we write, build, and review each page, and it is the standard we hold new work to before it ships.
Conformance describes an ongoing effort rather than a fixed finish line. As pages change and new features arrive, we test against the same standard again.
Measures we take
Every page uses semantic landmarks, a single main heading, and a logical heading order so that screen reader and keyboard users can understand and move through the structure. A skip link at the top of each page jumps straight to the main content.
Forms use real labels, grouped fieldsets, and ARIA descriptions for hints and errors, so assistive technology announces what each field expects and what went wrong. Interactive targets such as links, buttons, and toggles are sized to at least 44 by 44 pixels for easier pointer and touch use.
The site is operable with a keyboard alone, with visible focus and no keyboard traps. It supports zoom and reflow without loss of content, respects the reduced motion preference, and does not rely on color alone to carry meaning.
Language and direction
The website is offered in English and in Hebrew. Hebrew pages render fully right to left, with matching direction on text, forms, navigation, and layout, so the reading order stays natural in both languages.
Compatibility
The website is built to work with current versions of major browsers on desktop and mobile, together with their platform screen readers and common assistive technologies, including voice control, screen magnification, and browser zoom. Older or uncommon combinations may show smaller differences.
Known limitations
Some content depends on services outside our direct control, such as map tiles or an embedded challenge used to block automated abuse. Where a third party control is harder to operate, we provide a path to reach us so no task is blocked. If you find a barrier that is not listed here, please tell us and we will treat it as a priority.
Assessment and review
This statement was last reviewed on July 18, 2026. Accessibility is checked during development through a mix of automated tooling, keyboard and screen reader passes, and manual review of new pages. We revisit this statement as the website changes.
Feedback and contact
If something is hard to read, navigate, hear, or complete with a keyboard, screen reader, voice control, zoom, or another assistive technology, tell us which page and which device and software you used. We will help you complete the task in an accessible way and use the report to improve the product.
Report an accessibility barrier: [email protected]