Kilotest: Diagnoses of landmarks not distinctly named violation by HTML element 223 on Freedom House contact page

Basics

About the page

• URL: https://freedomhouse.org/about-us/contact-us
• Tested 3 days ago on 2026-10-07 at 21:20 by job 261007T2113-3d2
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 11
  • Violations: 517
  • Violators: 165
  • Issues: 44
• 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: DIV
• Text: Contact Us … Washington, DC 20005
• Start tag: <div class="region region-content" id="main-content" role="main">
• XPath: /html/body/div[2]/div[1]
• Bounding box: x = 0, y = 143, width = 1920, height = 1276
• Reported by Axe + Pour

Diagnoses

Here is how rule engines diagnose the landmarks not distinctly named issue for HTML element 223 of the Freedom House contact 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