Hadoop NameNode and ResourceManager UIs: no documented accessibility conformance for assistive technology

Context

Our team operates a Hadoop 3.3.x cluster and relies on the built-in NameNode UI (port 9870) and ResourceManager UI (port 8088) for day-to-day workflows. An internal requirement asks that all user-facing tools be usable with keyboard-only navigation and screen readers. Reviewing the Hadoop documentation, I can find no accessibility or WCAG conformance statement for these UIs, and the redesigned Hadoop 3 NameNode UI appears to be a legacy table-driven page set over JMX/REST.

Uncertainty

We need to decide whether to invest effort in making the built-in UIs accessible or to direct users to external dashboards or vendor consoles. The constraint is that any UI changes must not weaken documented security controls (Kerberos/SPNEGO authentication, read-only modes), and the ResourceManager UI's deep, parameterized URLs for filtering and pagination are hard to navigate with assistive technology.

Questions

What is the documented accessibility posture of the NameNode and ResourceManager UIs in Hadoop 3.3.x, and does the community have any open Jira issues or roadmap for WCAG conformance? Are there recommended approaches to harden the UI for screen readers and keyboard navigation without breaking Kerberos/SPNEGO authentication or read-only modes? If the built-in UIs are not intended to be accessible, is the guidance to use external tooling (custom dashboards over REST/JMX) the accepted path?