Our commitment

BlitzPulse is committed to making our platform accessible to as many people as possible, including users with disabilities. We treat accessibility as a continuous engineering responsibility, not a one-time audit.

Conformance target

We work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA published by the W3C Web Accessibility Initiative. WCAG 2.1 AA is the standard referenced by the U.S. Department of Justice in ADA Title III enforcement and by the European Accessibility Act.

This is a goal, not a claim of perfection. Some surfaces are still being remediated; see Known limitations below.

What we have implemented

• Semantic HTML — pages use heading hierarchy, landmark roles, and form labels so assistive technology can navigate them.
• Keyboard navigation — every interactive control on the trading dashboard, settings, and admin surfaces is reachable and operable via keyboard alone, including focus indicators that meet WCAG 2.4.7.
• Color contrast — text and meaningful UI elements meet WCAG 1.4.3 (4.5:1 normal, 3:1 large) under our default theme. The high-contrast theme on the Appearance page exceeds these ratios. Color is never the only signal for state (paid/free, profit/loss, alerts).
• Reduced motion — animation and chart transitions respect the operating-system prefers-reduced-motion setting.
• Screen-reader compatibility — tested against current versions of NVDA, JAWS, and VoiceOver on supported browsers.
• Resizable text — UI scales to 200% without loss of content or function (WCAG 1.4.4).
• Form errors — validation messages are programmatically associated with their fields and announced by assistive tech.

Known limitations

The following areas have known accessibility gaps. We are actively working on them and welcome feedback.

• Real-time charts. Live candlestick and depth-of-market visualizations are presented graphically; we are working to expose underlying data through an accessible table view.
• Heatmaps and treemaps. These rely on color and spatial layout. Tabular alternatives are planned.
• Third-party broker pop-ups. OAuth flows for Schwab, SnapTrade, and other broker integrations are rendered by the broker; their accessibility is governed by the broker’s own policies.

Browser and assistive-tech support

We test against the latest two stable releases of:

• Google Chrome on Windows, macOS, and ChromeOS
• Mozilla Firefox on Windows and macOS
• Apple Safari on macOS and iOS
• Microsoft Edge on Windows

Combined with:

• NVDA on Windows
• JAWS on Windows
• VoiceOver on macOS and iOS
• TalkBack on Android

If you use an older browser or different assistive-tech configuration and encounter problems, please tell us — we may not have tested it but will respond.

Reporting an accessibility issue

If a part of BlitzPulse is not accessible to you, please contact us so we can fix it. We treat accessibility reports with the same priority as security reports.

• Email: accessibility@blitzglobalcapital.com
• Subject line: “Accessibility — [page or feature]”
• Please include: the URL of the page, the assistive technology and browser you are using, and a description of the problem (a screen-reader transcript or screen recording is helpful but not required).

We aim to acknowledge accessibility reports within 2 business days and will share a remediation plan within 10 business days. Critical issues that block account access or trading functionality are treated as P0.

Formal complaints

If you are not satisfied with our response, you may also escalate to:

• In the United States: the U.S. Department of Justice ADA hotline at 1-800-514-0301, or your state’s attorney-general office.
• In the European Union: the accessibility-monitoring authority of your member state under the European Accessibility Act.

We do not require you to use our internal channel before filing externally. Both options are open.

Updates to this statement

We review and update this statement at least annually and whenever a substantive accessibility improvement or regression occurs. The Last updated date at the top of this document reflects the most recent revision.