What accessibility enhancements are needed for Aerospike Management Console to support keyboard navigation and screen readers?

Required Accessibility Enhancements for AMC

To transition the Aerospike Management Console (AMC) from a mouse-dependent interface to one that supports keyboard navigation and screen readers, several structural and attribute-level changes are required. These enhancements align with WCAG 2.1/2.2 standards to ensure that users with visual or motor impairments can monitor and manage clusters effectively.

Keyboard Navigation and Focus Management

Keyboard-only users require a predictable path through the application. The following implementations are necessary:

• Visible Focus Indicators: Every interactive element (buttons, links, inputs) must have a high-contrast focus ring to indicate the current active element.
• Logical Tab Order: The DOM order must match the visual layout so that the Tab key moves the cursor in a predictable sequence.
• Skip-Links: A "Skip to Main Content" link should be implemented at the top of the page to allow users to bypass repetitive navigation menus.
• Programmatic Focus Control: When a modal or configuration panel opens, focus must be moved into that container; when closed, focus should return to the triggering element.

Screen Reader Compatibility (ARIA)

Since AMC relies heavily on visual dashboards, screen readers need semantic metadata to interpret the data:

• WAI-ARIA Landmarks: Use <main>, <nav>, and <banner> roles to allow users to jump between functional areas.
• Descriptive Labels: Icon-only buttons (e.g., a gear icon for settings) must include aria-label attributes to describe their function.
• Form Labeling: Every input field must be explicitly associated with a <label> element.
• Live Regions: Real-time cluster statistics should use aria-live="polite" to notify users of updates without interrupting their current task.

Implementation Assumptions and Verification

Because AMC is built on third-party frameworks, these changes may require updates to the underlying UI library before they can be implemented in the console. To verify these improvements, the following scoped tests are recommended:

1. Keyboard Walkthrough: Attempt to perform a full cluster health check using only Tab, Shift+Tab, and Enter.
2. Screen Reader Audit: Use NVDA (Windows) or VoiceOver (macOS) to ensure all data visualization widgets provide a text-based summary of the data they represent.
3. HTML Validation: Run the interface through a WCAG 2.1 AA checklist tool to identify missing ARIA attributes.

Missing Diagnostic Detail: To provide a more accurate timeline or version estimate, it is necessary to know which specific version of the AMC (and its underlying framework) is currently deployed in your environment.