Our commitment
Veirox is targeting conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA across the console and marketing site. We have not yet completed a formal third-party accessibility audit — this statement describes what's actually in place today, not a compliance claim we can't back up.
Current state
Accessibility isn't a single project here — it's a set of conventions enforced as the console is built:
- Semantic HTML and ARIA labeling on interactive controls (row action menus, sort headers, dialogs).
- Full keyboard navigation on data tables — arrow keys, Enter, and a
g g"go to top" shortcut — plus keyboard-operable row actions, not just hover-revealed ones. - Dialogs and modals close on
Escape, auto-focus their primary input, and label every form field visibly (not just viaaria-label). - Automated lint rules (
jsx-a11y) flag missing keyboard handlers and non-native interactive elements on every pull request. - Dark and light theme support with contrast-checked color tokens.
What we haven't done yet: a full manual screen-reader pass (NVDA/JAWS/VoiceOver) across every console surface, or an independent WCAG audit. Some older pages and third-party-embedded content (e.g. certain chat tool-call renderers) may not fully conform.
This marketing site
Static HTML with semantic landmarks, alt text on images, and keyboard-operable navigation. It shares the same lint discipline as the console codebase but hasn't had a dedicated audit either.
Report a barrier
If you use assistive technology and hit something that doesn't work, tell us — specifics help: the page, the assistive tech + browser you're using, and what you expected to happen. Email support@veirox.com or use the support form. We treat accessibility bugs as bugs, not feature requests — they get triaged accordingly.
Target standard
WCAG 2.1 Level AA. We'll update this page as conformance work lands, and note the date of any completed third-party audit here rather than assert one that hasn't happened.