Will It Vibe?Multiple <h1> elements in one document
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
An HTML document with more than one <h1> gives screen-reader users, who often jump straight to the top-level heading to get page context, no single unambiguous "what is this page" landmark. Keep exactly one <h1> per document as the page title and demote the rest to <h2> or lower. Scoped to full HTML documents only, since a single component file in React/Vue/Svelte is routinely composed with others and its own <h1> count does not reflect the final rendered page.
Why it matters
Screen-reader users frequently jump between headings to skim a page, relying on there being exactly one <h1> as the unambiguous "what is this page" landmark. A document with two or more competes for that role and leaves the user unsure which one is the real title, especially when they land on the second one first via heading navigation.
How to fix it
Keep exactly one <h1> as the page's title, and demote any additional top-level headings to <h2> (or lower, depending on their place in the outline) based on where they actually sit in the document's hierarchy, not their font size.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo