At Planora we want everyone, including people with disabilities, to be able to use our website and our service easily, independently and with dignity. This statement describes what we have done to make them accessible, what is still limited, and how to reach us if you need help.
Legal basis and standard
We make the service accessible in accordance with the Equal Rights for Persons with Disabilities Law, 5758-1998, and the Equal Rights for Persons with Disabilities (Accessibility Adjustments for Service) Regulations, 5773-2013. The Regulations refer to Israeli Standard IS 5568, which is based on the international Web Content Accessibility Guidelines (WCAG). The public site aims to conform to WCAG 2.1 at level AA.
Accessibility of the public site
The site at planorastudio.tech has been built with accessibility in mind from the start:
- semantic HTML, with a clear heading structure and marked page regions (landmarks);
- a "skip to content" link at the top of every page;
- full keyboard operation, with a clearly visible focus indicator;
- text alternatives for images;
- sufficient colour contrast between text and background;
- text that can be enlarged to 200% without loss of content or function;
- a layout that adapts to phone screens and to browser zoom;
- respect for the system "reduce motion" setting;
- form fields with labels, and clear error messages that are also announced to screen readers;
- Hebrew pages displayed right to left and English pages left to right, with the language of each page correctly marked;
- no time limits for reading or for completing an action.
The accessibility menu
Every page of the site has an accessibility menu, where you can:
- make the text larger;
- switch to high contrast;
- underline links;
- stop animations;
- switch to a readable font.
Your choices are saved in your browser's local storage, so they stay in place on your next visit, and they are not sent to us. The menu complements the accessibility settings of your operating system and browser rather than replacing them; the site respects those settings too.
How we tested
We checked the site using the keyboard only and with automated accessibility checks against WCAG 2.1 level AA, at desktop and phone sizes, in the browser engines of Chrome, Firefox and Safari. The site supports the current versions of Chrome, Edge, Firefox and Safari. Testing with screen readers is planned next; until then, we want to hear about any difficulty you meet.
Accessibility of the Planora app
In the app at app.planorastudio.tech, the account screens, projects, forms, menus and dialogs work with the keyboard and with screen readers, in Hebrew (right to left) and in English.
Known limitations
We want to be open about what is not yet fully accessible:
- The drawing canvas of the plan editor and the 3D view – these are visual by nature, and drawing or moving around in them needs a mouse, a trackpad or touch. Keyboard shortcuts cover many actions, but not all of them.
- AI-generated images – do not yet have text descriptions.
- PDF and print presentations – follow the visual layout of the plan, so they may be less convenient to read with a screen reader.
We are working on improvements in these areas. If any of them makes it hard for you to use Planora, contact us and we will find an accessible way to help, for example help by e-mail or a guided session.
Information in an accessible format
You can ask us for information from the site or the service, including these legal pages, in an accessible format that suits you. Tell us what you need through the contact form, as described below.
Physical premises
Planora's service is provided online. We have no premises that receive the public, so physical accessibility arrangements do not apply.
Accessibility coordinator and contact
If you came across an accessibility problem, need help, or have a suggestion, please contact Planora's accessibility coordinator through the contact form and choose the topic "Accessibility". We reply by e-mail within 5 business days.
To help us help you quickly, it is useful to include:
- the page or screen where you came across the problem;
- a short description of the problem;
- the browser and the assistive technology you used, for example a screen reader.
Date of this statement
This statement was updated on 17 November 2026. The accessibility check was last reviewed in November 2026.