Accessibility Statement

Version 00.23 · updated 2026-09-18

1. Our commitment

PitchPlan is a planning tool for professionals and homeowners. We want it to be usable by people with disabilities, including people who navigate by keyboard, people who use a screen reader, people with low vision, and people who need larger text or reduced motion.

We are not there yet, and this statement says where we are.

2. What this statement covers

  • The PitchPlan website at https://pitch-plan.com, including the public landing, pricing and legal pages, registration, and the signed-in account area.

  • Not covered by the assessment below: the planning canvas itself, which is a 3D engine rendered inside a frame. A drawing canvas is not reachable by a screen reader in the way a form is, and we have not yet designed or tested an equivalent route to its function.

  • Not covered: a published showroom, whether opened from its own link or placed inside somebody else's website. It is the same 3D engine in a frame, it carries no accessibility panel of its own, and on another site the page around it is that site's responsibility rather than ours.

  • Not covered: the PitchPlan Android application. It has not been assessed and we make no conformance claim for it.

3. The standard we work to

We are working towards WCAG 2.2 Level AA (W3C Recommendation).

We chose that target because it is the strictest of the benchmarks that apply to us. WCAG 2.2 Level AA contains every success criterion of WCAG 2.1 Level AA, which in turn contains every success criterion of WCAG 2.0 Level AA, so the target we work to sits above each of the levels the instruments below adopt. Being above them is a choice, and clause 4 states how far along it we are.

The instruments this statement responds to:

Where Instrument Level Israel Equal Rights for Persons with Disabilities Law 5758-1998, and the Equal Rights for Persons with Disabilities (Service Accessibility) Regulations 5773-2013 made under it, regulation 35, applying Israeli Standard IS 5568 part 1, edition of September 2023, which supersedes the edition of May 2021. That standard adopts WCAG 2.0 of 11 December 2008 with Israeli national modifications and additions, other than as regards digital documents Level AA under regulation 35A European Union European Accessibility Act, Directive (EU) 2019/882, applicable since 28 June 2025, with EN 301 549 as the harmonised standard. Article 4(5) exempts microenterprises providing services from its accessibility requirements, and we may fall inside that exemption; we work to the standard regardless, and this statement does not assert that we are covered by the Directive Level AA United Kingdom Equality Act 2010, duty of reasonable adjustment No prescribed standard; WCAG 2.2 AA is the accepted benchmark United States Americans with Disabilities Act, Title III, as applied to commercial websites No prescribed standard; WCAG 2.2 AA is the accepted benchmark

Two of those instruments offer this business an exemption, and we do not rely on either. Regulation 35F of the Israeli regulations exempts a business whose average annual turnover does not exceed NIS 100,000, and Article 4(5) of the European Accessibility Act exempts a microenterprise providing services, defined in Article 3(23) as fewer than ten persons with turnover or balance sheet not over EUR 2 million. PitchPlan is below all three figures. We publish this statement, work to the standard in this clause, and list our failures in clause 5 regardless, so nothing in this statement is offered on the strength of an exemption and nothing in it is withdrawn if an exemption ceases to apply.

Territory follows the user, not the company. Operating from Israel is not a defence in any row of that table.

4. Conformance status

Partially conformant with WCAG 2.2 Level AA. Parts of the product do not fully conform, and the failures we know about are listed in clause 5.

This assessment rests on:

  • automated and scripted measurement of the live site, covering tab-order walks, accessible-name computation, overlap checks and inspection of roles and states. The date of the most recent run is given below and in clause 10, and it is the date this assessment speaks as of. We do not promise a measurement interval, because a promised interval that slips turns into a claim we are not keeping; what we state is the date, and the list in clause 5 is that date's output;

  • no manual testing with a screen reader by a person who uses one, and no testing with users with disabilities. That is a real limitation of this assessment and we state it rather than gloss it.

Measurements last taken across the whole site: 11 August 2026. Single pages were re-measured on 16 August and on 14 September 2026, and the list below says which.

5. Known limitations

These are measured failures, not a general disclaimer.

Blocking or severe

What fails WCAG Known since The public language selector writes to a setting the product does not read, so choosing a language does nothing 3.1.1 Language of Page 10 August 2026

Significant

What fails WCAG Known since On the Security and Privacy screen, five of six visually identical cards are inert with nothing announcing that they are unavailable; only Delete Account acts 4.1.2; 1.3.1 11 August 2026 Text direction is fixed left-to-right, so Hebrew and Arabic content renders in the wrong direction 1.3.2 Meaningful Sequence 9 August 2026 Escape inside the language list of the accessibility panel closes the whole dialog rather than the list 2.1.2 adjacent 10 August 2026 The accessibility panel can render in three languages at once 3.1.2 Language of Parts 10 August 2026 No navigation route to pricing exists at a 390 pixel viewport 2.4.5 Multiple Ways 8 August 2026

Minor

What fails WCAG Known since The billing tab strip is not a tab list, and the active tab is indicated by colour alone 1.4.1 Use of Color; 4.1.2 11 August 2026 A control points at a panel element that does not exist 4.1.2 8 August 2026 The accessibility panel's position button is named only by an English tooltip 4.1.2; 3.1.2 10 August 2026 The page language attribute disagrees with the English content shown 3.1.1 8 August 2026

Fixed since the list above was first published

