TradeTrade

Accessibility Statement

Last updated: April 29, 2026

1. Our Commitment

CleaRank Ltd (“CleaRank”, “we”, “us”) is committed to ensuring that our website (clearank.com) and our SaaS dashboard (trade.clearank.com) (together, the “Service”) are accessible to as many people as possible, including people with disabilities. We believe that financial education and paper-trading tools should be usable by everyone, regardless of ability, assistive technology, or device.

Accessibility is not a one-time project — it is an ongoing process. We design, build, test, and refine the Service against recognised international accessibility standards, and we welcome feedback that helps us do better.

2. Standards We Follow

We aim to conform to the following accessibility standards:

  • Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — published by the World Wide Web Consortium (W3C). This is the international benchmark for web accessibility and the basis of most national legal requirements.
  • EN 301 549 — the European harmonised standard for ICT accessibility, applicable under the European Accessibility Act (EAA) and the Web Accessibility Directive.
  • U.S. Section 508 and the Americans with Disabilities Act (ADA) Title III — for our users in the United States, where applicable case law treats commercial websites as places of public accommodation.

Where these standards differ, we apply the more protective requirement.

3. Compliance Status

This Service is partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that some parts of the content do not yet fully meet the standard. Known limitations are listed in Section 6.

Our most recent internal accessibility review was completed on April 29, 2026 by our product team using a combination of automated tools (axe DevTools, WAVE, Lighthouse) and manual testing with assistive technologies. We have not yet commissioned an independent third-party audit; we plan to do so as the Service matures. Our long-term goal is full conformance with WCAG 2.1 Level AA across the entire Service.

4. Accessibility Features

We have implemented the following features to support users with disabilities.

4.1 Perceivable

  • Text alternatives for all meaningful images, icons, and charts. Decorative images are marked appropriately so that screen readers skip them.
  • Captions and transcripts for all video and audio content embedded in the Service.
  • Sufficient colour contrast — body text meets a contrast ratio of at least 4.5:1, and large text meets at least 3:1, against background colours in both light and dark themes.
  • Resizable text — content remains readable and functional when zoomed up to 200% without horizontal scrolling on standard viewports.
  • Information not conveyed by colour alone — alerts, status indicators, and chart elements are also distinguishable by shape, label, or pattern.
  • Light and dark themes with sufficient contrast in both, switchable from the user-preferences menu.

4.2 Operable

  • Full keyboard navigation — every interactive element (buttons, links, form fields, charts, menus) is reachable and usable using only a keyboard. No keyboard traps.
  • Visible focus indicator — keyboard focus is always clearly visible with a high-contrast outline.
  • Skip-to-main-content link at the top of every page, allowing screen-reader and keyboard users to bypass repetitive navigation.
  • No content that flashes more than three times per second, in line with WCAG 2.3.1 (seizure-safe).
  • Adjustable session timeouts — when a session is about to expire, users are warned and offered the option to extend.

4.3 Understandable

  • Clear, plain language in all interface copy and educational content, with technical terms explained on first use.
  • Consistent navigation — primary navigation, action buttons, and labelling patterns are consistent across the Service.
  • Form input assistance — labels are programmatically associated with fields, errors are announced, and remediation guidance is provided in text.
  • Page language declared in the HTML so that screen readers pronounce content correctly.

4.4 Robust

  • Semantic HTML and ARIA — we use proper landmarks (<header>, <nav>, <main>, <footer>), heading hierarchy, and ARIA roles where native semantics are insufficient.
  • Tested with assistive technologies — see Section 5.
  • Status messages are announced to screen readers using aria-live regions where appropriate.

5. Compatibility With Browsers and Assistive Technologies

The Service is designed to be compatible with current and recent versions of:

Browsers

  • Google Chrome (current and previous major version)
  • Mozilla Firefox (current and previous major version)
  • Apple Safari (current and previous major version, macOS and iOS)
  • Microsoft Edge (current and previous major version)

Screen readers

  • NVDA (Windows) with Firefox or Chrome
  • JAWS (Windows) with Chrome
  • VoiceOver (macOS) with Safari
  • VoiceOver (iOS) with Safari
  • TalkBack (Android) with Chrome

Other assistive tools

  • Browser-native zoom up to 200%
  • High-contrast and forced-colours modes (Windows, macOS)
  • Speech-input tools such as Dragon NaturallySpeaking and Apple Voice Control
  • Switch-control devices (iOS / macOS)

The Service may not work reliably with browsers or assistive technologies more than two major versions old. We recommend keeping your browser and assistive software up to date.

