Daily Accessibility ReviewMultiple H1 Headings on Single Page (CountBox, CountGauge, ResourceSummary, Carousel) #17744
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.
-
Accessibility Issue: Multiple
<h1>Elements on a Single PageSeveral components use
<h1>for visually prominent numbers/titles, which results in multiple<h1>elements appearing on a single page. This violates best practices established under WCAG 2.2 Success Criterion 1.3.1 – Info and Relationships and 2.4.6 – Headings and Labels (Level AA).A page should have exactly one
<h1>representing its primary title. Using<h1>for numeric statistics/counts creates a confusing document outline for screen reader users who navigate by headings.Affected Files
1.
shell/components/CountBox.vue— line 70This component is used multiple times on the Cluster Dashboard to display statistics (e.g. "Total Resources: 522", "Node: 1", "Deployments: 10"). Each instance creates an additional
<h1>, resulting in several<h1>headings on one page.2.
shell/components/CountGauge.vue— line 102Used multiple times in the Cluster Dashboard Capacity section (Pods, CPU, Memory), each emitting its own
<h1>.3.
shell/components/ResourceSummary.vue— line 120Used in the resource summary cards — again creating multiple
<h1>elements.4.
shell/components/Carousel.vue— line 205Carousel slides each render an
<h1>for the chart name.Steps to Reproduce
local).Hin NVDA/JAWS) — multiple<h1>headings appear: the page title plus every metric count.Suggested Fix
Replace
<h1>with either:<div>or<span>(with appropriatearia-labelif needed), since these counts are data, not document headings; OR<h2>or<h3>) if a heading hierarchy is desired, ensuring no level is skipped.Example for
CountBox.vue:WCAG References
Beta Was this translation helpful? Give feedback.
All reactions