Accessibility Statement

1. How the Service is made accessible

• ●Keyboard accessibility — the main components can be navigated and operated with a keyboard.
• ●Compatibility with common screen readers, with explicit field labels (label / aria-label).
• ●Text resizable up to 200% without loss of functionality; the Service respects the browser's font-size setting.
• ●Alternative text (alt) for meaningful images.
• ●The document language is declared on every page (lang="he" / "en"), with full RTL support in Hebrew.
• ●Respects the OS-level prefers-reduced-motion setting — animations are reduced or disabled.
• ●A visible focus state on most interactive elements.
• ●Error messages are textual, not conveyed by color alone.

2. Known limitations and alternatives

We work toward continuous improvement. The following limitations are currently known to us:

• ●Some introductions screens rely on swipe gestures. A full alternative exists — like / pass buttons beside each card — so the Service can be used without swiping.
• ●The contrast of some secondary (low-emphasis) text has not yet been fully audited; we are working to ensure sufficient contrast.
• ●Emoji and text containing emoji may not always be announced optimally by every screen reader.

3. Accessibility contact

Encountered an accessibility issue? We would like to know and will work to fix it promptly:

• ●Email: info@simple-web.co.il
• ●Phone: 053-757-2773
• ●Please include: what you tried to do, on which page, which browser / device, and what difficulty arose.
• ●We aim to respond within 14 business days.

4. Technical basis

• ●The application is built in Next.js and React, and uses accessible Radix UI primitives.
• ●Automated accessibility linting (eslint-plugin-jsx-a11y) runs on every commit and in CI.

5. Updates

This statement is updated when there are significant changes to the Service's accessibility. Updates are published on this page.