Accessibility statement for the system

The system was made accessible under the Israeli standard IS 5568, which is based on the WCAG 2.0 guidelines, at level AA. We also work to WCAG 2.1, and check accessibility again with every change to the system. A few things worth knowing are listed under "Points to note", each with a way to get help.

• The system is available in Hebrew, Arabic, English and Russian. Each screen sets its language and writing direction, and Latin text such as email addresses and SKUs is shown in the right direction.
• Every screen has its own name and one main heading. The main menu, the top bar and the content are marked as regions, and the menu marks the screen you are on. A "Skip to content" link appears on the first press of Tab.
• Everything can be done with the keyboard: the menu, the search (Ctrl+K, or ⌘K on a Mac), the inventory table and each product's actions menu, the editing panel, dialogs and the guided tour. Escape closes a dialog, menu or editing panel, and the focus returns to where it was opened from. Where you are is clearly marked.
• When an editing panel opens, the focus moves to its heading, and before leaving with unsaved changes the system asks first.
• Every form field has a label, and optional fields are marked. An error message is written in words and tied to its field, and after trying to save, the focus moves to the first field to fix. A confirmation dialog appears before products are removed from a store.
• Messages about progress, success or failure, and the number of results in search and filters, are read out by screen readers without moving the focus.
• The inventory, orders and activity tables are built with column and row headers. On a phone, the inventory shows a card for each product.
• Stock, sync and store states are shown in words or with an icon and text, never by color alone.
• Text color contrast meets the standard, in light mode and in dark mode, and the mode can be switched from the top bar.
• Screen transitions and small animations stop for anyone whose device settings ask for less motion. There are no slideshows or scrolling text, and a video starts only after pressing play.
• The system fits phones and computers, and can be zoomed to 200% without losing content.
• The tutorial videos show the system without sound, with captions. Every step of a video is also written as text beside the player and under the video, and selecting a step takes the video to its moment.
• The QR code for turning on two-step verification is shown with its key as text, to type in by hand.

• Actions on several products at once appear on screens 640 pixels wide or more, such as a computer or a tablet. On a phone, products are edited one at a time. If you need such an action from a phone, write to us and we'll do it together.
• The captions in the tutorial videos are part of the picture, so their size and color are fixed. The same text is written in full beside the player, where screen readers and zoom work as usual.
• Product names, descriptions and pictures come from the connected stores, as written there. A product's picture is always shown next to its name.

Signing in with Google, and approving a store's connection on the approval screens of Shopify, Wolt and Google or in WooCommerce's admin on the store's site, happen on those companies' pages, whose accessibility is theirs to look after. So do the YouTube video player and the stores' product pages opened from the system. Having trouble there? Write to us and we'll help.

The system is designed to work in current versions of Chrome, Edge, Safari and Firefox, on computers and phones, with a keyboard and with assistive technologies such as screen readers.

StoreDuet's service is given in the system, on the site and by email, and there is no place where customers are received.

No exemptions or reliefs from the accessibility duties were granted to the system.

Ran into a problem, or is something in the system not accessible to you? Write to us at support@storeduet.com, even if you couldn't sign in. It helps to include the screen's name, what you tried to do, and which browser and assistive technology you used. Requests about accessibility are handled first.