Accessibility Statement

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility. We aim to conform to WCAG 2.1 Level AA.

WallaB.AI is partially conformant with WCAG 2.1 Level AA. Partial conformance means that some parts of the application do not yet fully conform to the standard. We are actively working to address the known issues listed below.

• •Loading, empty, and error states on every view — no unexplained blank screens
• •Full keyboard navigation, with focus traps in dialogs and visible focus indicators
• •Text alternatives on icon-only buttons and decorative graphics marked as such
• •Reduced motion respected: every animation on the platform is disabled automatically when your device requests reduced motion
• •Color contrast targeting AA across all three visual themes
• •Automated structural accessibility testing: key pages and components are checked against automated accessibility rules (heading order, landmarks, list and table semantics, most label and ARIA checks) as part of our regular testing, which helps catch many regressions before they ship — see §3 for the specific checks this does not yet cover.
• •Charts have a table view: every dashboard chart includes a keyboard-reachable “View as table” toggle that reveals the exact same data in a properly-marked-up table (WCAG 1.1.1)

The following areas are known to have accessibility gaps that we are working to address:

• •Complex data tables: a 2026-07 audit hand-checked a specific set of admin screens (subscriber management, plan setup, bulk actions, subscription creation, guardrail settings) and fixed the keyboard-operability gap found there — a sortable column header was mouse-only and is now reachable with Tab and activated with Enter or Space (WCAG 2.1.1). Six newer admin screens (workflows, email studio, win-back campaigns, win-back campaign detail, API keys, billing) now have automated structural accessibility coverage (axe-core, ARIA/labels/ landmarks) with zero violations found, but have not yet been through the hand keyboard-operability audit those five earlier screens received, and we have not yet run a full automated accessibility scan across every remaining admin surface, so gaps — including keyboard-operability ones — may still remain in screens we haven’t hand-audited yet; the remaining hand-audit and a full-surface automated pass are on our near-term roadmap.
• •Automated testing scope: our automated checks run in a simulated environment that does not measure rendered color contrast or on-screen target size (those are verified manually against WCAG AA) and, like any automated tool, cannot catch every case — for example a labeled form field where the label reference is broken but placeholder text is also present. Automated testing supplements, and does not replace, manual and assistive-technology review.
• •Language: the shopper subscription portal and sign-in emails are available in English, Spanish, French, German, and Brazilian Portuguese; the merchant dashboard is currently English-only. Broader admin and listing localization is on our public roadmap.

We are prioritizing remediation of these issues. If you encounter a specific barrier, please contact us (see §5) and we will work to resolve it promptly.

This application is designed to be compatible with:

• •Modern web browsers (Chrome, Firefox, Safari, Edge) with JavaScript enabled
• •Screen readers including NVDA (Windows), VoiceOver (macOS/iOS), and JAWS
• •Keyboard-only navigation
• •Browser zoom up to 200% without loss of content or functionality
• •Operating-system reduced-motion and color-scheme preferences

We welcome your feedback on the accessibility of this application. If you experience barriers or need content in an alternative format, please contact us: