Kilotest: Diagnoses of landmarks not distinctly named violation by HTML element 302 on Founders Pledge page

Basics

About the page

• URL: https://www.founderspledge.com/
• Tested 3 days ago on 2026-10-07 at 21:27 by job 261007T2113-g5v
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 485
  • Violators: 144
  • Issues: 54
• Download the full technical report (JSON)

About the issue

• Why it matters: User cannot get help on how some of the page is organized
• Priority: high
• Related WCAG standard: 1.3.6
• Reported by 2 rule engines (Axe + Pour)
• Violations: 3
• Violators: 2

About the violator

• Tag name: NAV
• Text: “Signing up to Founders Pledge was very real for me...I gave it very detailed thought and, quite frankly, it turned out to be a no brainer.” … Founder & CPO of SoundCloud
• Start tag: <nav class="wsum663">
• XPath: /html/body/main[1]/section[1]/div[2]/section[1]/div[2]/nav[1]
• Bounding box: x = 0, y = 4886, width = 1920, height = 76
• Reported by Axe + Pour

Diagnoses

Here is how rule engines diagnose the landmarks not distinctly named issue for HTML element 302 of the Founders Pledge page.

1. Landmarks should have a unique role or role/label/title (i.e. accessible name) combination; The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable

   Rule engine: Axe (Deque)

   Rule: landmark-unique

2. Landmarks of the same type need distinguishing labels

   Rule engine: Pour (David Yarham and Geoffrey Crofte)

   Rule: landmark-unique