Accessibility Statement

Charigent is committed to making our platform accessible to as many people as possible, including users with disabilities. We design, build, and test the product against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the international benchmark for digital accessibility.

Accessibility is treated as a first-class engineering concern, not a post-release checklist. Every public-facing page is reviewed against keyboard navigation, screen reader compatibility, color contrast, focus management, and motion-reduction preferences as part of the normal development workflow.

Target: WCAG 2.1 Level AA.

Status: Substantially conformant. We run an automated accessibility test suite against production releases (covering color contrast, semantic landmarks, heading hierarchy, alt text presence, focus indicators, and form labelling) and triage any regressions before deployment.

Some areas of the dashboard are still in active development and may contain accessibility issues we have not yet resolved. We track these openly and prioritize fixes for surfaces that block users from completing core tasks.

• Keyboard navigation. Every interactive control on public pages and the primary dashboard flows is reachable and operable using a keyboard alone. We provide a "Skip to main content" link as the first focusable element.
• Screen reader support. Pages use semantic HTML (landmarks, headings, lists, buttons), ARIA attributes where native semantics are insufficient, and descriptive labels on form controls.
• Color contrast. Body text meets the AA 4.5:1 contrast ratio on the default dark theme. UI colors are tested with both the automated suite and visual regression tooling.
• Focus management. Modals trap focus while open and restore focus to the trigger element on close. The Escape key closes overlays.
• Reduced motion. We honour the prefers-reduced-motion system preference and disable non-essential animations for users who request reduced motion.
• Image alternative text. Meaningful images include descriptive alt text. Decorative images are marked as such so screen readers skip them.

We test against the following combinations and aim for full functionality on each:

• NVDA + Firefox (Windows)
• JAWS + Chrome (Windows)
• VoiceOver + Safari (macOS, iOS)
• TalkBack + Chrome (Android)

We support the latest two major versions of Chrome, Firefox, Safari, and Edge.

We acknowledge the following areas where conformance is in progress. We are actively working on each and welcome reports.

• Some third-party embed surfaces (e.g. Stripe checkout, OAuth consent screens) are out of our direct control. Where possible we raise issues with the providers.
• Complex visualizations (Flow Builder canvas, analytics charts) provide accessible summary tables but do not yet have full keyboard parity with the visual canvas.
• Some user-generated content (custom Charigent personas, Marketplace listings) may not include alt text on images. We prompt creators to supply it but do not currently block submission without it.

If you encounter an accessibility barrier on Charigent, please tell us. We treat accessibility issues with the same urgency as security issues and aim to acknowledge reports within 2 business days.

Email [email protected] with:

• The page URL or feature where you experienced the barrier
• The assistive technology and browser/OS combination you use
• A description of the issue and what you expected

If you are not satisfied with our response, you may have additional options under applicable law:

• United States. Title III of the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act.
• European Union. European Accessibility Act (EAA) and Directive (EU) 2016/2102 on the accessibility of the websites and mobile applications of public sector bodies.
• United Kingdom. Equality Act 2010 and Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018.

We review this statement at least annually and after any major platform release. We will note material changes here and link to them from the platform changelog at /changelog.