Accessibility Statement

This is an English translation provided for convenience. The Hebrew version is the binding version; if the two differ, the Hebrew version prevails.

Last updated: [[PLACEHOLDER: date, set at launch]]

Draft — not legal advice. This page was written from the codebase to describe real data flows as accurately as possible. It has not been reviewed by a lawyer and must not be treated as a finished document until it is.

We want done. to work for as many people as possible, including people with disabilities. This statement says plainly what has been done, what is not yet accessible, and how to reach us if something gets in your way.

1. Accessibility level

We are working to meet Israeli Standard IS 5568, which is based on WCAG 2.0 level AA. The Service does not yet fully meet it. The marketing site and legal pages are closer to meeting it. The 3D editor is only partly accessible, as set out below. [[VERIFY: whether the operator qualifies for a small-business exemption under reg. 35]]

2. What has been done

  • Every button and control on the site and in the editor has an accessible name a screen reader can announce, including icon-only buttons — in Hebrew on the Hebrew site.
  • Everything around the 3D view — the project gallery, the illustrated navigators, panels, dialogs, sharing and the account page — can be operated from the keyboard, shows a visible focus indicator, and never traps the keyboard.
  • The 3D view can be reached with the keyboard, is named for screen readers, and announces its keyboard controls: moving and orbiting the camera, top view, framing, and rotating, deleting and deselecting a selected item.
  • Selected state is exposed to assistive technology, not shown by colour alone, and status messages are announced to screen readers.
  • Selecting something in the 3D view announces what was selected, for example “Wall · 3.20 m selected”.
  • Single-key shortcuts (such as 1–4, E, T and ?) can be turned off in the Help panel, for people who use voice control.
  • Pages have clear headings and landmarks, and form fields are tied to their labels.
  • Text in the editor’s panels meets a 4.5:1 contrast ratio in both the dark and light themes, including over the brightest parts of the 3D image. This was measured on the rendered screen.
  • The site and the editor can be zoomed to 200% without controls overlapping or disappearing.
  • For anyone who has asked their operating system for less motion, interface animations are removed, camera moves in the 3D view jump instead of gliding (including going into and out of the walkthrough), doors in the walkthrough open without swinging, rain and the wind in the trees stand still, and the homepage demo shows the finished room without animating. The demo’s rotation can also be paused.
  • The homepage demo starts on its own when you scroll to it. While it plays, a visible “Skip to the room” button stops it.
  • Tooltips can be dismissed with the Escape key.
  • The Service is available in Hebrew (right-to-left) and English, and measurements read in the right order in both.

3. What is not yet accessible

  • Editing the 3D model. Drawing walls, selecting, dragging and rotating items, and the walkthrough are done with a mouse or touch on a graphical view. They currently have no screen-reader or full keyboard alternative.
  • Small screens. The editor is not yet adapted for phones.
  • The Service has not yet been tested with screen readers (NVDA, JAWS, VoiceOver). It has been checked with an automated accessibility checker (axe, WCAG 2.0 and 2.1 A/AA) and with a keyboard walk-through of every public page in Hebrew and English.

If any of this stops you using the Service, write to us and we will look for an alternative together.

4. Accessibility requests

Found an accessibility problem, or need information from the site in another format? Contact us and we will try to reply within 14 business days. It helps to say which page, what you were trying to do, and which assistive technology you use.

  • Accessibility contact: done. [[VERIFY: whether the accessibility contact must be a named person rather than the company]]
  • Email: done.design.app@gmail.com
  • Phone: [[PLACEHOLDER: phone number]] [[VERIFY: whether a phone number is required in addition to email]]