We want everyone to be able to use the website at rabbitsync.io and the RabbitSync application at app.rabbitsync.io (together, the "Service"), including people who use a screen reader, a keyboard instead of a mouse, magnification, or other assistive technology. This statement says what standard we hold the Service to, how far it meets it, what we know does not work yet, and how to tell us when something gets in your way.
1. Who we are
The Service is provided by Chen Doytshman, a licensed dealer registered in Israel, of Tel Aviv, Israel ("RabbitSync", "we", "us" or "our").
2. The standard we follow
We build and test the Service against the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, published by the World Wide Web Consortium. It includes everything in WCAG 2.1 at level AA, the version that Israeli Standard 5568 and the European standard EN 301 549 are based on.
3. How far the Service meets it
The Service is partially conformant with WCAG 2.2 at level AA: most of it meets the standard, and section 5 lists the parts we know do not yet, or have not yet been able to confirm.
4. What we have done
- Every page and control can be used with a keyboard alone, in a logical order, with a clearly visible focus indicator. A "Skip to content" link is the first thing on every page.
- Every page has its own title and a clear structure of headings, and the main areas of each page are marked so that assistive technology can move between them.
- Text and controls meet WCAG's contrast ratios, in the application's light and dark themes, and colour is never the only way a status or a problem is shown.
- Every link, button and form field has a name that assistive technology can read. A form shows each error next to its field, and the application announces when something you did, such as saving a setting, did not work.
- Pages work at up to 400% zoom without scrolling sideways, and with larger spacing between lines, paragraphs, letters and words.
- If your device asks for reduced motion, the Service shows no animation.
- The video on our home page can be paused, and has a text description.
- Changes to the Service are checked automatically against WCAG 2.2 at level AA before they are released.
5. Known limitations
- Screen readers. We have tested the Service with automated tools and with a keyboard, but not yet end to end with screen readers such as NVDA and VoiceOver. That testing is planned; until it is done, some parts may not read as well as they should.
- Charts. The charts on the application's dashboard can be explored with a keyboard, but a screen reader may not read the value of each bar. The totals are also shown as text beside them.
- Parts provided by other companies. Some parts of the Service come from other providers, and we cannot change how they are built: signing in and managing your account (Clerk), checkout and billing (Lemon Squeezy, our reseller), and the security check on our contact form (Cloudflare Turnstile). If one of them gets in your way, contact us (section 6) and we will help you do what you were trying to do another way.
6. Tell us about a problem, or ask for another format
If something in the Service is hard or impossible for you to use, or you need information in another format, tell us:
- by email to [email protected], or
- through our contact form, choosing "Something else".
Please say which page and what you were trying to do and, if you can, which browser and assistive technology you use. We will reply, and where we can we will fix the problem or give you what you need another way.
7. How we checked
We assessed the Service ourselves: automated testing against WCAG 2.2 at level AA on every change, and a review of the main pages and tasks with a keyboard, at 400% zoom, with larger text spacing, and with reduced motion.
8. Updates
We review this statement whenever a change to the Service affects accessibility, and at least once a year. It was last reviewed on 10 October 2026.