Daily Accessibility ReviewMultiple H1 Elements Per Page Violate Heading Structure #17757
Unanswered
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem Description
Multiple pages in the Rancher Dashboard render more than one
<h1>element, violating the semantic heading structure expected by screen readers and assistive technologies.Affected pages and components:
/dashboard/home): Two<h1>elements — "Welcome to Rancher" (banner graphic) and "Clusters" (content area heading)./dashboard/c/local/explorer): Multiple<h1>elements — "Cluster Dashboard" (page title) plus numeric stat values such as "546", "1", "10" fromCountGauge,ResourceSummary, andCountBoxcomponents.WCAG 2.2 Violations
<h1>elements give screen reader users an incorrect picture of page structure.Relevant Code
shell/components/CountGauge.vue(line 102):shell/components/ResourceSummary.vue(line 120–123):shell/components/CountBox.vue(line 70):shell/pages/home.vue:Recommended Fix
Replace
<h1>with<span>(or a non-heading element) in stat/count components (CountGauge,ResourceSummary,CountBox) and apply equivalent CSS styling. The page-level heading ("Cluster Dashboard", "Welcome to Rancher") should be the sole<h1>per page. Section headings like "Clusters" should use<h2>or lower.Beta Was this translation helpful? Give feedback.
All reactions