Limits of the Prometheus Expression Browser Accessibility

The Prometheus expression browser is rendered from Go templates with minimal ARIA attributes, which restricts keyboard navigation and screen‑reader usability.

Community proposals suggest moving to a client‑side framework to gain richer accessibility features, but this would increase binary size and introduce runtime dependencies that conflict with Prometheus’s low‑overhead design goal.

What trade‑offs should guide the decision to retain the current lightweight UI versus adopting a more accessible modern frontend, and how can the project evaluate the impact on resource‑constrained deployments?