Accessibility Statement

Our commitment

Dropwire is operated by Avigdor Leibzon, an independent sole trader registered in Israel. We want this site to be usable by people with disabilities, including people who navigate by keyboard alone, people who use a screen reader, and people who need larger text, higher contrast or less movement.

We treat that as ordinary engineering work rather than a badge. Where we fall short, we would rather say so on this page than leave you to discover it.

What we aim for

This site meets the Israeli standard IS 5568 at level AA. IS 5568 is the Israeli web accessibility standard, and it is anchored to WCAG 2.0 at level AA. Our legal duty comes from the Equal Rights for Persons with Disabilities Act, 1998 and the Service Accessibility Regulations, 2013, which bring that standard in by reference.

We are not claiming an exemption. Exemptions from the website accessibility duty are based on revenue, and the three-year exemption for our revenue band applies only to sites that were already operating before 26 October 2017. This site is newer than that, so the duty applies to it in full.

What we have done

• Every page starts with a skip link so keyboard users can jump past the header and navigation straight to the content.
• Page structure uses real landmarks and headings in order, so screen reader users can move by region and by heading rather than reading everything from the top.
• Everything interactive is reachable and operable by keyboard, and the focused element always shows a visible focus ring.
• Text contrast is measured against the composited background, not assumed. Body text meets the 4.5 to 1 ratio and large text meets 3 to 1.
• Background video does not play for anyone whose system asks for reduced motion, and a Pause motion button in the corner of every page stops all movement for everyone else. That choice is remembered.
• Decorative images and video are hidden from screen readers, so they are not announced as meaningless content.
• The waitlist form has a real label, announces its result through a live region, and states what we do with your address before you type it.
• We use no accessibility overlay. Nothing on this site rewrites the page to make it look accessible to an automated checker.

What is not done yet

Listing these is part of the standard, and we would rather be specific than write that there are no known problems.

• We have tested with Narrator on Windows, and not yet with NVDA, JAWS or VoiceOver. NVDA in particular is the screen reader most widely used in Israel, so that is the next test we intend to run.
• The site has not been reviewed by a certified accessibility expert (morshe negishut). Our checks are our own.
• The signed-in application at app.dropwire.cc is a separate surface and is not covered by this statement. It is being worked through on its own.
• We have not yet tested against older assistive technology, or in Hebrew with a right-to-left layout, because the site is currently English only.

Telling us about a problem

If something here does not work for you, please tell us. You do not need to know what the technical problem is or name a standard. Describing what you were trying to do, and what happened instead, is enough.

Accessibility contact: Avigdor Leibzon
Email: avigdor@dropwire.cc

We aim to reply within three business days, and we will tell you what we are going to do about it and when. If we cannot fix something quickly, we will say that too, rather than going quiet.

If we do not put it right

You can complain to the Commission for Equal Rights of Persons with Disabilities at the Ministry of Justice, or bring a civil claim. Israeli law asks that an operator first be given notice of the problem and a reasonable chance to fix it, up to 60 days, which is another reason we would rather hear from you directly and early.

Testing behind this statement

Date of the last accessibility review: 23 September 2026.

That review covered three things. Automated testing with axe-core against the WCAG 2.0 A and AA rule sets across every page, which reported no failures. A keyboard pass checking tab order, focus visibility and the skip link. And a manual pass with a screen reader (Narrator on Windows), working through the skip link, the heading structure, the cookie choices, the settings dialog and the waitlist form. Automated tools cannot judge contrast on this site, because text here sits over video, gradients and scrims and the checker cannot work out what colour is actually behind a letter. So contrast was measured separately, by reading the pixels of the rendered pages: 527 pieces of text across the five pages, each compared against the background actually painted behind it. The lowest ratio found was 4.9 to 1, against a requirement of 4.5 to 1 for body text and 3 to 1 for large text.

The screen reader pass found two real problems, both since fixed. Reaching the cookie bar's Reject button took 29 key presses, because the bar sat at the end of the page; it now takes 3. And the Pause motion button was covered by that same bar, so on a narrow screen a tap aimed at it hit Reject instead. Neither was caught by any automated check, which is the argument for doing this by hand.