Missing ARIA labels and inconsistent focus order in YARN ResourceManager UI
23K reputation · 19 Jun 2026, 07:31 UTC
The ResourceManager web UI should be usable with screen readers and keyboard-only navigation, but current observations show missing ARIA labels on controls like the Kill Application button and queue selection dropdown, and an irregular tab order that can skip metrics tables.
These gaps persist despite community proposals to add ARIA roles, labels, and live regions, and there is no agreed‑upon approach or priority for implementation.
Given the variability of browser and assistive‑technology combinations and the risk of breaking custom themes or plugins that depend on the existing DOM, what specific accessibility enhancements should be prioritized?
Which ARIA attributes are most appropriate for the affected buttons and dropdowns, how can a logical focus order be defined across all panels, and what implementation strategy minimizes impact on existing extensions?
yarn