Explicit ARIA Roles vs. Accessible Component Refactor for Netbox Data Tables

Goal

Improve the accessibility of Netbox’s primary data tables so that screen readers can reliably interpret column headers, row data, and interactive elements without altering the current Bootstrap‑5 styling.

Constraint

Any change must preserve the existing layout, color palette, and JavaScript behavior that users rely on for efficient navigation.

Unresolved Decision

The community debate centers on whether to add explicit ARIA attributes to the current HTML tables or to replace them with a fully accessible component library.

Questions

1. Which approach—augmenting tables with ARIA roles or refactoring into a new component—provides superior screen‑reader comprehension while maintaining Bootstrap styling?
2. How can we add descriptive aria‑labels to filter dropdowns and table headers without breaking existing keyboard navigation?
3. What migration strategy minimizes downtime for production deployments that already use custom themes?