Keyboard navigation
Interactive elements are reachable via keyboard.
PilotCB is designed to support keyboard, touch and responsive use across a range of devices.
01 · Verified in the product
Current implementation practices that can be inspected in the public and operational interfaces.
Interactive elements are reachable via keyboard.
Focus states use a high-contrast outline on links, buttons, inputs, selects, and summary elements.
Pages use semantic landmarks and heading hierarchy. Collapsible content and file uploads use native controls with appropriate attributes.
Primary navigation links, buttons, and interactive controls use a minimum height of 44px with touch-friendly spacing.
Layouts adapt from mobile through ultrawide displays. Operational grids reflow at 820px and 620px without a fixed pixel content width.
The site respects prefers-reduced-motion, disabling smooth scrolling and minimizing transition durations.
Operational status indicators include text labels and icons in addition to color.
Some operational views, especially the Pro Workspace map and complex grid layouts, have not been independently audited for full assistive technology compatibility.
Map interactions rely on the Leaflet library, which provides its own accessibility layer. Keyboard and screen reader support for map controls follows Leaflet's implemented behavior.
Dynamic content updates, such as live NAS status and flight position polling, rely on visual indicators and do not currently broadcast status changes through ARIA live regions.
WCAG 2.2 Level AA is the design target. PilotCB has not undergone independent WCAG conformance testing, and no WCAG or ADA certification is claimed.
The product is designed to support accessible interaction patterns, but formal conformance status is not asserted.
Report accessibility issues to [email protected]. Include the affected page, device or assistive technology, and the task you could not complete.