Accessibility and digital equity: is this product actually usable by executives with disabilities, or is WCAG a line in your marketing?

The full executive answer

It is enforced in the build pipeline, which is the strongest claim any vendor can truthfully make. Accessibility lint errors — the jsx-a11y ruleset — are hard failures in our CI: a change that introduces an unlabelled control or a broken ARIA pattern cannot be merged, by anyone, including me. Beyond linting, we maintain dedicated accessibility engineering: a contrast utility validates colour pairs against WCAG thresholds, and a shared modal-accessibility hook enforces focus trapping, escape handling and focus return on every dialog — that focus-management layer was specifically hardened in recent work.

On equity of access more broadly: the product ships as a progressive web app with an offline fallback, so it degrades gracefully on poor connectivity — relevant for board members travelling or in low-bandwidth regions. The internationalisation foundation supports seven launch locales — English, Spanish, French, German, Arabic, Hindi and Japanese — including full right-to-left layout for Arabic, with a translation-coverage function that measures exactly what fraction of each catalogue is translated, so our language claims are quantified rather than aspirational.

Honest current-versus-roadmap: automated enforcement and the engineering substrate are current. A third-party WCAG 2.2 AA audit with a published VPAT/conformance report is roadmap — it is the natural next step once we have launch stability, and I would welcome your accessibility team testing the product as part of evaluation.