Last reviewed: August 2026
1. Our commitment
AgentaFlow, LLC is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards to whiteboxxai.com and the WhiteBox XAI platform.
We regard accessibility as a core quality requirement of the product, not an optional add-on. Barriers reported to us are treated as defects and prioritized accordingly.
2. Conformance standard
We measure this website against the Web Content Accessibility Guidelines (WCAG) 2.1 (opens in a new tab) at Level AA. WCAG 2.1 Level AA is the standard referenced by the Americans with Disabilities Act (ADA) in U.S. Department of Justice guidance and rulemaking, by Section 508 of the Rehabilitation Act for U.S. federal procurement, and by EN 301 549 in the European Union.
Level AA covers everything in Level A as well as the additional Level AA success criteria, including minimum contrast, resize and reflow, consistent navigation, error suggestion, and identifying the purpose of form inputs.
3. Conformance status
This website is substantially conformant with WCAG 2.1 Level AA. “Substantially conformant” means the site meets the Level AA success criteria across its public pages, with the specific exceptions described in section 6 below.
We state this rather than claiming full conformance because parts of the experience depend on third-party components we do not control, and because accessibility conformance is a continuous obligation rather than a one-time certification. We would rather give you an accurate picture and a way to reach us than an overstated claim.
4. Measures we take
- Accessibility is treated as a requirement of the definition of done, not a post-launch cleanup pass.
- Automated accessibility checks (axe-core) run against the public pages in our test suite on every change, and a failing check blocks the build.
- We build on semantic HTML and the accessible component primitives from Radix UI, rather than re-implementing interactive controls from generic elements.
- Colour choices are validated against WCAG contrast ratios before they enter the design tokens.
- Keyboard operability and focus visibility are reviewed for every interactive component.
5. Accessibility features of this site
- Keyboard access
- Every interactive element — navigation, menus, dialogs, forms, image galleries, and scrollable code samples — is reachable and operable with a keyboard alone. A visible focus indicator is drawn on whatever currently has focus, and no component traps keyboard focus.
- Skip to content
- A “Skip to main content” link is the first element on every page, letting keyboard and screen-reader users bypass the header navigation.
- Screen reader support
- Pages use landmark regions (banner, navigation, main, contentinfo), a single descriptive page title, and a correctly ordered heading structure. Decorative icons and images are hidden from assistive technology so they do not clutter the reading experience.
- Text alternatives
- Images that carry meaning have descriptive alternative text. Purely decorative images are marked as such. Links that open in a new tab announce that before they are followed.
- Colour and contrast
- Body text meets or exceeds the 4.5:1 contrast ratio required by WCAG 2.1 AA, and interactive component boundaries meet the 3:1 non-text contrast ratio. No information is conveyed by colour alone — status is always also given in text or shape.
- Forms
- Every field has a persistent visible label, not a placeholder standing in for one. Required fields are marked in text. Errors are described in words, tied to the field they belong to, and announced to screen readers when they appear. Fields collecting personal data carry autocomplete attributes so browsers and assistive tools can fill them.
- Motion
- Animations and transitions are reduced to near-zero for visitors whose operating system requests reduced motion. Nothing on the site auto-plays, flashes, or moves without the visitor starting it.
- Resizing and reflow
- Content reflows to a single column and remains usable at 400% zoom and at a 320 CSS pixel viewport width, without requiring horizontal scrolling of the page.
6. Known limitations
Despite our best efforts, some limitations remain. We list them here so you know what to expect and can contact us for an alternative.
- Embedded video player
- Product videos are embedded from YouTube, whose player we do not control. Captions and an interactive transcript are available through the player's own controls, and each video links out to the full YouTube page and to equivalent written documentation. No information on this site is available only in video form.
- Third-party content
- Our documentation site, payment checkout (J.P. Morgan), and authentication providers are operated by third parties. We evaluate their accessibility when selecting vendors, but we cannot directly remediate their interfaces. If you hit a barrier in one of these, tell us and we will work with the vendor and provide an accessible alternative route in the meantime.
- Ongoing assessment
- Our automated coverage runs on every change, but assistive-technology testing is periodic rather than continuous. Newly published pages may reach visitors before the next manual review cycle.
7. How we assess this site
AgentaFlow, LLC assesses the accessibility of WhiteBox XAI by self-evaluation, combining automated and manual methods:
- Automated rule checking with axe-core, run as part of our continuous integration suite against every public page, so a regression fails the build rather than reaching production.
- Manual keyboard-only walkthroughs of each page and interactive component.
- Programmatic verification of colour contrast ratios against the WCAG formula for every colour token in the design system.
- Review of markup semantics — landmarks, heading order, form labelling, and name/role/value of custom controls.
Automated tooling catches only a portion of possible accessibility issues. We do not present passing automated checks as proof of conformance, and we welcome reports of anything our process missed.
8. Compatibility and technical specifications
This site is designed to work with current versions of Chrome, Edge, Firefox, and Safari, used together with the screen readers commonly paired with them, including NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android. It also supports operating-system settings for increased text size, reduced motion, and increased contrast.
Accessibility of this site relies on HTML, WAI-ARIA, CSS, and JavaScript. It is not fully usable with JavaScript disabled.
9. Feedback and how to report a barrier
We welcome your feedback on the accessibility of WhiteBox XAI. If you encounter a barrier, or need information from this site in an alternative format, please contact us:
Please tell us the page address, what you were trying to do, and the browser and assistive technology you were using. That detail lets us reproduce the problem quickly.
We aim to acknowledge accessibility reports within 3 business days and to give you a remediation plan, or the information you requested in an accessible format, within 10 business days. If a fix will take longer, we will tell you why and offer an interim alternative.
10. Formal complaints
If you are not satisfied with our response, you may escalate the matter by writing to AgentaFlow, LLC at accessibility@agentaflow.com. Nothing in this statement limits any right you may have under applicable disability, consumer, or data protection law.