Accessibility statement

Novexa Pilot is built to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, across both light and dark themes. This is a design commitment enforced throughout the codebase — visible focus rings on every interactive element, full keyboard operability, semantic HTML with ARIA used only to fill gaps, 44×44px minimum touch targets, live regions for toasts and async results, and colour never used as the only signal — not a claim that every screen has been independently verified against it.

This statement is based on the design system’s rules and a static code-level review — grepping the codebase for common failure patterns (missing image alternative text, clickable elements without a keyboard-operable role, focus indicators removed without a replacement, form fields without an associated label) and fixing what that review found.

It is not a substitute for a full WCAG 2.1 AA audit performed by someone who did not build the screens, a real screen-reader pass through every core journey, a keyboard-only pass verifying focus order and trap behaviour in a live browser, or a reduced-motion/high-contrast verification pass in real assistive technology. Those require a human and a real browser, and remain open items — see the note in this product’s own Phase 10 tracking document.

• A single global rule collapses all animation/transition durations under prefers-reduced-motion: reduce.
• Every interactive element gets a 2px solid focus ring with a 2px offset on keyboard focus, not just a colour or shadow change.
• Radix UI primitives back menus, dialogs and popovers, giving correct roles, focus trapping in modals, and focus restoration on close for free.
• Form fields go through one shared component that always renders a real <label>, links hint and error text via aria-describedby, and sets aria-invalid.
• Charts carry role="img" with a descriptive aria-label summarising the trend, plus a table-view toggle as a non-visual alternative.

• No prefers-contrast: more handling exists yet — high-contrast mode has not been designed or verified, beyond the base theme already meeting AA contrast ratios.
• No independent WCAG audit, screen-reader pass, or keyboard-only pass has been run — the static review above catches a narrow, mechanical slice of real accessibility issues, not the full picture a human pass would find.
• The world map (visitor geography) is the one chart built outside the shared chart component set, on d3-geo directly rather than the charting library used elsewhere — it carries the same role="img"/label/table-toggle pattern, but as a one-off implementation it has had less scrutiny than the shared chart components.