Accessibility statement.

Arrive should work for everyone, including people who use a keyboard, a screen reader, a magnifier or voice control. This page says what we have done, what is not perfect yet, and how to tell us when something does not work.

The standard we aim for

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. We have not had an independent audit yet. [Israeli standard reference and exemption basis to be confirmed before launch.]

What we have done

• Every page can be used with a keyboard alone, with a visible focus outline and a "Skip to content" link.
• Headings, landmarks and button labels are written for screen readers, and the words and the tempo number in the animated pictures also have plain text.
• Text and controls meet the AA contrast ratios in both light and dark, and the page can follow your device setting or a choice you make.
• Buttons and controls are at least 24 by 24 pixels, the WCAG 2.2 minimum.
• Animation is decorative and limited. The slow background drift and the phone demo play for a short time and then stop, the phone demo has a pause button, and everything switches off if your device is set to reduce motion.
• The content is readable without JavaScript.

What is not perfect yet

• The phone picture on the home page is an illustration. Its two buttons, "Switch between run and walk" and "Pause demo", work with a keyboard and a screen reader; the rest of the picture is decoration, and the same information is in the text around it.
• The cards in "The Run" move by hover on a mouse. Use the dots under them, the arrow keys, or a swipe instead.
• We are still testing the site at 200% zoom and with each major screen reader. [Update before launch.]

Tell us when something does not work

This statement was last updated [date set at launch].