6. Known Limitations

We are open about areas where we do not yet meet WCAG 2.1 AA. We are actively working on each item listed below.

  • Interactive charts. Our advanced charting library on trade.clearank.com currently has limited screen-reader support for granular data points. We provide a tabular alternative for OHLC and indicator data on each chart page; full chart accessibility is on our 2026 roadmap.
  • AI-generated content. Output from our AI Coach and Market Analyst features is presented in accessible HTML, but the underlying generation may occasionally produce content that does not follow ideal heading structure. We post-process for structure and continue to refine prompts.
  • Third-party embeds. Some third-party widgets (notably the PayMe payment iframe) are governed by their providers’ accessibility implementations. We monitor and request improvements but cannot guarantee third-party conformance.
  • Real-time market data tables. Very large data grids may present performance challenges for some screen readers. We offer paginated and filtered views as an accessible alternative.
  • Some PDF educational materials. Older PDF resources may not be fully tagged. We are remediating these and aim to have all educational PDFs WCAG-compliant by Q4 2026.

7. Accessibility Lead

CleaRank has appointed an Accessibility Lead responsible for receiving and responding to accessibility requests, coordinating internal improvements, and liaising with users.

Accessibility Lead: Shaun David Email: info@clearank.com (please include “Accessibility” in the subject line) Postal address: CleaRank Ltd, Beni Berman 2, Netanya 4249330, Israel

We accept communications in English. Initial response within 5 business days; resolution timelines depend on complexity.

8. Feedback and Reporting Accessibility Issues

We welcome feedback from all users. If you encounter an accessibility barrier, have a suggestion for improvement, or want to request content in an alternative format, please contact us:

  • Email: info@clearank.com — please include “Accessibility” in the subject line.
  • Postal address: CleaRank Ltd, Beni Berman 2, Netanya 4249330, Israel — Attn: Accessibility Lead.
  • In-app feedback: use the “Help & Feedback” link in the dashboard footer.

When reporting an issue, it helps us to know:

  1. The page or feature where the issue occurred (URL or screenshot).
  2. The browser, operating system, and assistive technology you were using.
  3. A description of the problem and what you were trying to accomplish.

We aim to acknowledge accessibility reports within 5 business days and to provide a substantive response, including any remediation timeline, within 30 days. Urgent barriers that prevent essential use of the Service are prioritised.

9. Enforcement and Complaints

If you are not satisfied with our response to an accessibility report, you may escalate to the appropriate authority for your jurisdiction:

  • European Union / EEA — your national equality body or data protection authority. The European Commission maintains a list of national contacts under the Web Accessibility Directive and the European Accessibility Act.
  • United Kingdom — Equality and Human Rights Commission (equalityhumanrights.com).
  • United States — U.S. Department of Justice, Civil Rights Division, ADA Information Line.

We strongly encourage you to contact us first so that we have an opportunity to resolve the issue directly.

10. Technical Specifications

Accessibility of the Service relies on the following technologies working in combination with the user’s browser and any assistive technologies:

  • HTML5
  • CSS3
  • JavaScript / TypeScript (React)
  • ARIA 1.2

These technologies are relied upon for conformance with the accessibility standards used.

11. Accessibility in Procurement and Vendor Selection

When we select third-party services, components, and libraries — including market data providers, payment processors, and analytics tools — we evaluate their accessibility conformance and prefer vendors who publish a current Voluntary Product Accessibility Template (VPAT) or equivalent conformance report. Where a critical vendor does not yet meet our standards, we work with them on remediation or provide an accessible alternative within the Service.

12. Training and Internal Process

All product designers, engineers, and content authors at CleaRank receive accessibility training as part of their onboarding and at least annually thereafter. Accessibility checks are part of our pull-request review process, and automated accessibility tests run in our CI pipeline. Accessibility regressions are treated as bugs.

13. Updates to This Statement

We review this Accessibility Statement at least once every twelve months, and after any significant change to the Service. Material updates will be reflected in the Last Updated date at the top of this document. Substantive changes will additionally be announced via email to registered users and via in-app notification.

14. Contact

CleaRank Ltd (Israeli Company No. 329591143) Beni Berman 2, Netanya 4249330, Israel Email: info@clearank.com Website: clearank.com Dashboard: trade.clearank.com

If you would like this statement in an alternative format (large print, plain-text email, audio, etc.), please contact us and we will provide it within 14 days at no charge.

Thank you for helping us make CleaRank accessible to everyone.