Loading
One moment.
One moment.
Last updated: May 26, 2026
HelmXP is committed to making its platform accessible to all users, including those who rely on assistive technologies.
HelmXP targets WCAG 2.2 Level AA conformance across all four application surfaces: the public marketing site, the tenant portal, the customer-admin section, and the HelmXP super-admin control plane.
As of 26 May 2026, an automated and manual audit of the editor surface has completed. Full surface audits are in progress.
The platform is tested with the following combinations:
packages/ui/src/themes/high-contrast.css) are both supported@react-pdf/renderer) produces PDFs with embedded structural tagging for common readers but has not been tested against PDF/UA.Two CSS theme overrides ship in packages/ui/src/themes/:
high-contrast.css) — increases contrast ratios beyond the standard tokens; suitable for users with low vision or photosensitivitydyslexia-friendly.css) — increases letter-spacing, word-spacing, and line-height; uses a wider sans-serif stackTenant administrators can enable either theme from the portal accessibility preferences panel.
HelmXP ships with English (default), French (fr-CA), and partial Spanish (es) locale catalogs. The active locale is stored in hubs.default_locale (migration 0072). Locale-aware date, number, and currency formatting is provided by packages/i18n.
If you encounter an accessibility barrier, contact the HelmXP support team at support@helmxp.com with the subject line "Accessibility barrier." Include the URL, a description of the barrier, and the assistive technology you are using. We will respond within five business days.
This statement references WCAG 2.2 (W3C Recommendation, October 2023), Section 508 of the US Rehabilitation Act, and the European Accessibility Act (EAA) Directive 2019/882.