Kilotest: Diagnoses of landmarks not distinctly named violation by HTML element 77 on Global Greengrants Fund page

Basics

About the page

• URL: https://www.greengrants.org/
• Tested 3 days ago on 2026-10-07 at 21:38 by job 261007T2113-zjw
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 753
  • Violators: 226
  • Issues: 63
• 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: 7
• Violators: 5

About the violator

• Tag name: HEADER
• Text: Instagram … Subscribe to Newsletter
• Start tag: <header class="pre-header pre-header--desktop container--outer">
• XPath: /html/body/header[1]
• Bounding box: x = 0, y = 0, width = 1920, height = 72
• Reported by Axe + Pour

Take me there

Diagnoses

Here is how rule engines diagnose the landmarks not distinctly named issue for HTML element 77 of the Global Greengrants Fund 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