Kilotest: Diagnoses of not exactly 1 h1 heading
violation by HTML element 0 on Tradeoffs page
Basics
About the Tradeoffs page
- URL: https://tradeoffs.org/
- Tested 30 days ago by job
5g2on 2026-06-20 at 13:59
About HTML element 0
- Tag name:
HTML - Text: [not applicable]
- Start tag:
<html lang="en-US" style="--jp-search-page-ink: rgb(17, 17, 17); --jp-search-page-surface: rgb(255, 255, 255);"> - XPath:
/html - Bounding box: x = 0, y = 0, width = 1920, height = 7626
About the not exactly 1 h1 heading
issue
- Why it matters: User cannot understand the topic of the document
- Priority: low
- Related WCAG standard: 1.3.1
Diagnoses
Here is how rule engines diagnose the not exactly 1 h1 heading
issue for HTML element 0 of the Tradeoffs page.
- Expected at least one heading <code>h1</code> element, but found none.
Tool: ASLint (eSSENTIAL Accessibility)
Rule:
h1_must_be - Page should contain a level-one heading; Page must have a level-one heading
Tool: Axe (Deque)
Rule:
page-has-heading-one