Skip to content
Legal

Accessibility Statement

Last updated: July 25, 2026

Helm Pro LLC is committed to making Helm Pro usable by everyone, including people who use screen readers, keyboard-only navigation, magnification, or other assistive technology.

1. Conformance target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across our marketing site and customer Console.

We describe our status as PARTIALLY CONFORMANT: most of the product meets the standard, and we are aware that some areas do not yet. We would rather say that plainly than claim a conformance level we have not finished verifying.

2. What we do today

Semantic HTML with landmark structure, and a visible focus indicator on every interactive control.

Full keyboard operability for primary flows, including focus trapping and Escape-to-close on dialogs.

Color choices tested for contrast, and a design-token system that prevents ad-hoc colors from entering the product.

Motion is gated behind the operating system's reduced-motion preference.

Form controls carry programmatic labels, and errors are announced rather than conveyed by color alone.

Automated accessibility auditing runs against the Console as part of our development process.

3. Known limitations

Some data-dense operator views — particularly wide tables and charts — are not yet fully optimized for screen-reader navigation.

Automated auditing does not cover every route; manual assistive-technology testing is ongoing rather than complete.

Third-party embedded content may not meet the same standard, and is outside our direct control.

4. Feedback and requests

If you encounter a barrier, tell us and we will fix it. Email support@helmpro.io with the page or screen, what you were trying to do, and the assistive technology you use.

We aim to acknowledge accessibility reports within five business days, and we treat them as defects, not feature requests.

If you need information from the Services in an alternative format, ask and we will provide it.

5. Assessment approach

We combine automated auditing with manual keyboard and screen-reader testing during development. We have not commissioned a third-party audit; when we do, we will publish the result here.