Rancher Dashboard and SAML/OIDC login: can the UI meet WCAG 2.1 AA for compliance-driven deployments?

Question

We run Rancher as the authentication proxy in front of several downstream Kubernetes clusters, with a SAML/OIDC identity provider handling single sign-on. The user-facing workflow — IdP login redirect, cluster list, project selection, workload views — all goes through the Rancher Dashboard, so it is the surface our compliance review has to cover.

Our organization must attest that internal tooling conforms to WCAG 2.1 AA (and Section 508 for some users). I cannot find a published, versioned conformance statement for the Dashboard: no VPAT, no documented target standard, and no clear statement of which release line any accessibility fixes landed in. The RBAC and auth-proxy behavior is well documented, but the UI accessibility posture is not.

Assume a recent 2.7+ deployment; behavior may differ across versions, which is part of the problem.

Is there any official conformance target or VPAT for the Rancher Dashboard, per version? Which known gaps (keyboard navigation, focus management, screen-reader labeling) should we expect on the login and cluster-navigation workflows? Short of manual audit with NVDA/VoiceOver, is there a supported way to validate conformance for a compliance sign-off?

Tasadduq Burney · Answer

Direct answerThere is no published, version‑specific VPAT or official WCAG 2.1 AA conformance statement for the Rancher Dashboard; therefore you cannot assume the UI meets the standard without your own verification.Confirmed factsRancher’s documentation and release notes mention occasional accessibility fixes (e.g., improved focus handling, added aria‑labels) but never a cumulative conformance claim.Community reports and GitHub issues highlight recurring gaps in the SAML/OIDC login and cluster‑navigation workflows: missing or insufficient ARIA labels, inconsistent focus order after redirects, and modal dialogs that can trap keyboard focus.Automated tools such as axe‑core or Lighthouse can detect many WCAG violations (contrast, missing labels, landmark roles) but do not catch all focus‑management or screen‑reader announcement problems.Steps to validate for your deploymentIdentify the exact Rancher Server version (e.g., v2.7.5, v2.9.3) and note any custom themes, CSS overrides, or authentication extensions.Run an automated scan with axe‑core (browser extension or npm package) on the pages involved in the SAML/OIDC login redirect, the cluster list view, project selector, and workload pages. Record any WCAG 2.1 AA violations.Perform keyboard‑only navigation: Tab through the login form, verify a visible focus indicator, ensure focus returns to a logical element after the IdP redirect, and confirm that all modal dialogs can be opened, used, and closed without trapping focus.Conduct screen‑reader checks (NVDA on Windows, VoiceOver on macOS/iOS) for the same workflows; listen for missing or unclear labels, verify that dynamic updates (e.g., error messages, cluster list changes) are announced, and confirm that error messages are conveyed.Document the version, browser/screen‑reader combinations, test dates, and any remediation applied. Keep logs, screenshots, and axe reports as evidence for compliance sign‑off.Missing diagnostic detail that could change the recommendationIf you are using a custom UI theme or have injected additional HTML/scripts from your IdP, please specify those customizations; they may introduce accessibility issues not present in the vanilla Dashboard and would affect the validation steps.

Rancher Dashboard and SAML/OIDC login: can the UI meet WCAG 2.1 AA for compliance-driven deployments?

1 answer

Direct answer

Confirmed facts

Steps to validate for your deployment

Missing diagnostic detail that could change the recommendation

Your perspective belongs here.

0 question comments