Kilotest: Diagnoses of not exactly 1 h1 heading violation by HTML element 0 on Quiet Communities page

Basics

About the page

• URL: https://www.quietcommunities.org/
• Tested 3 days ago on 2026-10-07 at 22:17 by job 261007T2152-n0c
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 806
  • Violators: 388
  • Issues: 56
• Download the full technical report (JSON)

About the issue

• Why it matters: User cannot understand the topic of the page
• Priority: low
• Related WCAG standard: 1.3.1
• Reported by 2 rule engines (ASLint + Pour)
• Violations: 2
• Violators: 1

About the violator

• Tag name: HTML
• Text: [not applicable]
• Start tag: <html xmlns:og="http://opengraphprotocol.org/schema/" xmlns:fb="http://www.facebook.com/2008/fbml" lang="en-US" data-uw-w-loader="" style="--header-height: 208.21875px; scroll-behavior: smooth; --header-fixed-top-offset: 208.21875px; scroll-padding-top: 208.219px;">
• XPath: /html
• Bounding box: x = 0, y = 0, width = 1920, height = 8634
• Reported by ASLint + Pour

Diagnoses

Here is how rule engines diagnose the not exactly 1 h1 heading issue for HTML element 0 of the Quiet Communities page.

1. Expected at least one heading <code>h1</code> element, but found none.

   Rule engine: ASLint (eSSENTIAL Accessibility)

   Rule: h1_must_be

2. Every page should start its outline with an <h1>

   Rule engine: Pour (David Yarham and Geoffrey Crofte)

   Rule: page-heading-one