What we made accessible
These parts of Project3000 are covered by this statement: the home and sign-in page, the dashboard where you create, deploy and manage apps, your plan and billing screens, help popups, emails we send, and this page.
- Keyboard: everything can be used with a keyboard alone. Focus is always visible, a "Skip to main content" link comes first on every page, and popups keep focus inside them until they close (the Escape key closes them).
- Screen readers: pages use proper headings, landmarks and labels. Form errors, copy confirmations, upload progress and deploy results are read out automatically. Decorative animations are hidden from screen readers and described in text instead.
- Color and text: text and controls meet WCAG AA contrast. Information is never shown by color alone.
- Zoom and small screens: pages work at 200% zoom and on phones. On desktop, most pages fit on one screen; when you zoom in, the page scrolls instead of hiding content.
- Motion: moving demos have a "Pause animations" button, and we respect your device's "reduce motion" setting.
- Forms: every field has a label, supports browser autofill, and explains exactly what went wrong if something needs fixing.
- Language: the platform is in English, and each page declares its language so screen readers pronounce it correctly.
How we check it
Every page and popup is scanned with automated accessibility tests (axe-core, WCAG 2.2 A and AA rules) on desktop and phone sizes, and we test key flows by hand with a keyboard and a screen reader. We re-check before every release and do a full review every year.
Tested with: Google Chrome, Mozilla Firefox and WebKit (the engine behind Apple Safari), on desktop and phone screen sizes, and the Windows Narrator screen reader. We also check what screen readers announce on every page and popup. A test with Apple VoiceOver is planned, and this statement will be updated when it is done.
Known limitations
- Apps built by our customers run on *.apps.project3000.io. Their creators own and control them, and are responsible for their accessibility. If you find a problem in one of those apps, please contact its owner. You're also welcome to tell us.
- Payments happen in Paddle's secure checkout window, and Google sign-in happens on Google's page. Both are run by those companies under their own accessibility policies.
- Telegram support chat opens in Telegram, which is run by Telegram.
- We're not aware of other barriers right now. If you find one, please tell us and we'll fix it according to how serious it is: within 48 hours if it blocks a core task such as signing up, paying or deploying.
Report a problem or ask for help
If something is hard to use, or you need information in a different format, contact Project3000 support by email at [email protected], by phone at +972 54 552 1599, or through the Telegram help button on any page.
It helps to tell us which page you were on, what you were trying to do, and which browser and assistive technology you use (if any). We will:
- reply within 5 business days;
- tell you when we expect to fix it;
- help you finish what you were doing in the meantime, for example by email;
- let you know when it's fixed.
About this statement
Exemptions: no exemptions or relief under the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013 apply to this website.
This statement is issued by Project3000. It was last reviewed on September 25, 2026, and we review it at least once a year and whenever the platform changes significantly.