DRAFT 2 — not yet in force. Prepared on 19 October 2026 for the US & Canada edition. The “known limitations” in §3 must be replaced by the findings of a real keyboard and screen-reader check before publication — an accessibility statement that claims more than the product does is a liability, not a shield. The Hebrew accessibility statement remains in force in Israel.

Accessibility Statement

Trader Machine · US & Canada edition · Version 1.1 (DRAFT 2) · Effective date: not yet in force — set on publication · Last updated: 19 October 2026

The short version.

Our target is WCAG 2.2, Level AA. Today we are partially conformant — we say where we fall short (§3).
We fix our own code. We do not use, and do not rely on, accessibility overlay widgets.
Hit a barrier? Email us with the subject “Accessibility”. We reply within five business days and can reach you another way if email is hard for you (§8).

1. Our commitment

We want people with disabilities to be able to learn about, buy and use our software. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, for our websites, our legal and help pages, our sign-up and checkout flow, and our web application.

2. Where we are today

We have not yet completed a full accessibility audit, and we do not claim that the Service fully conforms to WCAG 2.2 AA. Our status is partially conformant: some parts of the content do not yet meet the standard. Section 3 lists what we know about.

3. Known limitations

Charts. Price charts and backtest equity curves are drawn as graphics. A screen reader cannot read the individual prices or points drawn on them. On request we send the underlying figures of a backtest as a table (§7).
Keyboard. Some panels in the application cannot yet be fully operated with a keyboard alone.
Contrast. Some secondary text and indicators in the dark theme may not meet the contrast ratio WCAG requires.
Captions. [OWNER DECISION: captions commitment for videos. Recommended default: as written in this bullet — every new lesson and session recording captioned within 7 days of posting; the existing library captioned within 90 days of publication; no live captions yet. WCAG treats captions on recorded video as a basic (Level A) requirement.] Every new lesson and session recording receives captions within 7 days of being posted, and recordings already in the library will have captions within 90 days after this statement is published.
Live captions. Live sessions do not yet have live captions; the captioned recording follows.

4. How we work on it

We fix the underlying pages: visible keyboard focus, labels on every form field (above all on sign-up, checkout and the cancel screen), text alternatives for meaningful images, sufficient colour contrast, and headings that describe the structure of each page.
We test with a keyboard only, with screen readers (NVDA on Windows and VoiceOver on macOS), with browser zoom up to 200%, and with automated checks — and we treat automated checks as a starting point, not proof.
We review this statement at least once a year and whenever we make a major change.

5. No overlay widgets

We do not use accessibility “overlay” plug-ins that promise to make a site compliant automatically, and we make no claim of compliance based on one. They do not repair the underlying code, and they can interfere with the assistive technology people already use. We make the changes in our own pages instead.

6. Desktop-only application

Our application is designed for current desktop versions of major browsers on Windows and macOS, and is not available on phones. Our legal and help pages work on any device. The desktop-only check does not block screen readers, magnifiers or browser zoom. If the desktop-only design is a barrier for you because of a disability, contact us and we will work with you on an alternative.

7. Third-party content and alternatives

Some parts of the experience are provided by others — the checkout and payment pages, which are run by Whop; the Vimeo player for lessons; the live-session room; Zoom for calls; and SignalStack. We consider accessibility when we choose providers, but we do not control their pages. If one of them stops you, tell us and we will help you another way.

On request, we will send any of our legal documents in plain text or large print, send backtest figures as a table, and help you through sign-up, checkout or cancellation by email or a call. We will never ask you to send a card number by email.

8. Tell us about a barrier

Email support@tradermachine.com with the subject line “Accessibility”. It helps to include the page or feature, what you were trying to do, and the browser and assistive technology you use. We reply within five business days.

If email is hard for you, send a short message saying how you would like us to reach you — for example a phone call, or a video call with captions — and we will contact you that way.

9. Other ways to raise a concern

If you are not satisfied with our answer, reply and ask for the owner to review it. Nothing in this statement limits any right you have under disability or consumer law.

10. About this statement

Prepared on 19 October 2026 (draft). It will be dated again when it is published and each time it is reviewed.