These were on the list, and are not failures any more. The date is the day the fix reached the site; where a later measurement of the live page confirmed it, that date is given too.

What failed WCAG Fixed Confirmed on the live site The guest view presented no focusable controls and no tab stops 2.1.1 Keyboard 15 August 2026 16 August 2026 The community view was listed beside it as unusable by keyboard; measured on 14 September 2026 it has 53 focusable, named controls 2.1.1 Keyboard never failed as listed 14 September 2026 The account menu declared a menu role with no menu items 4.1.2; 2.1.1 13 August 2026 16 August 2026 The same rectangle in the account menu took two tab stops with the same name 2.4.3 Focus Order 13 August 2026 16 August 2026 The visible engine frame had no title 4.1.2; 2.4.1 16 August 2026 16 August 2026 The four legal-agreement toggles announced only "Accepted" or "Accept"; each is now named by its agreement and its state 4.1.2; 1.3.1 13 August 2026 not yet: the signed-in pages have not been re-measured Two notification toggles on the Security and Privacy screen had no accessible name 4.1.2 13 August 2026 not yet: the signed-in pages have not been re-measured Four Expand details controls were hard-coded in English with no expanded-state announcement; each now names its agreement in your language and announces its state 4.1.2; 3.1.2 13 August 2026 not yet: the signed-in pages have not been re-measured

The planning canvas, and what we offer instead

The 3D planning canvas is the core of the product. It is not usable by keyboard alone or by a screen reader, and we do not claim otherwise.

We provide no alternative route to its function today. We offer no text-based, form-based or assisted equivalent of drawing a plan, and we will not describe one that does not exist. What we can offer is a person: write to the address in clause 8, tell us what you are trying to achieve, and we will work out with you what is possible, including doing part of it for you.

Everything outside the canvas, which is registration, account management, billing, the community library and the legal pages, is in scope of clause 5 and is where our work is going first.

Not assessed at all

  • The Android application.

  • Colour contrast across the product, computed rather than judged by eye.

  • Screen-reader behaviour as experienced by somebody who uses one daily.

  • Cognitive and low-vision testing.

6. Where the website was checked, and how to adjust it yourself

The measurements in clause 4 were taken on the website running in a current Chromium-based browser, at desktop, tablet and mobile viewport widths. We have not separately measured Firefox, Safari or Edge, and we do not claim a result for them.

Some adjustments are your browser's rather than ours, and they work on any site:

  • Zoom. Hold Ctrl, on a Mac Command, and press the plus key to enlarge the page or the minus key to reduce it. Ctrl together with the mouse wheel does the same. Ctrl and zero returns the page to its normal size.

  • Keyboard navigation. The Tab key moves to the next control, Shift and Tab move back, and Enter or the space bar activates the control you are on. Where this fails on our site, it is listed in clause 5.

  • Text size and colours. Your browser and your operating system can enlarge text and change contrast for every site you visit, in their own accessibility settings.

The accessibility panel described in clause 7 offers some of the same adjustments inside the site itself.

We make no claim about assistive software we have not tested with. We have not verified PitchPlan against any screen reader, screen magnifier or voice recognition package, and clause 4 says so.

7. The accessibility panel

The site carries a floating accessibility panel offering visual adjustments. It comes from a third party and is bundled into the site rather than loaded from another company's servers.

It is a comfort tool. It does not make the site conformant, and we do not present it as conformance. The failures in clause 5 are in our own markup and are fixed there, not by an overlay.

8. Feedback and how to reach us

If you hit a barrier, however small, tell us:

Accessibility coordinator: Daniel Dadashev accessibility@pitch-plan.com · +972-543-357-357 Postal address: Haplada 23, Ashkelon, Israel.

Regulation 35 of the Israeli Service Accessibility Regulations requires an accessibility statement to name the person responsible for accessibility and how to reach them, where the business is required to appoint one. We name a person whether or not the appointment is required of a business this size.

Say what you were trying to do, which page you were on, and what you use, such as keyboard only, a screen reader and which one, or magnification.

We aim to reply within 14 business days. A business day is Sunday to Thursday, excluding public holidays in Israel, where we operate.

If our answer does not satisfy you:

  • Israel: the Commission for Equal Rights of Persons with Disabilities at the Ministry of Justice.

  • European Economic Area: the market surveillance or enforcement body designated in your country under the national law transposing the European Accessibility Act, and your national consumer body.

  • United Kingdom: the Equality Advisory and Support Service.

9. What we are doing about it

Accessibility is measured on this product periodically, and every failure in clause 5 is a tracked item with a first-seen date and an owner. That is the mechanism, and the list above is its output as at the date in clause 10. The date is the claim; we make no claim about how often the measurement runs, and the gap between that date and today is what it is. We update this statement when the list changes.

We have not set a target date for full WCAG 2.2 Level AA conformance, and we will not publish one we have not planned for.

10. How this statement was prepared

Version: 00.22, in force since 6 September 2026. Statement prepared: 14 August 2026, by review of the product's own measured accessibility record. Last reviewed: 18 September 2026. Measurements last taken: 11 August 2026 across the whole site; single pages on 16 August and 14 September 2026. Method: scripted measurement of the live site, covering tab-order traversal, accessible-name computation, overlap detection, and inspection of roles and states. Not used: manual screen-reader testing, testing with users with disabilities, or a third-party audit.