Kilotest: Diagnoses of landmarks not distinctly named violation by HTML element 97 on Portland City Club page

Basics

About the page

• URL: https://www.pdxcityclub.org/
• Tested 0 days ago on 2026-10-10 at 05:30 by job 261010T0528-evq
• Summary of results:
  • Rule engines:
    • Called: 12
    • Were able to test: 12
    • Reported any rule violations: 12
  • Violations: 718
  • Violators: 203
  • Issues: 53
• 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: About Us What We Do Events Membership Support Us
• Start tag: <nav id="site-navigation" class="main-navigation" role="navigation">
• XPath: /html/body/div[1]/div[1]/header[1]/div[2]/div[1]/div[2]/nav[1]
• Bounding box: x = 710, y = 74, width = 780, height = 67
• Reported by Axe + Pour

Diagnoses

Here is how rule engines diagnose the landmarks not distinctly named issue for HTML element 97 of the Portland City Club 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